GNOME Bugzilla – Bug 675298
caps-lock doesn't work as super key
Last modified: 2021-07-05 14:38:24 UTC
When I select "caps-lock as additional super key" in g-c-c keyboard, it has no effect. Selecting another entry, for example "caps-lock as additional delete key" works as expected. Steps to Reproduce: 1. open g-c-c keyboard 2. select "caps-lock as additional super key" Actual results: nothing Expected results: caps-lock working as super-key bugzilla.redhat.org: #767518
I just tried to confirm this, and it seems to work for me. System setup: Gnome 3.4.2 on Fedora 17 One keyboard layout: US English I used the following steps to get it to work on my end: 1. Opened Gnome Control Center 2. Clicked "Keyboard" 3. in the "Typing" tab i chose the "Layout Settings" link at the bottom 4. in the "Layouts" tab, i clicked the "Options" button in the lower right hand corner. 5. I then expanded the "Caps Lock Key behaviour" tree item 6. Finally, i selected the "Make Caps Lock an additional Super" radio button. This series of steps successfully disabled the left Super key and remapped it to the caps lock key. is there any further information / differentiation between our setups that may be causing this on your end? --ryanlerch
Indeed, the Caps Lock button does seem to work as additional Super now. I'am on 3.4.2 with F17 also. But now the normal super-key (ie the windows button) doesn't work. Only Caps Lock. Can you confirm that? In my understanding "additional Super" means both should work. My only additional setting is that I have two keyboard layouts (german & english) and switch between the two via alt-capslock.
It looks like we are getting similar results. When i enable the ""Make Caps Lock an additional Super" option, it does disable the normal super key. I am pretty sure that this is normal behaviour, AFAICT, this feature is in place for users with older keyboards that do not have Super keys at all. That said, in the very least, the language of the option should be changed to prevent confusion. Maybe something like: "Make the Caps Lock key the Super key"
Checking the symbols on my F17 box here, this isn't xkeyboard-config's fault. Once assigned, both keys send the right keysym (Super_L) and set the Mod4 modifier. xev log below: KeyPress event, serial 29, synthetic NO, window 0x2600001, root 0x15b, subw 0x0, time 91398373, (197,158), root:(1880,281), state 0x0, keycode 133 (keysym 0xffeb, Super_L), same_screen YES, XKeysymToKeycode returns keycode: 66 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 32, synthetic NO, window 0x2600001, root 0x15b, subw 0x0, time 91398501, (197,158), root:(1880,281), state 0x40, keycode 133 (keysym 0xffeb, Super_L), same_screen YES, XKeysymToKeycode returns keycode: 66 XLookupString gives 0 bytes: XFilterEvent returns: False The CapsLock key sends the same events, but its events are grabbed by gnome shell and used to switch to the overlay. So the issue here appears to be that gnome shell only has one key to trigger the overlay.
Might be a dupe of bug 659899.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.