Package Details: plymouth 0.9.2-9

Git Clone URL: https://aur.archlinux.org/plymouth.git (read-only)
Package Base: plymouth
Description: A graphical boot splash screen with kernel mode-setting support
Upstream URL: http://www.freedesktop.org/wiki/Software/Plymouth/
Licenses: GPL
Conflicts: plymouth-git
Provides: plymouth
Submitter: PirateJonno
Maintainer: nullptr_t
Last Packager: nullptr_t
Votes: 361
Popularity: 7.606980
First Submitted: 2009-08-12 04:16
Last Updated: 2016-05-07 15:05

Latest Comments

morealaz commented on 2016-08-11 12:08

excellent Notes @mjkillough
I think these notes which you mention must be included in wiki and also plymouth-deactivate.service must be included in this package.
I use them and worked perfectly for me.

mjkillough commented on 2016-08-07 11:46

I have written some notes about getting a seamless Plymouth to X transition: https://github.com/mjkillough/notes/blob/master/boot-experience.md

As described in [0], it seems the intended way to get a seamless transition is to call `plymouth deacivate` before starting X (rather than `plymouth quit`, as the .service scripts in this package do). I've created a `plymouth-deactivate.service` for this purpose, which is available in my notes above.

I'm still tweaking, but will eventually try to get my notes onto the wiki. Perhaps it would be worth including the `plymouth-deactivate.service` script in this package so it is easier for others to use?

[0] https://lists.freedesktop.org/archives/plymouth/2014-March/000753.html

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:
https://wiki.archlinux.org/index.php/Unofficial_user_repositories#nullptr_t

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

[nullptr_t]
SigLevel = Optional TrustedOnly
Server = https://www.slau.me/archlinux/mirrors/$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 (initrd-switch-root.target.wants , sysinit.target.wants)
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:
[Install]
WantedBy=sysinit.target
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 https://ptpb.pw/je1W.path as plymouth-start.path and add plymouth-start.path to the list of units to add in plymouth.initcpio_install.

All comments