I update Tumbleweed daily. I have several luks encrypted drives to mount during boot. Over the last couple of days, Plymouth will prompt for my encryption password, but it apparently isn’t being passed on to the system. One of the partitions is my “home” partition. The others mount in subfolders of “home”. After a 4 minute delay I can hit the “enter” key and will be prompted by console for my passwords. Before I can complete them, the display manager appears for me to log in. Since “home” was never unlocked or mounted, it is a useless endeavor. For a workaround, I can log in as root, use Yast Partitioner to unlock all encrypted partitions, then run mount -a from a command line. At that point I can log out as root and log back into my user account. I am not sure if it’s a kernel issue or cryptsetup or even maybe Plymouth.
Maybe related…
https://bugzilla.opensuse.org/show_bug.cgi?id=1245163
Similar problem here, started yesterday.
After the grub bootloader normally I am asked for the /home password but not any longer. What I do is press escape and in the terminal that then is given there is password prompt. Giving the password there resumes the boot process.
The journal shows:
Jun 22 11:19:12 systemd[1]: Starting Cryptography Setup for cr-auto-1...
Jun 22 11:19:12 systemd[1]: Starting File System Check on /dev/disk/by-uuid/4b1b8b4c-5b37-4999-a57c-7408dc41d759...
Jun 22 11:19:12 systemd[1]: Starting File System Check on /dev/disk/by-uuid/CF52-CA15...
Jun 22 11:19:12 systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jun 22 11:19:12 systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
Jun 22 11:19:12 systemd[1]: Stopped Virtual Console Setup.
Jun 22 11:19:12 systemd[1]: Stopping Virtual Console Setup...
Jun 22 11:19:12 systemd[1]: Starting Virtual Console Setup...
Jun 22 11:19:12 systemd[1]: Finished File System Check on /dev/disk/by-uuid/4b1b8b4c-5b37-4999-a57c-7408dc41d759.
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd-vconsole-setup[939]: setfont: ERROR kdfontop.c:212 put_font_kdfontop: Unable to load such font with such kernel version
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
...
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd[1]: Forward Password Requests to Plymouth was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid).
Jun 22 11:19:12 systemd[1]: systemd-ask-password-plymouth.path: Trigger limit hit, refusing further activation.
Jun 22 11:19:12 systemd[1]: systemd-ask-password-plymouth.path: Failed with result 'trigger-limit-hit'.
Jun 22 11:19:12 systemd-vconsole-setup[932]: Setting source virtual console failed, ignoring remaining ones.
Jun 22 11:19:12 systemd[1]: Finished Virtual Console Setup.
Jun 22 11:19:12 systemd[1]: Started Dispatch Password Requests to Console.
Jun 22 11:19:12 systemd-tty-ask-password-agent[996]: Starting password query on /dev/tty1.
Strange to see that all has the same timestamp, I did wait ~10 seconds before I hit the Esc hey.
Seems to match what Aaron writes on the ticket.
Yep, that’s exactly the issue.
A workaround to speed up the boot process again (although it will still not be as fast as before) is to remove splash=silent quiet from the GRUB parameters and add plymouth.enable=0.
It worked for me but I think a real solution will come quite quickly.
That bug has meanwhile but closed as duplicate for:
https://bugzilla.suse.com/show_bug.cgi?id=1237564
The problem seems to be with systemd service dependencies.
A solution has been uploaded to the repos. plymouth 22.02.122+94.4bd41a3-17.1 and the associated packages pulled in with it solved the issues for me. Thanks to the maintainers.
Okay, good it was solved for you. Something changed also for me, a graphical prompt for the password pops up again once more.
Still things do not work for me as it should, if I type the password, I do not see the dots appearing, eventually I saw only one dot and after some time I was thrown into the console. There I saw the password prompt with all dots.
With new boot also the problem described above disappeared, likely I initially trigger problems because all the debugging I had enabled.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.