Package Details: plymouth-git 24.004.60.r34.gedc7c3ea-1

Git Clone URL: https://aur.archlinux.org/plymouth-git.git (read-only, click to copy)
Package Base: plymouth-git
Description: Graphical boot splash screen (git version)
Upstream URL: https://www.freedesktop.org/wiki/Software/Plymouth/
Licenses: GPL-2.0-or-later
Conflicts: plymouth
Provides: plymouth
Submitter: PirateJonno
Maintainer: Taijian
Last Packager: Taijian
Votes: 274
Popularity: 0.021519
First Submitted: 2009-05-02 09:53 (UTC)
Last Updated: 2024-05-17 07:42 (UTC)

Required by (174)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 51 Next › Last »

sjnims commented on 2022-03-11 17:32 (UTC)

Thanks for maintaining this for us! Question: is there a way to grab the changes that Hans de Goede has in his fork for Fedora 35 (https://gitlab.freedesktop.org/jwrdegoede/plymouth/)? He made some changes to how the Plymouth themes display the text box for entering the password to unencrypt an encrypted drive (see https://www.reddit.com/r/Fedora/comments/t6yt4i/fedora_vs_ubuntu_plymouth_differences/ for sample pictures). I guess it stems from changes Hans made as he details in a blog post here: https://hansdegoede.livejournal.com/22565.html. Fedora actually uses Hans' fork for the F35 release, see the rpm spec here: https://src.fedoraproject.org/rpms/plymouth/blob/f35/f/plymouth.spec.

cthulhaire commented on 2022-01-30 21:57 (UTC)

I made a small change to the plymouth-encrypt hook which allows it to skip the password prompt if the root device has already been decrypted earlier.

diff --git a/plymouth.encrypt_hook b/plymouth.encrypt_hook
index 8acb9af..97b1c45 100644
--- a/plymouth.encrypt_hook
+++ b/plymouth.encrypt_hook
@@ -69,29 +69,33 @@ EOF
     if resolved=$(resolve_device "${cryptdev}" ${rootdelay}); then
         if cryptsetup isLuks ${resolved} >/dev/null 2>&1; then
             [ ${DEPRECATED_CRYPT} -eq 1 ] && warn_deprecated
-            dopassphrase=1
-            # If keyfile exists, try to use that
-            if [ -f ${ckeyfile} ]; then
-                if eval cryptsetup --key-file ${ckeyfile} luksOpen ${resolved} ${cryptname} ${cryptargs} ${CSQUIET}; then
-                    dopassphrase=0
-                else
-                    echo "Invalid keyfile. Reverting to passphrase."
-                fi
-            fi
-            # Ask for a passphrase
-            if [ ${dopassphrase} -gt 0 ]; then
-                echo
-                echo "A password is required to access the ${cryptname} volume:"
-                plymouth ask-for-password --prompt="Password for ${cryptname} volume" --dont-pause-progress --number-of-tries=5 --command="/sbin/cryptsetup luksOpen --key-file=- ${resolved} ${cryptname} ${cryptargs} ${CSQUIET}"
-                sleep 2
-            fi
+            # Check whether device has already been decrypted
             if [ -e "/dev/mapper/${cryptname}" ]; then
-                if [ ${DEPRECATED_CRYPT} -eq 1 ]; then
-                    export root="/dev/mapper/root"
-                fi
+                echo "${cryptname} already unlocked, continuing..."
             else
-                err "Password succeeded, but ${cryptname} creation failed, aborting..."
-                exit 1
+                dopassphrase=1
+                # If keyfile exists, try to use that
+                if [ -f ${ckeyfile} ]; then
+                    if eval cryptsetup --key-file ${ckeyfile} luksOpen ${resolved} ${cryptname} ${cryptargs} ${CSQUIET}; then
+                        dopassphrase=0
+                    else
+                        echo "Invalid keyfile. Reverting to passphrase."
+                    fi
+                fi
+                # Ask for a passphrase
+                if [ ${dopassphrase} -gt 0 ]; then
+                    echo "A password is required to access the ${cryptname} volume:"
+                    plymouth ask-for-password --prompt="Password for ${cryptname} volume" --dont-pause-progress --number-of-tries=5 --command="/sbin/cryptsetup luksOpen --key-file=- ${resolved} ${cryptname} ${cryptargs} ${CSQUIET}"
+                    sleep 2
+                fi
+                if [ -e "/dev/mapper/${cryptname}" ]; then
+                    if [ ${DEPRECATED_CRYPT} -eq 1 ]; then
+                        export root="/dev/mapper/root"
+                    fi
+                else
+                    err "Password succeeded, but ${cryptname} creation failed, aborting..."
+                    exit 1
+                fi
             fi
         elif [ -n "${crypto}" ]; then
             [ ${DEPRECATED_CRYPT} -eq 1 ] && warn_deprecated

whynothugo commented on 2021-12-12 02:03 (UTC)

Can gdm-plymouth.service be dropped?

The link is broken and systemd reports over and over this when applying presets.

It seems that it's no longer recommended or necessary anyway: https://aur.archlinux.org/packages/gdm-plymouth/#pinned-761822

hoban commented on 2021-11-09 16:31 (UTC)

I ran into the same issue as @medoix which was fixed on my end by manually deleting the directory ~/.cache/paru/clone/plymouth-git. Is there any easier way to clean build? Perhaps it was awkward on my end because of an issue on the Paru side? I did not have luck building this package after running paru -Sc, for what it's worth.

medoix commented on 2021-10-29 19:44 (UTC)

@Taijan A cleanBuild fixed it thanks! Always the simple things you forget to check.

Taijian commented on 2021-10-29 11:10 (UTC)

@medoix: Have you tried a clean build directory? Because it sure works for me...

medoix commented on 2021-10-29 07:35 (UTC) (edited on 2021-10-29 07:36 (UTC) by medoix)

Trying to update to 0.9.5.r84 and getting the following, any ideas?

==> Starting prepare()...
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -aur plymouth.src/scripts/plymouth-update-initrd plymouth.patch/scripts/plymouth-update-initrd
|--- plymouth.src/scripts/plymouth-update-initrd        2014-02-20 19:38:13.319427393 +1100
|+++ plymouth.patch/scripts/plymouth-update-initrd      2014-02-20 19:54:13.035553244 +1100
--------------------------
File to patch:

Taijian commented on 2021-07-09 11:26 (UTC) (edited on 2021-07-09 11:27 (UTC) by Taijian)

@whynothugo: Could you post your complete HOOKS entry from mkinitcpio.conf?

Also: What does your disc layout look like and are you sure that your initramfs is not on an encrypted partition?

whynothugo commented on 2021-07-08 16:06 (UTC)

I'm using the systemd hook, and adding the sd-encrypt hook did not work for me.

When the system starts, I get prompted for the disk password and plymouth starts after that.

d_fajardo commented on 2021-07-02 06:12 (UTC)

Any update on this infinite loop / trailing 0's?

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 51 Next › Last »