Hide Forgot
Description of problem: Most of the time on boot plymouth password input is not shown for my encrypted swap lvm. Later in the session, I will see in the logs where it attempts to swap that it can not because the password was not given. When I look in the boot log I'll see this: Oct 31 08:20:00 raykj systemd-cryptsetup[835]: Timed out Oct 31 08:20:00 raykj systemd-cryptsetup[835]: Failed to query password: Timer expired I believe that the password prompt is going to tty instead of plymouth. Important to note that when this happens, I do not see the plymouth boot theme -- it starts and then disappears for two lines of text. Boot works, but this obviously adversely impacts the performance of the system. I don't believe this is caching as this morning I booted for the first time in 24 hours and it still didn't ask me. Version-Release number of selected component (if applicable): F16 RC1 How reproducible: Very -- although not every time Steps to Reproduce: 1. Boot -- look for plymouth boot theme and password prompt. 2. 3. Actual results: Two lines of text shown on black screen and no plymouth theme Expected results: Plymouth theme and a password prompt on every boot. Additional info:
Created attachment 530993 [details] Photo of what i see during boot Adding photo of what I see during boot.
Hi, on my Fedora 16 system I have the same problems with systemd and an encrypted partition. Here systemd.x86_64 37-25.fc16 is running.
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.