Package Details: plymouth-git 24.004.60.r19.g954abd07-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: 276
Popularity: 0.032331
First Submitted: 2009-05-02 09:53 (UTC)
Last Updated: 2024-02-26 16:48 (UTC)

Required by (172)

Sources (6)

Latest Comments

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

Lutrim commented on 2022-08-10 08:21 (UTC) (edited on 2022-08-10 08:24 (UTC) by Lutrim) 

~/» sudo mkinitcpio -P              
==> Building image from preset: /etc/mkinitcpio.d/linux-libre.preset: 'default'
  -> -k /boot/vmlinuz-linux-libre -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-libre.img
==> Starting build: 5.18.14-gnu-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [plymouth]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [plymouth-encrypt]
==> ERROR: file not found: `/usr/share/fonts/cantarell/Cantarell-Thin.otf'
==> ERROR: file not found: `/usr/share/fonts/cantarell/Cantarell-Regular.otf'
  -> Running build hook: [lvm2]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-libre.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux-libre.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-libre -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-libre-fallback.img -S autodetect
==> Starting build: 5.18.14-gnu-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [plymouth]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: isci
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [plymouth-encrypt]
==> ERROR: file not found: `/usr/share/fonts/cantarell/Cantarell-Thin.otf'
==> ERROR: file not found: `/usr/share/fonts/cantarell/Cantarell-Regular.otf'
  -> Running build hook: [lvm2]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-libre-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
~/»

Installing cantarell-fonts does not change anything...

daenney commented on 2022-07-29 14:47 (UTC)

Whatever it was, it seems to have fixed itself. I wonder if I ended up forgetting to rebuild something, but I'm positive I rebuilt plymouth-git first and then gdm-plymouth before rebuilding the initramfs. The only real change between then and now is a slightly newer kernel.

For reference, the hardware in this case was a Lenovo IdeaPad 5 Pro 14ACN6. Initcpio is a systemd based stack (HOOKS=(base systemd keyboard sd-plymouth autodetect sd-vconsole modconf sd-encrypt fsck filesystems)) with amdgpu as the first entry in MODULES.

Taijian commented on 2022-07-22 20:56 (UTC)

@daenney: Also helpful would be some information about your hardware setup (NVIDIA?) and your mkinitcpio.conf.

whynothugo commented on 2022-07-22 18:56 (UTC)

@daenney Can you post logs from journalctl? You might still have the ones for last time you tried; you'll need to use journalctl --since XXX --until YYY.

That should point out what's failing.

daenney commented on 2022-07-22 17:21 (UTC)

Since 22.02.122.r48.g9e72df3d I can't boot with plymouth-git anymore. It gets past the sd-encrypt prompt, but at some point something locks, gdm doesn't launch and nothing responds to input anymore. I've rebuilt gdm-plymouth too and rebuilt the initramfs, but no dice. I get a kernel oops when booting with it. If I disable plymouth things boot just fine.

Reverting to 22.02.122.r2.g716b5bd solved the issue for me, but I'm entirely unclear as to why.

dacioromero commented on 2022-07-19 19:17 (UTC)

There was an update to plymouth making --with-runtimedir obsolete. https://gitlab.freedesktop.org/plymouth/plymouth/-/commit/9e72df3d8ada4767e418b3efebe7d96fc9eb439f

Switching it to --runstatedir seems to do the trick, but I'm not sure if they're strictly equivalent.

diff --git a/PKGBUILD b/PKGBUILD
index ecaa0a2..82eb13e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,7 +4,7 @@
 #               Lara Maia, Padfoot, Jorge Barroso, carstene1ns, Sebastian Lau

 pkgname=plymouth-git
-pkgver=22.02.122.r2.g716b5bd
+pkgver=22.02.122.r48.g9e72df3d
 pkgrel=1
 pkgdesc="A graphical boot splash screen with kernel mode-setting support (Development version)"
 url="https://www.freedesktop.org/wiki/Software/Plymouth/"
@@ -88,7 +88,7 @@ build() {
        --with-background-end-color-stop=0x4D4D4D \
        --without-rhgb-compat-link \
        --without-system-root-install \
-       --with-runtimedir=/run
+       --runstatedir=/run

    make
 }

michaldybczak commented on 2022-03-15 19:21 (UTC)

@Taijian, the problem with documentation is that it's never 100% clear for regular users as me. Arch wiki is also often very badly written, in a dry, technical, manner, assuming some greater, wider knowledge.

From my point of view it looks like that: the package worked well for years, and now it stopped. I don't know what changed and where to look.

I have two options. Either I try to find some answers, so I could fix the issue, or give up on the package, since it became worthless to me. The fact that it worked well, and I was even able once to find and report a bug that was later fixed, shows that, even regular users as me, could provide something valuable. However, we can't do that if we have no support. I'm used to troubleshooting myself, but in this case, this is too obscure to know where to start. Maybe if I searched and red for hours, I would figure it out. I don't have that kind of time, whereas for someone familiar, it's quicker to process information from me and point me toward the solution. I know, I know, everybody is busy and that is why, I don't expect quick answers. As you said, there is little incentive to help individual users (which is a pity, but this is how it is), so possibly I won't get much help or at all, but I can at least try.

sjnims commented on 2022-03-15 02:21 (UTC) (edited on 2022-03-15 02:25 (UTC) by sjnims)

@Taijian, I switched to using a similar boot configuration as you, so instead of using udev and GRUB, I'm now using systemd-style init, and booting from efistub. However, still not getting the Fedora-style unencrypt screen. My efistub parameters are as follows:

efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "Arch Linux" \
--loader /vmlinuz-linux-zen --unicode 'initrd=\intel-ucode.img \
initrd=\initramfs-linux-zen.img rd.luks.name=<UUID of 2nd nvme partition>=cryptroot \
root=UUID=<UUID of cryptroot> rootflags=rw,subvol=@' --verbose

Boots much faster than w/ GRUB, and I don't see any console messages at all now which is a plus, but as I mentioned, still no Fedora-style. Look forward to hearing what you find out!

sjnims commented on 2022-03-14 21:19 (UTC) (edited on 2022-03-14 21:19 (UTC) by sjnims)

@Taijian, it also doesn't help that Fedora uses dracut vs mkinitcpio to generate their initramfs...makes it harder to peek at what they're doing! :P

Taijian commented on 2022-03-14 20:45 (UTC)

@michaldybczak: Since the info I asked you for is very specific to Arch (and derivatives), I do not think that upstream will find your bug report very interesting/helpful. I does however suggest to me that you have not yet fully read through the wiki pages for mkinitcpio.conf or GRUB.

Please do so and then come back with the info I asked for.

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