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 318704 - One can't use Super_L instead of Alt
One can't use Super_L instead of Alt
Status: RESOLVED DUPLICATE of bug 165343
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
2.12.x
Other All
: Normal minor
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-12 19:49 UTC by Łukasz Stelmach
Modified: 2006-07-22 12:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Łukasz Stelmach 2005-10-12 19:49:45 UTC
Super_L cannot be used as a modifier for shortcuts while using
gnome-keybinding-properties. When pressed it's accepted and bound to an action
as a single key. 

xmodamp says:
shift       Shift_L (0x32),  Shift_R (0x3e)
lock        Caps_Lock (0x25)
control     Control_L (0x42),  Control_R (0x6d)
mod1        Alt_L (0x40),  Alt_L (0x7d),  Meta_L (0x9c)
mod2        Num_Lock (0x4d)
mod3      
mod4        Super_L (0x7f),  Hyper_L (0x80)
mod5        Mode_switch (0x5d),  ISO_Level3_Shift (0x71),  ISO_Level3_Shift (0x7c)

Other information:
Comment 1 Sergey V. Udaltsov 2005-10-12 21:35:41 UTC
well, I am not really interested in xmodmap. Could you please show me "xprop -root | grep XKB"? Are you 
using standard gnome keyboard configuration tool from control center?
Comment 2 Łukasz Stelmach 2005-10-13 07:35:09 UTC
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "imac", "pl", "",
"lv3:rwin_switch,ctrl:swapcaps"
_XKB_RULES_NAMES(STRING) = "xorg", "imac", "pl", "", "lv3:rwin_switch,ctrl:swapcaps"

imac is my own hand-made model with pc105 symbols.

Yes I do.
Comment 3 Łukasz Stelmach 2005-12-21 00:36:51 UTC
I've managed this by putting <Mod4> everywhere I put <Super_L> before. I've tried to figure out why Super_L is treated as a normal key instead of a modifier but I still don't know. It looks like the KeyPress events generated by Super_?  are completly indistinguishable from key presses made with other "ordinary" keys (Alt, Shift and other modifier keys look the same). The only difference is that if a key has been defined as a modifier it doesn't gnerate subsequent KeyPress/KeyRelease repeated events and it has. Another difference can be found in KeyRelease events, it is non-zero /state/. Please compare these two pairs of events (Super_L is Mod4 as in my first note):

KeyPress event, serial 29, synthetic NO, window 0x3600001,
    root 0x7d, subw 0x0, time 13435045, (317,31), root:(329,131),
    state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (6c) "l"
    XmbLookupString gives 1 bytes: (6c) "l"
    XFilterEvent returns: False

KeyRelease event, serial 29, synthetic NO, window 0x3600001,
    root 0x7d, subw 0x0, time 13435124, (317,31), root:(329,131),
    state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (6c) "l"

KeyPress event, serial 29, synthetic NO, window 0x3600001,
    root 0x7d, subw 0x0, time 13436108, (317,31), root:(329,131),
    state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 29, synthetic NO, window 0x3600001,
    root 0x7d, subw 0x0, time 13436180, (317,31), root:(329,131),
    state 0x40, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes: 





Summing up, gnome-keybinding-properties does not know Super_L
Comment 4 André Klapper 2006-07-07 02:35:17 UTC
reopening as requested information has been provided.
Comment 5 Sergey V. Udaltsov 2006-07-07 22:19:45 UTC
OK that's right. It is not XKB configuration problem, it is g-kb-p does not have knowledge about Super_L. Sorry for confusion.
Comment 6 Olav Vitters 2006-07-22 12:20:29 UTC

*** This bug has been marked as a duplicate of 165343 ***