Package Details: plymouth 0.9.3-3

Git Clone URL: (read-only)
Package Base: plymouth
Description: A graphical boot splash screen with kernel mode-setting support
Upstream URL:
Licenses: GPL
Conflicts: plymouth-git, plymouth-legacy, plymouth-nosystemd
Provides: plymouth
Submitter: PirateJonno
Maintainer: nullptr_t
Last Packager: nullptr_t
Votes: 414
Popularity: 4.501925
First Submitted: 2009-08-12 04:16
Last Updated: 2017-09-21 17:24

Latest Comments

zeroxfourc commented on 2017-11-06 19:29

Hey, please consider using a stronger hash algoritm than MD5 (for example SHA256) and a HTTPS download link such as this one:

charlesmilette commented on 2017-10-15 19:08

With the gdm-plymouth service, it is impossible for me to use a TTY, because it shows me the following instead of a login prompt:

[*** ] A start job is running for Hold until boot process finishes up (system uptime here / no limit)

zerophase commented on 2017-10-15 14:28

Is anyone else getting a white screen when UEFI booting? The plymouth boot spinner comes up eventually, but only for a second or 2 before getting into the desktop.

After booting with rEFInd shouldn't the plymouth boot spinner come up right away?

nullptr_t commented on 2017-10-13 17:12

For anybody having troubles with plymouth themes after the new release from upstream, please refer to post #6 of this thread:

towo commented on 2017-09-22 07:31

@mtorromeo: Uuuh, that's way nicer. Didn't know about that one.

nullptr_t commented on 2017-09-21 17:14

@mtorromeo, @towo: I was going to place an "ExecStartPre = mkdir -m 755 -p /run/plymouth" into the [Service] section to address the pid file problem, but I think @mtorromeos solution is more pleasing fashion.

mtorromeo commented on 2017-09-21 17:01

@towo, @nullptr_t: Just add "RuntimeDirectory = plymouth" to the [Service] section of the systemd unit to delegate the creation of /run/plymouth to systemd.

towo commented on 2017-09-21 10:46

Cheers; when going for a complete systemd initramfs with sd-encrypt, systemd-ask-password-plymouth never starts up because it depends on a pidfile existing in /run/plymouth/; since the systemd hook initializes /run as tmpfs, the add_dir from the install script is useless.

My current würgaround is including a systemd service to create /run/plymouth if necessary (, but this should probably be fixed in a more pleasing fashion.

nullptr_t commented on 2017-09-06 08:38

Thanks, is changed in the 0.9.2-2 release.

digitalcube commented on 2017-09-05 18:27

I think there may be a small typo in plymouth.encrypt_hook line 79: ${cryptdev} should be ${resolved} like in the vanilla encrypt hook. That would allow PARTUUID to be used to identify the encrypted device.

All comments