Hide Forgot
+++ This bug was initially created as a clone of Bug #552397 +++ Description of problem: I find the keyboard layout is incorrect so open System->Preferences->Keyboard and remove the USA mapping and select the United Kingdom one. I close gnome-keyboard-properties and use the keyboard mapping successfully. But when I log out, and log in again, the layout is incorrect once more, it is reverted to the USA setting. I have to repeat this every time I log in. Version-Release number of selected component (if applicable): control-center-2.28.1-8.fc12.i686 How reproducible: 100% on my system Steps to Reproduce: 1.log in and change keyboard layout from USA to UK 2.remove USA layout, select United Kingdom layout 3.log out and log in again Actual results: USA layout is in effect again Expected results: USA layout nowhere to be seen, UK layout remains selected. Additional info: I tried gnome-session-save after changing the setting and it didn't make any difference. --- Additional comment from dirk.goetz on 2010-06-02 13:36:05 EDT --- Description of problem: Running in the same bug after upgrading from F12 to F13 using the install DVD. My setup is nearly the same, I want to use "German eliminate dead keys" and always get "USA". I can easily switch to my wanted layout by using the switch utility in the panel. But after the next login it is switched back to "USA". Version-Release number of selected component (if applicable): control-center-2.30.1-2.fc13.x86_64 Additional info: I tried to get all information that can be helpful from files I know keyboard could be affected by. If someone has an idea what else I can provide please tell me. $ cat /etc/sysconfig/keyboard KEYBOARDTYPE="pc" KEYTABLE="de-latin1-nodeadkeys" MODEL="pc105" LAYOUT="de" VARIANT="nodeadkeys" $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [de nodeadkeys,us] options = [terminate terminate:ctrl_alt_bksp,caps caps:none,grp grp:shift_caps_toggle] model = $ cat /etc/X11/xorg.conf ... InputDevice "Keyboard0" "CoreKeyboard" ... Section "InputDevice" # generated from data in "/etc/sysconfig/keyboard" Identifier "Keyboard0" Driver "kbd" Option "XkbLayout" "de" Option "XkbModel" "pc105" Option "XkbVariant" "nodeadkeys" EndSection ... $ egrep "(keyboard|xkb)" /var/log/Xorg.0.log [ 1399.327] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 1399.327] (**) Power Button: Applying InputClass "system-setup-keyboard" [ 1399.331] (II) Power Button: Configuring as keyboard [ 1399.331] (**) Option "xkb_rules" "evdev" [ 1399.331] (**) Option "xkb_model" "pc105" [ 1399.331] (**) Option "xkb_layout" "de" [ 1399.331] (**) Option "xkb_variant" "nodeadkeys" [ 1399.331] (**) Option "xkb_options" "terminate:ctrl_alt_bksp," [ 1399.359] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 1399.359] (**) Power Button: Applying InputClass "system-setup-keyboard" [ 1399.362] (II) Power Button: Configuring as keyboard [ 1399.362] (**) Option "xkb_rules" "evdev" [ 1399.362] (**) Option "xkb_model" "pc105" [ 1399.362] (**) Option "xkb_layout" "de" [ 1399.362] (**) Option "xkb_variant" "nodeadkeys" [ 1399.362] (**) Option "xkb_options" "terminate:ctrl_alt_bksp," [ 1399.377] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3) [ 1399.377] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall" [ 1399.377] (**) AT Translated Set 2 keyboard: Applying InputClass "system-setup-keyboard" [ 1399.377] (**) AT Translated Set 2 keyboard: always reports core events [ 1399.377] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event3" [ 1399.381] (II) AT Translated Set 2 keyboard: Found keys [ 1399.381] (II) AT Translated Set 2 keyboard: Configuring as keyboard [ 1399.381] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD) [ 1399.381] (**) Option "xkb_rules" "evdev" [ 1399.381] (**) Option "xkb_model" "pc105" [ 1399.381] (**) Option "xkb_layout" "de" [ 1399.381] (**) Option "xkb_variant" "nodeadkeys" [ 1399.381] (**) Option "xkb_options" "terminate:ctrl_alt_bksp," --- Additional comment from dirk.goetz on 2010-06-10 09:56:16 EDT --- I found a solution for me. The gdm-greeter's default is USA-keyboard after update with anaconda, so if I don't change my keyboard settings also to German here it will switch it to USA. After I have done it one time the default after login is German. Problem is that you don't recognize that after choosing your user at the buttom an option menu appears where you have to choose. ;-) If this also works for F12 I think it can be closed! --- Additional comment from camilo.uk on 2010-06-11 17:04:47 EDT --- I think Dirk has shed some light on the mechanism of this problem, I just checked and what he says is true. However the behaviour has changed. Now looking at F13, I have: control-center-2.30.1-2.fc13.i686 I set the keyboard at login time to USA (once, the default) and logged in. Then although control center remembered I had the UK setting, it showed that as selected even though the USA layout was still in force. No matter what I did with the control center I could not change the keyboard layout to UK. This behaviour is much worse than the original problem! To fix the whole problem I suggest: 1. Anaconda should default to the previous keyboard setting when upgrading 2. Login window should not reveal settings at the last moment, or if it does it should make them more obvious 3. Control center should not be silently overridden by the system setting, it should allow you to change the system default or change it just for your user. *** Bug 667700 has been marked as a duplicate of this bug. *** IBM is also saying their reproducer is: 1) Set german Keyboard layout 2) remove US Keyboard layout 3) open Terminal - everything okay 4) reboot 5) open terminal -> Keyboard is US layout again :-( 6) open keyboard layout settings: Youll see US is back in the list although german layout is ticked and set as standard. 6) remove US Keyboard 7) everything works fine 8) reboot 9) open terminal -> US keyboard layout again
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
*** Bug 797213 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0949.html