Package Details: plymouth 0.9.3-5

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, plymouth-legacy, plymouth-nosystemd
Provides: plymouth
Submitter: PirateJonno
Maintainer: nullptr_t
Last Packager: nullptr_t
Votes: 445
Popularity: 3.739032
First Submitted: 2009-08-12 04:16
Last Updated: 2018-08-24 03:10

Sources (19)

Latest Comments

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

nullptr_t commented on 2018-09-06 07:07

I recommend to decrease the number of --number-of-tries from the commit https://aur.archlinux.org/cgit/aur.git/commit/?h=plymouth&id=3f7e30ce4a77 .

nullptr_t commented on 2018-09-06 06:29

Yes, that is okay for me. Since the last release the package includes the first patch after the 0.9.3 release, a patch from a non-stable version, that was requested. The modifications in the releases since 0.9.3-1 where requested.

FFY00 commented on 2018-09-01 15:26

I am interested in moving this to [community]. Is this ok with you?

tintypemolly commented on 2018-08-13 06:30

I think the maintainer can update this package to include the #include <sys/sysmacros.h> patch. glibc recently made its major version upgraded 11 days ago in the Arch official repository, presumably removing the #include <sys/sysmacros.h> in its header. The patch itself made its way into the plymouth's official repo, but there has been no release since then. So, for the time being, there is no other way than patching it to make it build.

tintypemolly commented on 2018-08-13 06:04

@ABOhiccups Download the patch. Assuming path to the patch file is /path/to/sysmacros.patch, 1. Open PKGBUILD and look for prepare() function. 2. Append patch -p1 -i /path/to/sysmacros.path at the end of the function. 3. Do makepkg stuffs as usual.

ABOhiccups commented on 2018-08-12 20:09

@koassim How do I use a patch? This link is from Gentoo. We're on Arch Linux.

koassim commented on 2018-08-10 12:26

If you are unable to compile with the following error: /usr/bin/ld: libply-splash-core/.libs/libply-splash-core.so: undefined reference to minor' /usr/bin/ld: libply-splash-core/.libs/libply-splash-core.so: undefined reference tomajor'

Use the patch from here: https://bugs.gentoo.org/627690

rocky7x commented on 2018-07-24 14:58

Any idea how to get plymouth to show graphical password prompt for non-root luks partitions? plymouth-encrypt hook is not usable here and the only thing I get is the text password prompt "behind" the splash...

14mRh4X0r commented on 2018-06-09 18:50

Reloading systemd with systemctl daemon-reload triggers plymouth-start.service, hence switching to the boot splash. I'm a GNOME user, and when using X, switching back to the proper VT is all that's needed, but when using Wayland, switching back causes the following messages in the journal and needs a restart of gdm to recover:

Jun 09 20:34:13 vischium sudo[1775]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 09 20:34:13 vischium systemd[1]: Reloading.
Jun 09 20:34:14 vischium sudo[1775]: pam_unix(sudo:session): session closed for user root
Jun 09 20:34:14 vischium systemd[1]: Starting Setup Virtual Console...
Jun 09 20:34:14 vischium systemd[1]: Started Setup Virtual Console.
Jun 09 20:34:14 vischium systemd[1]: Starting Show Plymouth Boot Screen...
Jun 09 20:34:14 vischium systemd[1]: Received SIGRTMIN+20 from PID 1824 (plymouthd).
Jun 09 20:34:14 vischium systemd[1]: Started Show Plymouth Boot Screen.
Jun 09 20:34:14 vischium kernel: rfkill: input handler enabled
Jun 09 20:34:15 vischium gnome-shell[634]: Failed to apply DRM plane transform 0: Permission denied
Jun 09 20:34:15 vischium gnome-shell[634]: Failed to set power save mode for output eDP-1: Permission denied
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: > Warning:          Unsupported maximum keycode 374, clipping.
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: >                   X11 cannot support keycodes above 255.
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: > Warning:          Unsupported high keycode 372 for name <I372> ignored
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: >                   X11 cannot support keycodes above 255.
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: >                   This warning only shows for the first high keycode.
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: > Internal error:   Could not resolve keysym XF86WWAN
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: > Internal error:   Could not resolve keysym XF86RFKill
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: > Internal error:   Could not resolve keysym XF86Keyboard
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: Errors from xkbcomp are not fatal to the X server
Jun 09 20:34:15 vischium gnome-shell[634]: Failed to set CRTC mode 1920x1080: Permission denied
Jun 09 20:34:15 vischium kernel: gnome-shell[634]: segfault at 20 ip 00007f38fb899d37 sp 00007ffcc8b73610 error 4 in libmutter-2.so.0.0.0[7f38fb794000+183000]
Jun 09 20:34:15 vischium systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Jun 09 20:34:15 vischium systemd[1]: Started Process Core Dump (PID 1829/UID 0).
Jun 09 20:34:15 vischium org.gnome.Shell.desktop[634]: (EE) failed to read Wayland events: Broken pipe
Jun 09 20:34:15 vischium gnome-session[626]: gnome-session-binary[626]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jun 09 20:34:15 vischium polkitd[574]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.30, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus)
Jun 09 20:34:15 vischium gnome-session-binary[626]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jun 09 20:34:15 vischium gnome-session-binary[626]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jun 09 20:34:15 vischium at-spi-bus-launcher[679]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1024"
Jun 09 20:34:15 vischium at-spi-bus-launcher[679]:       after 21 requests (21 known processed) with 0 events remaining.
Jun 09 20:34:16 vischium systemd-coredump[1830]: Process 634 (gnome-shell) of user 120 dumped core.

This makes plymouth rather unusable for me, but I do like my boot splash. Is it something with my configuration or is it something with plymouth?

For completeness' sake, this is what happens when booted with plymouth.enable=0:

Jun 09 20:37:46 vischium sudo[1618]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 09 20:37:46 vischium systemd[1]: Reloading.
Jun 09 20:37:46 vischium sudo[1618]: pam_unix(sudo:session): session closed for user root
Jun 09 20:37:46 vischium systemd[1]: Starting Setup Virtual Console...
Jun 09 20:37:46 vischium systemd[1]: Started Setup Virtual Console.

minextu commented on 2018-04-25 14:51

Please add libgcc_s.so.1 to the plymouth-encrypt hook. See line 22 in https://git.archlinux.org/svntogit/packages.git/tree/trunk/install-encrypt?h=packages/cryptsetup