Bug 1332296

Summary: Cannot decrypt disk after installation
Product: [Fedora] Fedora Reporter: Michael Catanzaro <mcatanzaro+wrong-account-do-not-cc>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 24CC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
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: 2016-05-02 19:42:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Catanzaro 2016-05-02 19:39:13 UTC 
Description of problem: Using the F24 Alpha Workstation install media, I selected the Dvorak keyboard layout and set a disk encryption password using that keyboard layout. When booting the computer for the first time after installation, my password was rejected each time I typed it, and I could not boot the computer.


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


How reproducible: I tested three installations, happens every time.


Steps to Reproduce:
1. Select keyboard layout first
2. Then visit the partitioning spoke, select disk encryption, enter password...
3. Finish install, reboot computer

Actual results: Password is repeatedly rejected


Expected results: Computer boots


Additional info: This is a regression from F23. I wound up installing F23 on this computer instead.

Note that I have not tested with Qwerty, so I'm not positive that keyboard layout is to blame for this. But in the past we had a similar bug where disk encryption required a Qwerty keyboard layout because keyboard layout wasn't being saved in the initramfs... so I'm inclined to suspect a similar issue.
Comment 1 David Shea 2016-05-02 19:42:48 UTC 

*** This bug has been marked as a duplicate of bug 1318045 ***