Package Details: plymouth 0.9.2-9

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
Provides: plymouth
Submitter: PirateJonno
Maintainer: nullptr_t
Last Packager: nullptr_t
Votes: 354
Popularity: 5.514085
First Submitted: 2009-08-12 04:16
Last Updated: 2016-05-07 15:05

Sources (16)

  • arch-logo.png
  • gdm-plymouth.service
  • kdm-plymouth.service
  • lightdm-plymouth.service
  • lxdm-plymouth.service
  • plymouth-start.path
  • plymouth-start.service
  • plymouth-update-initrd.patch
  • plymouth.encrypt_hook
  • plymouth.encrypt_install
  • plymouth.initcpio_hook
  • plymouth.initcpio_install
  • slim-plymouth.service

Latest Comments

Koterpillar commented on 2016-06-29 08:08

With Infinality installed, I get:

-> Running build hook: [plymouth-encrypt]
==> ERROR: file not found: `/etc/fonts/conf.d/60-latin.conf'

nullptr_t commented on 2016-03-27 10:37

This works: cryptdevice=UUID=xxxxx

hexchain commented on 2016-03-26 10:32

Using a cryptdevice=PARTUUID=xxxxx parameter works with encrypt hook but not plymouth-encrypt.

nullptr_t commented on 2016-01-08 20:50

I've got the repo up and running again, but the URL changed:

nullptr_t commented on 2015-12-12 17:57

NOTE: If you are using my mirror, the repo name changed to nullptr_t to reflect username change

nullptr_t commented on 2015-12-10 21:02

You can now get this package prebuild, signed and secured from my repo here by adding the following to /etc/pacman.conf

SigLevel = Optional TrustedOnly
Server =$repo/$arch

The key-id is 1607AC45
armv6h might follow when I have more time.

swiftgeek commented on 2015-11-26 14:31

Sadly mentioned path file doesn't do anything (even with path changed to bogus one, ofc inside initrd)
EDIT1: Ok i think i made it work, by removing plymouth-start symlinks in *.wants/ and putting path files symlinks in them ( ,
Now this will start service after first drm based fb is made - so probably that has to be fixed by user passing earlymodules in kcmd (is that still working on systemd based initrd?). [This is for intel+radeon/nvidia optimus-like notebooks and more]
EDIT2: I had to also remove those lines from plymouth-start.service:
WantedBy seems to be redundant to the directory in edit above

Now it looks like i'm back in square one - sysfs doesn't seems to be available this early so i'm slightly out of ideas on detecting vesafb->drm
Or inotify isn't kicking in fast enough (not much idea on how to debug)
Important notes:
• text splash is evil and is going to damage ttys in one way or another WITHOUT providing any eye candy whatsoever
Even fedora isn't using this particular theme/engine as fallback!
• *DM and plymouthd have to be started on the same tty - it can be changed in either of them - otherwise you won't get smooth transition in eg. lightdm
"X -background none" is also helping with having smooth transition.
• If your *DM is starting one X for greeter (login prompt) and starting another for the user you can expect KD_GRAPHICS->KD_TEXT->KD_GRAPHICS and there is *probably* nothing you can do about that (or you can workaround by reusing the X server).
• If plymouth is crashing during boot, not passing splash isn't going to help - you need to boot with initrd without plymouth in such case. (crash of plymouth can cause unusable mouse/ctrl,backspace,escape)
• In order to not have plymouth inside fallback initrd add plymouth hook after -S in fallback_options in /etc/mkinitcpio.d/linux.preset
eg. fallback_options="-S plymouth,autodetect,keymap,consolefont -A keyboard"

Celti commented on 2015-11-26 04:07

Actually, reconsidering that unit add-in. I think that might just keep it from triggering at all. Instead, let's try this:

Save as plymouth-start.path and add plymouth-start.path to the list of units to add in plymouth.initcpio_install.

Celti commented on 2015-11-26 03:55

Also, regarding encryption, you shouldn't need the plymouth-encrypt hook at all, even with the systemd units added — what you do need is sd-encrypt, because that's what has all the fancy systemd cryptsetup generators.

Celti commented on 2015-11-26 03:53

Glad to hear my work is now “official”! :)

Back when I was using it it “just worked”, no need to wait for the drivers, but to make the appropriate units trigger on the existence of the path, --REMOVED because I'm an idiot and write things that don't work, see above--

All comments