Debian User Forums

About plymouth : https://wiki.debian.org/plymouth

probably has to do with the fact that for all my installations of Debian I use the /unofficial/non-free/cd-including-firmware/current-live/amd64/iso-hybrid/ , but apparently this ISO installs/activates the following packages by default : libplymouth5 / plymouth / plymouth-label version 0.9.5-3 ?

until now NEVER caused any problems , I have to say that I do not use the possibilities that this application offers for graphical enhancement ... personally I do not see the use of it … that’s me .

So ask me the question , given the admittedly rare ? problems that this application can cause ( for example when upgrading the kernel ) , do I as well preventively may / can deactivate ( synaptic ) these packages ?

am I overlooking something ?

thank you

Translated with www.DeepL.com/Translator (free version)

These are things I personally deinstall (boot being so fast nowadays). I generally try to get rid of things I don't use.

fabien wrote: ↑2022-05-09 14:26 These are things I personally deinstall (boot being so fast nowadays). I generally try to get rid of things I don't use.

Thank you fabien
What was in my mind when I started this topic was actually following annoying phenomenon :
On 3 of our laptops ( always been so ) during the boot process a laundry list of " ACPI BIOS ERROR (bug) pass by .
Sometimes I manage to take a picture of them (they pass by very quickly), at least if I want to know what's in it , for example :

Following a few topics, my attention was drawn to the "plymouth" application and secretly hoped to correct this message or at least to help to get rid of it .
After some research I found out that there is no way to remove these messages but also that I can simply ignore them as the computers are working properly .

Have no further questions regarding Plymouth .

edit :
Outdated / no longer in force : https://askubuntu.com/questions/54176/w ... ired#55023

I followed your advice and “ purged “ plymouth on all our laptops .

Translated with www.DeepL.com/Translator (free version)

Fossy wrote: ↑2022-05-10 11:24Outdated / no longer in force : https://askubuntu.com/questions/54176/w ... ired#55023

Interesting, thanks for this link. I must admit that I wondered why plymouth was installed but without the graphical configuration that, in my mind, would justify it. And I didn't investigate further.
Not sure that it is outdated. Those who use encrypted file systems should ponder whether or not they keep it.
plymouth package description:

Plymouth provides a boot-time I/O multiplexing framework - the most obvious use for which is to provide an attractive graphical animation in place of the text messages that normally get shown during boot. (The messages are instead redirected to a logfile for later viewing.) However, in event-driven boot systems Plymouth can also usefully handle user interaction such as password prompts for encrypted file systems.

fabien wrote: ↑2022-05-12 14:19

Fossy wrote: ↑2022-05-10 11:24Outdated / no longer in force : https://askubuntu.com/questions/54176/w ... ired#55023

Interesting, thanks for this link. I must admit that I wondered why plymouth was installed but without the graphical configuration that, in my mind, would justify it. And I didn't investigate further.
Not sure that it is outdated. Those who use encrypted file systems should ponder whether or not they keep it.
plymouth package description:

Plymouth provides a boot-time I/O multiplexing framework - the most obvious use for which is to provide an attractive graphical animation in place of the text messages that normally get shown during boot. (The messages are instead redirected to a logfile for later viewing.) However, in event-driven boot systems Plymouth can also usefully handle user interaction such as password prompts for encrypted file systems.

seems to me to be purely a graphical embellishment / personalization of the boot process ? ( 10.3 and following ) : https://access.redhat.com/documentation ... e/plymouth

if it is the case that removing / not having plymouth in use would be irresponsible then I do expect clarification on this from the corner of the insiders ... may I assume that ?

Fossy wrote: ↑2022-05-12 18:24seems to me to be purely a graphical embellishment / personalization of the boot process ? ( 10.3 and following ) : https://access.redhat.com/documentation ... e/plymouth

This chapter says this in its introduction though:

Plymouth also handles user interaction during boot.

but it does not elaborate on it after.

Fossy wrote: ↑2022-05-12 18:24if it is the case that removing / not having plymouth in use would be irresponsible then I do expect clarification on this from the corner of the insiders ... may I assume that ?

I would often very much like to get clarification from the corner of the insiders

