Description of problem:
GDM defaults to US keyboard layout on login, even though Norwegian keyboard was selected in the installer. The console also has US keyboard layout.
Version-Release number of selected component (if applicable):
Fedora 12 Alpha
How reproducible: Always
Steps to Reproduce:
1. Install Fedora, select Norwegian keyboard layout in installer
US keyboard layout as default on login, even for a newly credted account
Norwegian keyboard as default
/etc/grub.conf has "KEYBOARDTYPE=pc KEYTABLE=no" for the newly installed kernel, so it seems that the settings are passed on but not used in all places.
What does /etc/sysconfig/keyboard look like?
There is no /etc/sysconfig/keyboard, so I suppose that might be the problem.
The installation was done from the i686 Live image.
The same is happening with Brazilian keyboard layout. This might be a high severity bug, since it could affect every localized installation of Fedora.
I guess this not a system-config-keyboard bug. GDM defaults to US keyboard layout even on live images created with custom kickstart files. It also defaults to US keyboard every time I try log in.
I have the same issue here, with Hungarian layout in 12 beta (x86_64 DVD install).
GDM "forgets" my keyboard layout between logins too. I'm using Norwegian and chose that during install.
(In reply to comment #5)
> GDM "forgets" my keyboard layout between logins too. I'm using Norwegian and
> chose that during install.
Kjartan, this issue was fixed on bug #530452.
Anyway, the behavior is still broken when using kickstart files.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
I am having the same problem in Fedora 13. Is this the place to mention this?
Confirm that I have had the same issue in f13 for a UK keyboard setting.... reverts to US on login through gdm.... using gnome.
One additional strange behaviour - in GDM if I switch to the USA selection
before logging in then it uses the UK keyboard mapping! This implies that
there may be a pair of lines or filenames swapped to the opposite of what is
I think I have figured out what is going on - and that the bug is not in dgm or gnome but in the installer.
What appears to have happened is that during the install anaconda decided that the keyboard was US. This makes no difference until a password containing non alphameric characters is entered such as the normal user password at firstboot.
Then when the user selects the UK keyboard the password has characters that did not match for any of the non alphameric characters with the UK selected keyboard.
This also explains why the screensaver requires the same characters taken from keys for the US key positions to unlock the screensaver.
To test this I switched to the UK keyboard in gnome and then reset the password using the UK normal keyboard keys. Then after logging out and selecting the UK keyboard in gdm, login works correctly for the password. Within gnome the UK keyboard is now retained, and the screensaver password works with the UK keys.
Hence this is definitely a bug in anaconda and not in gdm or gnome, nor in control-center I believe.
I also checked the anaconda-ks.cfg file in root and it shows that the install
keyboard was selected as "keyboard us". This is definitely an anaconda bug and
the component should be reassigned to anaconda.
I just did another install on a different machine and I had no keyboard
problems - so I am now not sure if I perhaps did not select the UK keyboard on
the initial install - unless I reinstalled on the machine where I had the
problem I now can't reproduce the problem I had! However the system I had uses
a usb keyboard and the others were laptops where there was no problem. If it is
my clumsiness then apologies for the noise!
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.