Bug 1005493

Description of problem:

I decided to to a fresh install of Fedora 19 to a new hard drive.  So I booted up the live CD.  My keyboard is DVORAK.  In my first install attempt, I simply clicked on the install fedora button that appears when first starting up.  I selected my language as English, and my keyboard as US dvorak.  I got all the way to the disk configuration before I realized it was taking my input as querty.  So I had no idea what it would be using as my luks full disk password...   At that point there is no BACK button, no exit button, or no minimize button.  It took several minutes of struggling to find a way to kill the window so I could start over again.

Before starting my second attempt I set my keyboard and language settings directly in gnome.   This time everything in the install process works.   That is until the machine rebooted.  At that point it would not accept my luks password.   Now, I am fortunate enough to have a switchable keyboard.   So I toggled the settings and I was able to enter the luks password.

The third problem is the console was also not mapped to dvorak...

The forth problem is grub was not mapped to dvorak, for live edits to the configuration.

I found the solution for grub rather quickly in google.  It is an issue of building a keyboard mapping, adding to the /boot directory, and modifying the configuration to load the keyboard mapping.

The problem with the virtual console stumped me for about an hour.  I finally found the kernel parameter set in a bug update for F18 is ignored.  Instead what is use is the contents of /etc/vconsole.conf.

So I updated /etc/vconsole.conf, ran dracut.  Now everything is mapped to dvorak.



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

anaconda

How reproducible:

100%

Steps to Reproduce:
1. Attempt to use a non-US keyboard during install.
2.
3.

Actual results:
1. Passwords and other text are entered wrong.
2. Grub uses the wrong keyboard mapping.
3. The initramfs uses the wrong keyboard mapping for luks.
4. The wrong mapping is used for vconsoles.

Expected results:
It should just work.

Additional info:
There are several similar bugs I saw listed.  But none included a full description and all the related problems.