After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 564687 - Keyboard settings do not apply when new keyboard is plugged in.
Keyboard settings do not apply when new keyboard is plugged in.
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Keyboard
2.24.x
Other All
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-12-15 23:59 UTC by Stephen Thorne
Modified: 2008-12-17 10:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Stephen Thorne 2008-12-15 23:59:31 UTC 
Please describe the problem:
I have changed a setting under "Hardware > Keyboard > Layouts > Layout Options... > CapsLock Key Behaviour".

I have selected "Swap ESC and CapsLock". This setting works on my primary keyboard (the built in keyboard on my laptop).

When I insert a new keyboard (ID 05ac:0220 Apple, Inc. Aluminum Keyboard) the capslock key does not behave as 'ESC', nor does the ESC behave as capslock, they both have their original functions.

Going to this dialog and selecting 'Default' then 'Swap ESC and CapsLock' makes the behaviour take effect as expected.

Steps to reproduce:
1. Change a setting under "Hardware > Keyboard > Layouts > Layout Options... > CapsLock Key Behaviour"
2. Plug in new usb keyboard



Actual results:
New keyboard does not behave as per the setting, instead the default behaviour is seen.

Expected results:
A new keyboard plugged in should follow the settings that are set for the keyboard, instead of the defaults.

Does this happen every time?
Yes.

Other information:
Comment 1 Sergey V. Udaltsov 2008-12-16 01:12:28 UTC 
Fixed in 2.25.x (with new libxklavier)
Comment 2 Stephen Thorne 2008-12-16 23:04:10 UTC 
Okay, but I'm running 2.24 - is there any way to fix this now? I'm having to do this twice a day. Even if it's possible to script it.
Comment 3 Sergey V. Udaltsov 2008-12-17 03:07:16 UTC 
Running setxkbmap (with necessary parameters) on plugging the kbd might help. How to setup the hook script? I do not know, actually (whether it is actually possible at all).
Comment 4 Stephen Thorne 2008-12-17 05:16:13 UTC 
I'm okay with having a script that I run in a shell or when I click on a launcher in the bar, it's just that at the moment I have to surf through dialogs to get to this part of the ui.

How do I figure out what gnome is doing in order to enact this setting so I can script it? Or is there a way I can send a signal to gnome to apply these settings.
Comment 5 Sergey V. Udaltsov 2008-12-17 10:33:16 UTC 
In that case, just look at the manual of setxkbmap, create one-liner script, put the launcher on the panel.

In order to find out your current xkb settings, do "xprop -root _XKB_RULES_NAMES" - you'll see them (ruleset, model, layouts, variants, options).

HTH