Package Details: plymouth 0.9.4-7

Git Clone URL: (read-only, click to copy)
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: 498
Popularity: 6.55
First Submitted: 2009-08-12 04:16
Last Updated: 2020-04-09 06:49

Dependencies (6)

Required by (123)

Sources (18)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

rhysperry111 commented on 2020-05-28 08:11

@gui_user It should work if you follow the instructions at

gui_user commented on 2020-05-28 08:05

Is this working on a default installation?

rhysperry111 commented on 2020-05-26 09:40

Hi, is anyone else having problems booting with encrypted root?

If I unlock while plymouth is running it hangs, but if I press esc and then unlock my boot works normally

ZinStack commented on 2020-04-16 19:53

Not sure if anyone noticed, but getty cannot start because plymouth-quit-wait.service hangs the system in a starting state. Stopping it manually will kinda fix it, it will drop out of session and will need to restart gdm-plymouth to log back in, perhaps just unexpected system state change or some gnome stuff idk. Not critical, but very annoying

avrelaun commented on 2020-04-08 15:31

@nullptr_t while you're at it, could you please update the old arch logo and replace it with the new one ? Here's the one I made and used for a while now, specifically sized to be a drop-in replacement in /usr/share/plymouth/arch-logo.png, and it's also a transparent png:

n34r1297 commented on 2020-04-04 22:26

@nullptr_t please add RemainAfterExit=true to plymouth-start.service and plymouth-read-write.service. This can be easily done with a patch.

avrelaun commented on 2020-04-01 16:31

As suggested in the systemd previouly mentionned, adding RemainAfterExit=yes on both plymouth-start.service and plymouth-read-write.service fixes the problem. This package service files need to be updated to fix it for all users.

Subs commented on 2020-03-20 12:12

Hi, Since systemd 245, plymouth start screen never stops. See issue (direct link to the fix) here

diabonas commented on 2020-03-11 11:13

@TheJackiMonster patch and autoconf are part of the base-devel group, which is assumed to be always installed when building packages. They should never be included in makedepends.

RealOrRandom commented on 2020-03-11 10:23

If (after the systemd update to v245) you suffer from a bug that the plymouth screen appears at random times even after the boot process has completed and renders your system unusable, one of the following workarounds is sufficient:

  • Add the line "RemainAfterExit=yes" to the [Service] section in /usr/lib/systemd/system/plymouth-start.service OR
  • "sudo systemctl mask plymouth-start.service" (and unmask after the issue has been fixed in plymouth)

Plymouth will be fixed soon, see