Red Hat Bugzilla – Bug 836649
coming from emergency mode (Control-D) plymouth hangs after encrypted FS unlocked
Last modified: 2013-08-14 19:10:44 EDT
Description of problem:
Since Fedora 16 at least I have noticed a problem where if I do not unlock my encrypted home directory before the timeout which drops me to emergency mode it will hang on second go around.. If I do Control-D from emergency mode to continue plymouth asks for my passphrase, I give it, then plymouth hangs and never shows Fedora logo or GDM
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Fedora with an encrypted home directory
2. boot system
3. when prompted to enter passphrase do not enter passphrase (say you got up during boot to do something)
4. plymouth will drop to emergency mode, do Control-D to continue
5. plymouth will prompt for passphrase again, this time enter it
6 plymouth progress bar will go almost all the way, but not complete
fedora logo never shows, GDM never loads
it just sits there. I have waited 7 minutes in reproducing for this bug, but I have waited longer in the past with same results.
plymouth completes and GDM starts
Switching to virtual desktops gets no console to debug further.. the second virtual desktop does seem to show a login prompt for a split second and then it is blanked.
Created attachment 595352 [details]
Created attachment 595353 [details]
Created attachment 595354 [details]
Created attachment 595355 [details]
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17'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 17 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 change the
'version' to a later Fedora version prior to Fedora 17's end of life.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.