Description of problem: Wrong keyboard layout when entering encryption passphrase during boot-up Version-Release number of selected component (if applicable): 024-15.git20121218.fc18 How reproducible: Always Steps to Reproduce: 1. Install Fedora 18 with a French keyboard layout and encrypted root partition using a passphrase containing at least the letter 'A' 2. Upon first boot of installed system, type the passphrase by pressing the same keyboard keys which were pressed while setting up the passphrase during installation Actual results: Passphrase is rejected Expected results: Passphrase is accepted Additional info: - Typing the passphrase by using the corresponding keys in the US QWERTY layout results in the passphrase being accepted. - Adding vconsole.keymap=fr to the linux command solves this issue.
"vconsole.keymap=fr" should have been added to the linux command line by anaconda at installation time.
Indeed. What F18 tree did you install with?
(In reply to comment #2) > Indeed. What F18 tree did you install with? I installed F18 using the latest nightly boot.iso available on Dec. 26th on one of the official Fedora mirrors. Under the package selection, I selected "Minimal installation" instead of "GNOME Desktop". I'm not sure if that answers your question as I don't know what you mean by "tree".
Basically, I need to know which version of anaconda is present on your installation media. This gets printed during boot up of the installer and should also be one of the first lines in /tmp/anaconda.log.
(In reply to comment #4) > Basically, I need to know which version of anaconda is present on your > installation media. This gets printed during boot up of the installer and > should also be one of the first lines in /tmp/anaconda.log. Right now, I only have access to the installed system, which I installed using the affected version of anaconda. If /var/log/anaconda/anaconda.log is a copy of /tmp/anaconda.log, then here's its first line: /sbin/anaconda 18.37.4
Ah, this was fixed in 18.37.7. I'll dup to the bug that was attached to the commit. Thanks for looking it up. *** This bug has been marked as a duplicate of bug 875567 ***
Ok, thanks for your help, and sorry for not having found the earlier report.