The last time I used an encrypted filesystem was on a laptop with Wheezy, and Wheezy is the last Debian without systemd as default. At this time there was no problem to enter passwords without plymouth, but as I have not tested since, I prefer pointing out this potential question.

I uninstalled everything plymouth-related years ago and I've never noticed any issues.

Cyborg wrote: ↑2022-05-14 21:04 I uninstalled everything plymouth-related years ago and I've never noticed any issues.

I did the same. Never saw any real use for Plymouth.

Cyborg wrote: ↑2022-05-14 21:04I uninstalled everything plymouth-related years ago and I've never noticed any issues.

ticojohn wrote: ↑2022-05-15 20:38I did the same. Never saw any real use for Plymouth.

Thanks, but you didn't say whether you were using encrypted filesystem.

Sorry, I missed that part.
No, I don't use encryption.

We don’t use encryption ...

We purged plymouth on all our laptops

/var/log/boot.log :
with the 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux :
Starting #[0;1;39mNetwork Manager Script Dispatcher Service#[0m...
[#[0;32m OK #[0m] Started #[0;1;39mNetwork Manager Script Dispatcher Service#[0m.
[#[0;1;31mFAILED#[0m] Failed to start #[0;1;39mRaise network interfaces#[0m.
See 'systemctl status networking.service' for details.
[#[0;32m OK #[0m] Reached target #[0;1;39mNetwork#[0m.
Starting #[0;1;39mCUPS Scheduler#[0m...
Starting #[0;1;39mPermit User Sessions#[0m...
[#[0;32m OK #[0m] Started #[0;1;39mUnattended Upgrades Shutdown#[0m.
[#[0;32m OK #[0m] Finished #[0;1;39mPermit User Sessions#[0m.
Starting #[0;1;39mLight Display Manager#[0m...
Starting #[0;1;39mHold until boot process finishes up#[0m...
[#[0;32m OK #[0m] Started #[0;1;39mCUPS Scheduler#[0m.
[#[0;32m OK #[0m] Started #[0;1;39mMake remote CUPS printers available locally#[0m.
[#[0;32m OK #[0m] Finished #[0;1;39mRotate log files#[0m.
/var/log/boot.log :
With the 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 GNU/Linux
Starting #[0;1;39mNetwork Manager Script Dispatcher Service#[0m...
[#[0;32m OK #[0m] Started #[0;1;39mNetwork Manager Script Dispatcher Service#[0m.
[#[0;1;31mFAILED#[0m] Failed to start #[0;1;39mRaise network interfaces#[0m.
See 'systemctl status networking.service' for details.
[#[0;32m OK #[0m] Reached target #[0;1;39mNetwork#[0m.
Starting #[0;1;39mCUPS Scheduler#[0m...
Starting #[0;1;39mPermit User Sessions#[0m...
[#[0;32m OK #[0m] Started #[0;1;39mUnattended Upgrades Shutdown#[0m.
[#[0;32m OK #[0m] Finished #[0;1;39mPermit User Sessions#[0m.
Starting #[0;1;39mLight Display Manager#[0m...
Starting #[0;1;39mHold until boot process finishes up#[0m...
[#[0;32m OK #[0m] Started #[0;1;39mCUPS Scheduler#[0m.
[#[0;32m OK #[0m] Started #[0;1;39mMake remote CUPS printers available locally#[0m.
[#[0;32m OK #[0m] Finished #[0;1;39mRotate log files#[0m.

and they are all are working properly ( wireless ) , but nevertheless continue to watch your comments with interest

edit : Systemd-analyze ( seems pretty acceptable to me ) :
Startup finished in 5.648s (firmware) + 2.928s (loader) + 3.640s (kernel) + 8.757s (userspace) = 20.974s
graphical.target reached after 8.734s in userspace

back to square one ,
considering I'm an ordinary " home user " , read ... ( with all due respect to ) , not a tinker / tweaker and mindful of the principle : “ https://wiki.debian.org/DontBreakDebian “
and in practice I can only conclude that whether or not plymouth is in use has no impact on the proper functioning of our systems I finally decided to put plymouth back in use .
I clear the space for the " encrypters “

Translated with www.DeepL.com/Translator (free version)