Description of problem: My problem is similar to #579158: plymouth doesn't prompt for LUKS passphrase on boot if I don't touch the keyboard. But if I will hit escape afer it shows up for the first time, it will show up again after some boot proccess debug information with the password dialog. If I won't touch anything -- it will be just a black screen. If I will press escape after that (but if a minute will pass -- it won't work) I will see a text (not plymouth) password dialog. Everything works great without 'rhgb' kernel argument: no delays, straight text password dialog. Version-Release number of selected component (if applicable): plymouth-0.8.4-0.20110510.2.fc15.x86_64 How reproducible: Every boot. Steps to Reproduce: 1. Have a LUKS-encrypted LVM partition. 2. Boot. Actual results: System hangs. Expected results: Password dialog appearance. Additional info: /etc/crypttab: home /dev/mapper/vg00-crypted_home none luks /etc/fstab | grep home: /dev/mapper/home /home ext4 defaults 0 2
The problem is still there on recent up-to-dated Fedora 16 with these packages: plymouth-0.8.4-0.20110822.2.fc16.x86_64 kernel-3.1.1-2.fc16.x86_64
This bug is still active. My hw consists of Acer Aspire 3102 WLMi laptop with Mobile AMD Sempron 3200+ and ATi Radeon Xpress 1100. F16 is installed with encrypted root, swap and home partitions. This is reproducable almost in every boot.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.