On Wed, Nov 25, 2015 at 09:38:29PM +0000, Ben Hutchings wrote: > > So this bug might deserve a reassign to plymouth, I guess.
Thanks for doing this, Ben. I'll eagerly wait feedback from the Plymouth maintainers on how to help them debug this further :) > > Still, why are kernels 4.2 and 4.3 triggering plymouth usage, whereas > > 4.1 is not? (FWIW, all my grub entries have "splash" on the kernel > > cmdline.) > > Perhaps you installed plymouth after Linux 4.2? Only the newest > initramfs is updated when you install plymouth (and most other > packages that trigger an initramfs update). No, that's not it. I've had Plymouth installed since ever. FWIW, here are the plymouth packages I've installed on my machine: dpkg -l '*plymouth*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=============================-===================-===================-================================================================ ii libplymouth4:amd64 0.9.2-3 amd64 graphical boot animation and logger - shared libraries ii plymouth 0.9.2-3 amd64 boot animation, logger and I/O multiplexer rc plymouth-drm 0.9.0-4 amd64 Graphical Boot Animation and Logger (DRM) un plymouth-theme <none> <none> (no description available) ii plymouth-themes 0.9.2-3 amd64 boot animation, logger and I/O multiplexer - themes un plymouth-themes-all <none> <none> (no description available) un plymouth-themes-fade-in <none> <none> (no description available) un plymouth-themes-glow <none> <none> (no description available) un plymouth-themes-script <none> <none> (no description available) un plymouth-themes-solar <none> <none> (no description available) un plymouth-themes-spinfinity <none> <none> (no description available) un plymouth-themes-spinner <none> <none> (no description available) ii plymouth-x11 0.9.2-3 amd64 boot animation, logger and I/O multiplexer - X11 renderer No idea why old kernel versions weren't calling plymouth to ask for the luks password. Just in case: is "dpkg --purge plymouth" supposed to be a safe way out of this bug these days? Or do we now require plymouth in order to be able to ask for luks password during boot? Cheers. -- Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Former Debian Project Leader . . . . . @zacchiro . . . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club »
