Bug 720178 - LUKS passphrase required twice
Summary: LUKS passphrase required twice
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 15
Hardware: i686
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 745970 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-10 16:11 UTC by David A. De Graaf
Modified: 2012-08-07 18:28 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-07 18:28:06 UTC
Type: ---
Embargoed:
bill-bugzilla.redhat.com: fedora_requires_release_note+


Attachments (Terms of Use)
First prompt (1.65 MB, image/jpeg)
2011-07-10 16:11 UTC, David A. De Graaf
no flags Details
Second prompt (2.10 MB, image/jpeg)
2011-07-10 16:13 UTC, David A. De Graaf
no flags Details
Second prompt reappears after typing commences (2.18 MB, image/jpeg)
2011-07-10 16:15 UTC, David A. De Graaf
no flags Details

Description David A. De Graaf 2011-07-10 16:11:59 UTC
Created attachment 512096 [details]
First prompt

Description of problem:
Prompt for passphrase is repeated after several screenfuls

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


How reproducible:
Always occurs on one machine; never on another

Steps to Reproduce:
1.  Boot an encrypted laptop, using multi-user.target, and no rhgb
2.  Supply passphrase, when prompted
3.  Express surprise and dismay when prompted a second time
  
Actual results:
Two prompts

Expected results:
One prompt

Additional info:
I am asked for the LUKS passphrase twice, despite having specified a 
"global passphrase" for four ext4 partitions - /, /f14, /home and swap - 
during a fresh installation of F15.  The /boot partition is not encrypted.
This is on an IBM T30 laptop, on which F14 works perfectly, eg, the 
passphrase is required only once.

I attach photographs of the screen; I know of no other way to capture
this data.

The first prompt for the passphrase is crystal clear (#1).  The second 
prompt is buried in a morass of systemd drivel (#2), but is revealed
when typing commences (#3).

I use the multi-user.target mode, and remove rhgb from the kernel line,
so I can actually see what happens during boot.  It's not pretty.
After logging in in text mode, I use startxfce4 and am spared the 
horror of gnome 3.

On another ASUS N10 netbook, configured identically, no second prompt
for the passphrase occurs.  Go figure.

Please fix this bug in systemd to remove the unnecessary and redundant
second passphrase prompt.

Comment 1 David A. De Graaf 2011-07-10 16:13:45 UTC
Created attachment 512097 [details]
Second prompt

Comment 2 David A. De Graaf 2011-07-10 16:15:46 UTC
Created attachment 512098 [details]
Second prompt reappears after typing commences

Comment 3 Bill McGonigle 2011-09-29 19:23:29 UTC
dup of bug 716291 ?

Comment 4 Fedora Admin XMLRPC Client 2011-10-20 16:28:33 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Jóhann B. Guðmundsson 2012-01-25 13:54:20 UTC
Is this still an issue or can this bug be closed?

Comment 6 Bill McGonigle 2012-01-25 17:59:12 UTC
still an issue (Status: NEW)

Comment 7 David A. De Graaf 2012-01-25 20:29:05 UTC
Yes, the bug is still with us.  Today I yum updated and got a new kernel.
I hoped this bug would be gone, but it's still there.

kernel-3.2.1-3.fc16.i686.PAE
IBM T30 laptop

Of two laptops, only this one asks a second time for LUKS passphrase.
My other one, an ASUS N10 netbook, asks only once.

Comment 8 Jóhann B. Guðmundsson 2012-01-25 21:44:02 UTC
A reporter mentioned an reliable workaround in bug 749027 comment three add   "plymouth.debug=file:/run/plymouth/debug.log" to the kernel command line. 

Can you confirm/deny this workaround?

Comment 9 David A. De Graaf 2012-01-26 21:44:54 UTC
Yes, activating plymouth logging does result in only a single request for the LUKS passphrase.  But it also adds a gigantic stream of cruft to the screen - with rhgb absent, and booting to multi-user.target (init level 3).

I had expected this info to be put into /run/plymouth/debug.log, and it was, but it also streams onto the screen.  It would certainly better to *only* save it in a file.

Comment 10 Jóhann B. Guðmundsson 2012-01-26 22:36:16 UTC
Adding the plymouth maintainer who might shed some lights on what's happening here...

Comment 11 Jóhann B. Guðmundsson 2012-01-27 19:01:08 UTC
Reassigning against plymouth afters speaking with it's maintainer. 

This is a fall out from requests being asynchronous now. 

What happens is that system needs a password so it first asks plymouthd if there are any already known passwords then plymouth will either respond with the password or will instead say "i don't know any" then it will ask plymouth to ask for a password.

Now you can end up in a situation where you end up with two processes asking for any known passwords at the same time plymouthd telling both of them at the same time "i don't know any"then both processes at the same time saying  "okay ask the user"

At that point plymouthd will know about that password and the next request that comes by plymouthd won't say "i don't know any" instead it will reply with what it knows...

The fix should be pretty straightforward and will be dealt with as soon as he has the time to do it.

Thanks for your patience.

Comment 12 Jóhann B. Guðmundsson 2012-01-30 09:36:15 UTC
*** Bug 745970 has been marked as a duplicate of this bug. ***

Comment 13 Bill McGonigle 2012-02-27 19:16:29 UTC
Is the proposed fix the same as Lennart's proposal in bug 679907 comment #1?  If so, this bug might now be a duplicate.

Either way, with Fedora 17 past alpha now, perhaps we should flag this for release note if it's not going to be fixed in time.

Something like:

"Global passphrases used to decrypt multiple LUKS volumes may result in multiple password prompts due to a deficiency in systemd.  As a workaround, add "plymouth.debug=file:/run/plymouth/debug.log" to the kernel command line.  This will result in verbose debugging to the screen but the passphrase will only be required once."

Comment 14 David A. De Graaf 2012-03-22 16:28:50 UTC
I have just received via yum update a new kernel 3.3.0-4.fc16.i686.PAE and rebooted without the "plymouth.debug=file:/run/plymouth/debug.log" workaround.
I was NOT prompted twice for the LUKS passphrase and the non-rhgb progress screen was clear and readable.

Thanks to whomever fixed this annoying problem.

Bugzilla really does work.

Comment 15 Michal Schmidt 2012-03-22 16:34:37 UTC
Isn't this known to be a plymouth bug, and not a kernel one? If updating the kernel makes a difference, it may be just good luck with timing.

Comment 16 Fedora End Of Life 2012-08-07 18:28:09 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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


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