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 441061 - mod4 treated as a key not a modifier (graphical interface only)
mod4 treated as a key not a modifier (graphical interface only)
Status: RESOLVED DUPLICATE of bug 165343
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
2.16.x
Other All
: Normal minor
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-24 22:14 UTC by gottlieb
Modified: 2008-09-26 14:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description gottlieb 2007-05-24 22:14:44 UTC
Please describe the problem:
The gconf editor is working when invoked.  I am not sure what application handles
system>preferences>keyboard shortcuts.

When using system>preferences>keyboard shortcuts, mod4 is treated as a key (Super) rather than as a modifier.  This makes it impossible to specify a key
such as mod4-v

This is new behavior as I previously was able to specify mod4-v (and the action assigned then--expand vertically--still works)

I can go into system tools>configuration editor.  Then go to metacity and
can enter strings like <Shift><Mod4>F1 to specify keys.  That is the text interface works fine, the graphical interface has a comparatively new bug


Steps to reproduce:
1. system>preferences>keyboard shortcuts
2. choose any action
3. Hit the mod4 keysym


Actual results:
Super is entered as the shortcut

Expected results:
Nothing entered, but when another key (say v) is entered
<mod4>v is entered as the shortcut

Does this happen every time?
Yes

Other information:
Comment 1 Cosimo Cecchi 2008-09-25 17:20:20 UTC
-> gnome-control-center

but this might be fixed in newer versions.
Comment 2 Jens Granseuer 2008-09-26 14:37:49 UTC
Indeed.

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