Any way to remove plymouth completely?

[penguin]

Any way to remove plymouth completely? I have deactivated from appearing but still during shut down, Sparky still hangs some moments on it.
The plymouth cannot be removed using Synaptic because is part of Sparky Core.My Sparky 32bit xfce.

[paxmark1]

Are you Sparky5 or 4    - Buster or Stretch for your Debian core

Try looking at
http://sparkylinux.org/forum/index.php/topic,4257.msg10635.html#msg10635

I have removed plymouth in the distant past via command line to lose the start up image and to see error messages scroll by.  But then I lost all the sparky applications. 

As Pavroo says in the Dec 24 2017 post you can re-install the sparky apps. 

Also via a 2016 post   
http://sparkylinux.org/forum/index.php/topic,3768.msg8908.html#msg8908

check out the latest at

https://wiki.debian.org/plymouth       ## no comments there for Buster - Sparky 5
I would not recommend the Arch web page I mentioned prior in 2016.  It is only good for information, Arch has several large differences from Sparky. 

Code not pasting from my Sparky5 in virtual box.  more info can be found by running these commands
"aptitude why plymouth"                ## you might not have aptitude installed

and
"apt-cache showpkg plymouth"      ## the reverse depends are the reasons.

None of these actions will change anything on your system. 

[penguin]

Are you Sparky5 or 4    - Buster or Stretch for your Debian core

Try looking at
http://sparkylinux.org/forum/index.php/topic,4257.msg10635.html#msg10635

I have removed plymouth in the distant past via command line to lose the start up image and to see error messages scroll by.  But then I lost all the sparky applications. 

As Pavroo says in the Dec 24 2017 post you can re-install the sparky apps. 

Also via a 2016 post   
http://sparkylinux.org/forum/index.php/topic,3768.msg8908.html#msg8908

check out the latest at

https://wiki.debian.org/plymouth       ## no comments there for Buster - Sparky 5
I would not recommend the Arch web page I mentioned prior in 2016.  It is only good for information, Arch has several large differences from Sparky. 

Code not pasting from my Sparky5 in virtual box.  more info can be found by running these commands
"aptitude why plymouth"                ## you might not have aptitude installed

and
"apt-cache showpkg plymouth"      ## the reverse depends are the reasons.

None of these actions will change anything on your system.

I use the latest stable Sparky Debian (4.8.1). The LXDE desktop is purged and XFCE is installed instead of it.
I read all about plymouth(given on your links) . Plymouth gives me idea that Sparky spend in vain time during startup or shutdown. Simply I would like to see boot and log out logs. I have deactivated plymouth from grub and I am able to see all logs, but still I see on the screen a line related to plymouth that glitches/delays Sparky a little bit(sometimes longer) 

[paxmark1]

plymouth is what many desire, but this is linux, and we can change some things

Sounds good.  How did you remove plymouth?    Did you deactivate it via changing grub 2? 
If you did please post your how you did disable plymouth from grub2 for others to see how to do it. 
If satisfied mark you post "Solved: Any way to  ... ? "

that would be the conservative way
If you can live with that, all is good.

The more drastic method would be to specifically remove plymouth and then replace Sparky items that were removed with it. 
"man apt-get"  or "man apt"  would help make your decisions.  Years ago I had a Sparky box that I removed plymouth, but did not re-install - so in effect I mostly had a debian box that was installed via sparky.  More recent installs I have not removed plymouth.  My main box is Debian stable with important things and it came without plymouth.  Not running plymout might have consequences, back up, back up.  See
https://www.freedesktop.org/wiki/Software/Plymouth/       

Plymouth isn't really designed to be built from source by end users. For it to work correctly, it needs integration with the distribution. Because it starts so early, it needs to be packed into the distribution's initial ram disk, and the distribution needs to poke plymouth to tell it how boot is progressing.

Things can go wrong.  Trials can be made in a virtual system.  I have a virtual system of Sparky5 that I could try removing plymouth on, but I have very little time presently, my father is moving, we are ... and ...  and ...   - busy, busy and work wants extra hours also. 

For someone who appears to want to learn and have a lean system with a fast boot time, reading up on systemd systemd-analyze journalctl will be well worth your effort.  DigitalOcean has some very good web pages.  And for playing around with  "what if I do ..."   "apt - s remove blah" or "apt -s install blah"  will show the basics of what and how many binaries will be effected.    No actual changes will be made.  Also read up on the   --no reccomends

[penguin]

I remember that I asked pavro times ago and more or less i changed grub lines as follow:

Code Select Expand

https://askubuntu.com/questions/25022/how-to-enable-boot-messages-to-be-printed-on-screen-during-boot-up

follow line are grabbed by article:

gksudo gedit /etc/default/grub  # use gedit or open by your favorite editor
and enter your password.

Find the line starting with GRUB_CMDLINE_LINUX_DEFAULT and remove the parameters quiet and  splash.
Save the file and close the editor.
Finally, start a terminal and run:
sudo update-grub
to update GRUB's configuration file.

but....
let me explain. I have a loptop X201i, with a SSD of 64 GB,where I have installed MX Linux and Saprky Linux (both 32 bit) and a SD Card that has Sparky Linux 64 bit installed on it.
When I installed Sparky 32bit the laptop have an installed grub before from MX Linux.So the grub is let's say is part of MX-Linux 32 bit. Many times I have forget this :(  . On this kind of combination, when you will need to apply something like:  (initramfs - command ) never forget that grub is installed on boot sector of SSD but owner is another Linux. There are some of my posts(on this forum), when I have make the same mistakes(forgetting the grub owner) and how I resolve this problem.
When I installed Sparky64 bit on my SD Card 32 Gb (this laptop can be boot from SD Card natively), the grub was installed on the boot sector of SD Card. So,I only updated grub on MX Linux32 bit , but also on my SD Card from Sparky64 bit.On this way, I can play easily without having. a risk. When I want to test a new Linux Distro,I use half of my SD Card (16 gb) and during installing procedure I never install grub.When I finish installation, simply I open my MX Linux 32 bit or Sparky 64 bit and upgrade grub in able to catch the new Linux distro entry. With a good speed read/write SD Card on an refurbish machine like Lenovo X201i or Lenovo T410 (that can boot from SD Card) you do not need to have a SSD or HDD and Sparky32/Sparky 64 runs very fast.With this kind of machine build, you can have a very good/fast and cheap Linux Laptop.

[nickboyle]

Fortunately, you don't need to remove plymouth in order to disable it; there's a GRUB boot option called splash that can toggle the graphical boot screen on or off. (on a command-line-only system or any other Ubuntu variant, open a terminal and type sudo nano /etc/default/grub instead.) [copied from other source]