Bug 707316

Summary: Unable to type passphrase for swap with spinner theme
Product: [Fedora] Fedora Reporter: Michael Monreal <michael.monreal+bugs>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: agk, dwysocha, fedora, lvm-team, mbroz, opensource, pjones, prockai, rstrode, whulbert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 18:23:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Monreal 2011-05-24 16:50:35 UTC
After preupgrading to F15, I am not able to boot into my system normally: the first I see is a text console with the following text:

---
/dev/sda3 (luks-.......) is password protected
Enter passphrase for /dev/sda3:
---

The partition in question is my swap. If I start typing my password, it tells me no such key even before I finish typing. All I can do is ctrl-alt-del to reboot. On the second boot, it displays other stuff, finally shows the splash and asks me for a password there and it works.

Before upgrading to F15, this used to work fine.

Comment 1 Michael Monreal 2011-05-24 18:57:52 UTC
I have to correct myself: the reboot does not work around the problem, but pressing ESC a few times just after GRUB does...

Comment 2 Milan Broz 2011-05-24 19:14:53 UTC
I do not think this is cryptsetup problem, it seems like some script or so run it with wrong paramaters ot there is some race.
(Actually cryptsetup itself never asks for passphrase directly, it is plymouth dialog probably.)

/dev/sda3 is LUKS device, correct? What's in /etc/crypttab?

Comment 3 Michael Monreal 2011-05-24 19:39:31 UTC
Yes you are most likely right, but I am not sure how the new boot process in Fedora works, so it's hard for me to find the correct component :/

cat /etc/crypttab
luks-a471458d-d688-4eea-8546-2362a896515f UUID=a471458d-d688-4eea-8546-2362a896515f none 
luks-a2a51e12-0b8d-48f4-b39b-cce24d4fde5a UUID=a2a51e12-0b8d-48f4-b39b-cce24d4fde5a none

Comment 4 Michael Monreal 2011-05-25 15:37:49 UTC
Looks like this is a bug in plymouth, specifically the new "spinner" theme. Can you please re-assign?

Comment 5 Milan Broz 2011-05-25 20:17:15 UTC
ok, it seems like plymouth interfere here somehow, reassigning.

Comment 6 Fedora End Of Life 2012-08-07 18:23:42 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