Red Hat Bugzilla – Bug 441009
First boot ignores the keyboard layout selected in the installer, used by the system in the console and used the English one in Fedora Core 9 Beta 1
Last modified: 2008-04-07 11:01:05 EDT
Description of problem:
When 'firstboot' is executed after a reboot following the installation of Fedora
Core 9 Beta 1, using the french keyboard layout during the installation process,
it's using the English keyboard layout and not the French one.
This is weird because, when I had to type the passphrase to decrypt my root
partition, I did it using the french keyboard layout.
The problem is present in X11 too, after configuring the system with firstboot
so the problem could be hidden to the user until it loads its session.
Version-Release number of selected component (if applicable):
Fedora Core 9 Beta 1, Installation DVD, X86_64, networkless installation.
Actually, tried it only once.
Steps to Reproduce:
1. Install Fedora Core 9 Beta 1 with the installation DVD designed for X86_64
2. During the installation, choose the French latin9 keyboard layout and type
your password using the French layout.
3. After the installation, reboot, wait for Firstboot to come and try to input
'qsdf' in text-areas where the text isn't masked (IE : not password textareas !)
If you got a French keyboard, you'll see 'asdf' printed in the text-area
selected, indicating that the keyboard layout currently used is the English one,
not the French one.
The characters input in the text-area MUST be 'qsdf'. It's important, at this
point of the installation to have a correct keyboard layout since you'll input
the password used by the principal user account !
If the layout is wrong, you'll input a different password that you think you've
same issue here....made installations of fedora 9 beta 1 on i386 arch and also
on x64_86 architecutre...both version do have this problem.
when you select a keyboard-layout while installing, this is not configured after
the reboot to your system. you have to setup manually again your keyboard layout...
I think this was due to using evdev as opposed to the older keyboard driver.
Can you test either the weekly snapshot releases or rawhide and let me know if
this is still broken? Thanks.
Looks like this one is still around.
*** This bug has been marked as a duplicate of 438246 ***