On Mon, 2026-05-11 at 19:06 +0300, Askar Safin wrote: > > - Plymouth prefers not to use SimpleDRM devices. This is because they > > I just installed debian forky KDE using latest daily d-i from here: > > https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso > > I installed it to Qemu. I picked default answers to all questions asked by > d-i (except for one: I chose kde). > > In resulting system Plymouth was enabled, but it didn't show any actual > animation.
I know, our default theme is "text" for some reason. > I know that it is enabled, because early boot messages shown in cyan as > opposed to gray. > > So, why we enable Plymouth and deal with all plymouth pain if it doesn't > show any actual animation? (I don't see any value in cyan [as opposed to > gray] boot messages.) > > I think that for forky plymouth should be either disabled by default > (this will free us from a lot of plymouth-related problems), either > plymouth should show some real animation. (Personally I like first > option more, because I don't see a lot of value in boot animation.) My understanding is that Plymouth is needed for e.g. inputting the disk encryption password. But I never looked that deeply at how it's being used. In my opinion, when the desktop task is installed, Plymouth should be installed and configured to use the current release's theme, like GRUB and the desktop itself. But I think any change to that is separate from the SimpleDRM issue. Ben. -- Ben Hutchings - Debian developer, member of kernel, installer and LTS teams
signature.asc
Description: This is a digitally signed message part
