Hello,
I’m under Tumbleweed Slowroll and I have a luks partition which is mounted at boot. In fact, I have a crypttab file in /etc, a line in /etc/fstab and everything did work fine for some years. I had also plymouth install. But since the last update, no password is asked at boot so Plasma is not launched. I have to wait to enter administrator mode in a console, enter my password for root, enter exit and then Plasma is launched. I’ve disabled Plymouth, it boots in text mode but no password is asked for the luks partition (so a start job is running for that partition). I’ve found a workaround. I have to press a key and then it ask for the luks password.
I had encountered the same problem some years ago and had the distribution reinstalled.
Has someone encountered the same problem ?
Thanks in advance.
Three bugs reported on this, including the one above. The active bug is:
https://bugzilla.suse.com/show_bug.cgi?id=1237564
To me it looks like the problem is that plymouth is restarted during boot and the process to ask the password is confused by that.
A working but not that nice work-around: Add plymouth.enable=0 to the boot line.
Yes, many thanks for your answers.
I think that’s it and I’ll follow these bugs.
Following as well, currently stuck on an older June 2025 snapshot because of this
The problem is gone (at least) as the commit has been reverted ~ 1 Jul.
With it I have back:
/usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd’s process lifecycle management for the service. Please update the service to use a safer KillMode=, such as ‘mixed’ or ‘control-group’. Support for KillMode=none is deprecated and will eventually be removed.
And the underlying problem is not really solved.
Did you read past comment #42?
Yes I did, I added comments #46, #48, #50, #53-55, #61, #62, #70,#71, #74 and recently #82.
My understanding, based on your analysis, is that it would be good to disable the YaST2-Firstboot.service, at least after the first boot.