Bug 717208

Summary: luks / systemd timeout in default rhgb boot provides no user interaction
Product: [Fedora] Fedora Reporter: Jimmy Dorff <jdorff>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: bill-bugzilla.redhat.com, contact, fedora, pentarh, rstrode, stephane.raimbault
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-17 13:42:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
/etc/crypttab - nothing interesting but including for completeness none

Description Jimmy Dorff 2011-06-28 11:29:54 UTC
Created attachment 510257 [details]
/etc/crypttab - nothing interesting but including for completeness

Description of problem:
When booting a f15 install with luks encrypted /home, plymouth gives a GUI password problem. I the human fails to enter the password quickly, the screen goes blank and remains blank with no user interaction possible. 

If I remove rhgb from the kernel args and just wait for a timeout I see:
Starting /home aborted because a dependency failed.
Starting Relabel all filesystem, if necessary aborted because a dependency failed.
Starting Mark the need to relabel after reboot aborted because a dependency failed.
error: unexpectedly disconnected from boot status daemon
Welcome to emergency mode. "Use systemctl default" or ^D to activate default mode.

Version-Release number of selected component (if applicable):
plymouth-0.8.4-0.20110510.2.fc15.x86_64
systemd-26-4.fc15.x86_64
initscripts-9.30-2.fc15.x86_64
kernel-2.6.38.8-32.fc15.x86_64

How reproducible:
Happens every time

Steps to Reproduce:
1. Install a system with an encrypted "/home" partition
2. Boot the system, when the luks passphrase is prompted ignore it for a few minutes

  
Actual results:
Blank screen with no errors and no ability for the user to do anything other than power cycle or ctl-atl-delete. For a novice user this is total fail.

Expected results:
Some sort of text on the screen indicating there was a problem.

Additional info:

Comment 1 Bill McGonigle 2011-08-03 21:54:05 UTC
Confirming this here.  It gets compounded by the other bug where systemd sometimes somehow forgets that it got a global passphrase for / .

Pressing 'del' to get to the text screen is a workaround.  Delete the 3 garbage characters that get entered into the text password prompt first, though.

I've seen this on all of my f15 machines with encrypted filesystems (simple primary partitions for /boot, swap, /, and /home, all encrypted except for boot) so it's probably not hard to reproduce (else I just got extra 'lucky').

Comment 2 Pentarh Udi 2011-08-27 09:04:44 UTC
+1 to this bug. Annoying thing

Comment 3 Stéphane Raimbault 2011-12-17 22:25:50 UTC
Yes very annoying and the bug still present in Fedora 16.

Comment 4 Stéphane Raimbault 2012-06-02 20:41:24 UTC
The bug is fixed in Fedora 17.

The prompt doesn't quit anymore after few minutes.

Comment 5 Stéphane Raimbault 2012-06-17 13:42:35 UTC
This bug can be closed...