Package Details: plymouth 0.9.4-4

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: 470
Popularity: 3.472501
First Submitted: 2009-08-12 04:16
Last Updated: 2019-03-01 12:49

Dependencies (6)

Sources (17)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

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.

r3b311i0n commented on 2017-08-24 03:02

No services are duplicated, it just shows the same message twice before "Started Deactivate Plymouth Boot Screen", and I don't have any HOOKs set twice. Also, if I use official gdm instead of gdm-plymouth, the duplication doesn't occur.

nullptr_t commented on 2017-08-23 21:58

I could not find any duplications in there (by human eyes). The journal messages are following the scheme

t - Mounting /mnt/data...
t+x - Mounted /mnt/data

If your boot screen output differs from log: Does your initcpio maybe have a HOOK set twice (/etc/mkinitcpio.conf)?

r3b311i0n commented on 2017-08-19 01:33

Thanks for the reply @nullptr_t

It's an HP Envy 15.
HD4600 (modesetting driver) + GeForce GT-740m using nvidia proprietary with Bumblebee + bbswitch.
Bootloader: systemd-boot

kernel params:

root=PARTUUID=02531cbb-14c0-4888-b1e3-a096e60d1106 quiet splash loglevel=3 acpi_backlight=vendor nvidia-drm.modeset=1 rw

Journal for systemd -

The issue is very similar to this
I've tried with the nvidia card on both early and late KMS with the same result.
I've also noticed that the last few service messages (the ones after "Started Deactivate Plymouth Boot Screen") do not get duplicated.

Thanks again for the help :)

nullptr_t commented on 2017-08-18 13:52

Can you provide some more details on journal and configuration please?

r3b311i0n commented on 2017-08-18 12:13

I'm getting duplicated boot messages after the 0.9.3-1 upgrade.

> Optimus system.
> Using gdm-plymouth.

Downgrading to 0.9.2-14 fixes this.

sovanyio commented on 2017-08-16 20:25

@Aetf, odd it worked for me here and for plymouth-git. The add_full_dir command is probably cleaner anyway.

Aetf commented on 2017-08-16 18:09

@sovanyio, @nullptr_t

This doesn't work for me. Still only normal files were added to initcpio.

Here's the gist I'm using:

Note the add_full_dir call replaced the whole for loop.


nullptr_t commented on 2017-08-16 07:14

Thanks to both! The patch is included in the new release.