Bug#801563: race condition in systemd boot with cryptsetup password prompt

[Aryeh Leib Taurog]

Dear maintainers,

I am experiencing exactly the behavior described here.  I have a LUKS 
encrypted /home partition on my system.  If I don't enter the 
passphrase quickly during the boot sequence, systemd first drops into 
emergency mode, then continues to targets "System Initialization" and 
"Basic System," but doesn't offer any possibility of interacting with 
the system.  Sometimes the window of opportunity seems quite short, 
less than 90s.

The last three messages on the console are:

[   OK   ]  Stopped Dispatch Password Requests to Console.
[   OK   ]  Stopped Forward Password Requests to Plymouth.
[   OK   ]  Stopped Forward Password Requests to Wall.


For me the preferred, backwards compatible, behavior would be to wait 
indefinitely for the passphrase without dropping to emergency mode.

Is this bug definitely superceded by bug #802897?  If so I would 
certainly like to see that patch included in stable.  Should I send a 
message to that bug as well?

Changes to stable aside, is there a configuration change I could make 
to get the desired behavior?


Much thanks,
Aryeh Leib Taurog