Bug 753647 - No password entry visible during boot with disk encryption
Summary: No password entry visible during boot with disk encryption
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 16
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-13 23:21 UTC by marco
Modified: 2013-02-13 21:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 21:50:32 UTC
Type: ---


Attachments (Terms of Use)

Description marco 2011-11-13 23:21:51 UTC
Description of problem:

When booting fedora 16 with disk encryption enabled during the DVD installer the password entry sometimes doesn't show up. In the normal case a graphical screen appears with the entry box just after switching from the text mode screen. The graphical screen only shows the password entry box, which is normal I think. In the wrong case though, the screen stays in text mode (seems to hang) but when I type the password blindly and wait some time, the rotating icon down-right of the screen appears and then the normal login screen.
It might be a problem with starting the graphical screen during boot, the fedora icon that fills up in normal cases doesn't show up at all in the wrong case. Might be a hardware thingy of the laptop I use: Acer aspire 5935 (It seems to have two video cards).
This is quite confusing at first. When playing with the keyboard it once showed the password entry in textmode. That gave me the hint that typing the password blindly would work as well. 

Version-Release number of selected component (if applicable):

fedora 16

How reproducible:

50%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Hardware: laptop Acer aspire 5935

Comment 1 marco 2012-03-23 00:55:07 UTC
The problem occurs almost every time when the system reboots. 
The system needs the password to read the encrypted disks in order to boot.
In most cases no password entry is shown.

If you need more info please contact me.

Comment 2 Fedora End Of Life 2013-01-16 17:18:35 UTC
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

Comment 3 Fedora End Of Life 2013-02-13 21:50:36 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.