https://bugzilla.novell.com/show_bug.cgi?id=703947 https://bugzilla.novell.com/show_bug.cgi?id=703947#c5 Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|systemd: boot.crypto no |systemd: cryptsetup |longer called / cryptohome |passphrase prompt times out |not mounted |too quickly Severity|Critical |Normal --- Comment #5 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-07-05 21:03:00 CEST --- Ok, rebooted to test. crypto.service runs, but the passphrase input times out very fast (~5 seconds?), then the X server starts, the boot console gets cleared and you never see that passphrase prompt again. Starting it afterwards is not easy: susi:~ # systemctl status crypto.service crypto.service Loaded: masked (/dev/null) Active: inactive (dead) Warning: Unit file changed on disk, 'systemctl --system daemon-reload' recommended. susi:~ # systemctl start crypto.service Failed to issue method call: Unit crypto.service is masked. susi:~ # systemctl start crypto.service Failed to issue method call: Unit crypto.service is masked. So I finally did systemctl restart cryptsetup.target # not sure if that was necessary systemctl --system daemon-reload systemctl restart crypto.service And finally got my passphrase prompt. Maybe a allowing "/etc/init.d/boot.crypto start" to also work would be helpful for users in panic mode (as I was ;-) And the timeout is too short. I mean - continuing to boot makes absolutely no sense without $HOME mounted, so the "speed" argument is not valid ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.