Comment # 24 on bug 966255 from Jacob W

I can confirm that Fabian's workaround from comment 23 does NOT work for me. It
changes nothing. cryptsetup, with or without plymouth still behaves like the
password prompt is NOT required (it background's the job indefinitely). So when
Plymouth is enabled, it crashes the boot process. The only solution is what I
have proposed in bug 942940#37 which is:

Remove kernel boot parameter "splash=silent" but keep "quiet". Without "quiet"
the job is ignored and put into the background.


Now I don't know if my system is suffering from this bug or bug 942940 or
possibly something else.


I am cross posting my issue from bug bug 942940 because it may help:

I am now experiencing a similar issue since TW update Build20160205, maybe one
previous, sure 100% sure. Before prompt worked great in TW and in 13.2.

I only have /home encrypted. LUKS without LVM. Both fstab and crypttab show the
correct disk id.

Password prompt is not shown and plymouth theme never shows up, instead it
freezes the system where VT switching does not work.

Forcing the system to boot without plymouth (press e on grub's kernel list)
shows what looks like cryptsetup trying to prompt for the password, but instead
instantly being backgrounded as a job. After more processes go through their
boot procedure, the boot process stops and looks frozen. If I press a button on
the keyboard, it forces the password prompt to re-appear. Now I can enter my
password and everything works from there.

I tried to add/remove nofail option (all 4 combinations) in both fstab and
crypttab, does not help.

I tried plymouth-set-default-theme -R <theme> and yast2 bootloader. Does not
help.

Adding x-systemd.device-timeout=15 to /etc/fstab from #963526 DOES NOT help or
fix this problem. Tried both plymouth and raw boot, nothing changed.


I'm attaching a photo (boot-screen-password-prompt-job-problem.jpg) I made of
the boot screen right before submitting password. Please note that the last
line, like mentioned above, only appears after hitting a key on the keyboard.
In other words, I have to force it to the foreground.