Red Hat Bugzilla – Bug 1277399
Plymouth LUKS password dialog disappears quickly on boot of live usb
Last modified: 2016-07-19 14:24:49 EDT
Description of problem:
When copying a Fedora live image to USB and enabling the encrypted persistent home option, the plymouth password entry screen is only shortly visible and then disappears. As a result, it is not possible to insert the LUKS passphrase and the boot hangs because it is waiting to decrypt the home partition.
Version-Release number of selected component (if applicable):
livecd-tools.x86_64 1:22.2-1.fc22 @updates
plymouth.x86_64 0.8.9-9.2013.08.14.fc22 @System
spin-kickstarts.noarch 0.22.5-1.fc22 @fedora
systemd.x86_64 219-25.fc22 @updates
Steps to Reproduce:
1. Download the Fedora live XFCE spin.
2. Copy the live image to USB with livecd-iso-to-disk, setting an encrypted home partition: livecd-iso-to-disk --extra-kernel-args "persistenthome=UUID=X-X-X-X" /path/to/iso/file.iso /dev/sdbX
3. Reboot from USB and wait for passphrase dialog to appear.
The plymouth password entry screen briefly appears, but then disappears as other systemd services are started. As a result, boot hangs because it is waiting for passphrase, which cannot be inserted.
The pymouth password dialog shows up, the user inserts the password, and boot continues.
This happens also in basic graphics mode. I expect systemd to be responsible for this, because it continues loading other services that mask the boot prompt.
The script from which plymouth ask-for-password is called is in the file fedora-live-base.ks from the spin-kickstarts package.
Same on Fedora 23
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.