Bugzilla – Bug 116451
when booting suse expects f2 pressed to continue when encrypted partition is expected
Last modified: 2005-09-12 13:09:59 UTC
I have encrypted partition /koti When booting suse it comes to "view more information" state when askin for the crypto password (if I havent pressed f2 earlier). The boot process stops here (whether I give the password+enter or not) - if I havent pressed the f2 earlier. To continue I have to press once f2 button to continue the boot process. - This is annoying for remote booting and actually makes it impossible.
which version are you really seeing this in? Its not RC2 because that does not exist. Please use the right version!
There is a timeout for the passphrase. And if you're are using a encrypted partition you have to sit in front of the system for your passphrase and this can not be done remote. Btw: Does your system continue to boot after you have typed in your passphrase or do you have press F2 aftrewards?
(In reply to comment #2) > There is a timeout for the passphrase. And if you're are using > a encrypted partition you have to sit in front of the system for > your passphrase and this can not be done remote. This occurs in my laptop as well in homeserver computer. I have several users for the computer. My user data is in encrypted partition (auto-login). When others are using the computer they are told to press enter or just to wait - and login in the normal way. - Possibly I make encrypted partitions for each (with auto-login for each?) so the actual login would be made through the passphrase entering. Would be nice if the passphrase prompt would ask "passphrase for Bill:" - a virtual name for the encrypted partition. > Btw: Does your system continue to boot after you have typed in your > passphrase or do you have press F2 aftrewards? YES ------------------------ The release of SUSE is 10rc3 / beta3 (the newest one). - was not in the list when submitting this bug
The information of which user uses what encrypted partition is not given without the mounted partition. Now: For which SUSE 10 you have to press F2 after typing the passphrase? Is it Beta3 or RC3 ... for RC3 this should be fixed. Please provide the output of rpm -q --changelog sysvinit | head -n 4 to see which version we're talking about.
(In reply to comment #3) > > Btw: Does your system continue to boot after you have typed in your > > passphrase or do you have press F2 aftrewards? > > YES This answer does not make sense to a choice question. > The release of SUSE is 10rc3 / beta3 (the newest one). > - was not in the list when submitting this bug What should 10rc3 be? 10 is no correct version number for SUSE Linux, and since there is no RC2, how should there be a RC3 already? And you can enter Beta3.
(In reply to comment #5) > (In reply to comment #3) > > > Btw: Does your system continue to boot after you have typed in your > > > passphrase or do you have press F2 aftrewards? > > > > YES > > This answer does not make sense to a choice question. - Either I have to press f2 (manually) before OR after submitting the passphrase. - - Either I have to press f2 (manually) before OR after NOT submitting the passphrase - waiting for timeout or pressing enter. > > The release of SUSE is 10rc3 / beta3 (the newest one). > > - was not in the list when submitting this bug > > What should 10rc3 be? 10 is no correct version number for SUSE Linux, > and since there is no RC2, how should there be a RC3 already? > And you can enter Beta3. --------------- kukkove@varis:~> rpm -q --changelog sysvinit | head -n 4 * Thu Aug 25 2005 - werner@suse.de - Apply the new LSB rule for optional pid files only (bug #105845) ------------
And this is bug #105999. There was a file descriptor leaks which stops the splash process on waiting on stdout. After pressing F2 the splash was stopped and the boot process was continued. /suse/werner> rpm -q --changelog sysvinit | head -n 4 * Thu Sep 01 2005 - mls@suse.de - do not leak stdout fd to splash process (bug #105999) *** This bug has been marked as a duplicate of 105999 ***