Package: plymouth Version: 0.9.5-3 Severity: important Hi there,
Activating Plymouth's pretty bootsplash graphics by adding "splash" to the default Linux commandline in /etc/default/grub worked as expected. Both plymouth-preview and an actual reboot showed the Debian "homeworld" default theme. So Plymouth is *working*. After changing to a different theme, eg `plymouth-set-default-theme -R glow`: * `plymouth-set-default-theme` reports "glow"; * lsinitramfs shows that /usr/share/plymouth/themes/glow *has* been copied into the initrd.img; * `plymouth-preview` still shows homeworld; * at shutdown, homeworld is still displayed; * at startup, after GRUB's message about loading the initramfs, I get a blank grey screen and an ugly un-styled LUKS prompt — not the black-background console-mode LUKS prompt from before activating Plymouth — I'd guess it's Plymouth's fallback mode for when no theme is available. Looking for hints in the logs, I found that journalctl contains these lines: Received SIGRTMIN+20 from PID 305 (plymouthd). Received SIGRTMIN+21 from PID 305 (plymouthd). Received SIGRTMIN+21 from PID 305 (plymouthd). I don't know what that means or whether it's significant, but nothing else looked out of place. "Starting Show Plymouth Boot Screen... Started Show Plymouth Boot Screen." etc. Changing back to homeworld the same way *does* have the expected result: * `plymouth-set-default-theme` reports "homeworld"; * `plymouth-preview` still shows homeworld; * lsinitramfs shows [...]themes/homeworld/ has been copied into the initrd.img; * at shutdown, homeworld is, unsurprisingly, still displayed; * At startup, I see the homeworld theme as expected, including nicely styled LUKS passphrase prompt. I have tried 3 different non-default themes, including glow which is installed from official Debian repo. All three resulted in the ugly grey fallback mode as described above during startup. I took a guess at severity "important" based on the reasoning that theming the bootup process is Plymouth's core purpose, so if you can't choose your theme, plymouth is failing at its core job. I assume you can adjust that if needed. I'm happy to provide more info if it'll help, though you may have to tell me where to dig. Is there a way to set Plymouth to debug-level verbosity and capture that in logs somewhere? Does the homeworld theme use some additional trick I should replicate? Cheers! -Chris -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-5-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plymouth depends on: ii init-system-helpers 1.60 ii initramfs-tools 0.139 ii libc6 2.31-9 ii libdrm2 2.4.104-1 ii libplymouth5 0.9.5-3 ii lsb-base 11.1.0 ii systemd 247.3-3 ii udev 247.3-3 plymouth recommends no packages. Versions of packages plymouth suggests: ii desktop-base 11.0.2 ii plymouth-themes 0.9.5-3 -- Configuration Files: /etc/plymouth/plymouthd.conf changed: ShowDelay=0 [Daemon] Theme=glow
