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 662772 - Cannot use Mod4 as part of a keyboard shortcut
Cannot use Mod4 as part of a keyboard shortcut
Status: RESOLVED DUPLICATE of bug 662580
Product: gnome-shell
Classification: Core
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-26 14:52 UTC by Xabier Rodríguez Calvar
Modified: 2012-05-05 18:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Xabier Rodríguez Calvar 2011-10-26 14:52:37 UTC 
I used normally Mod4+Right and Mod4+Down (being Mod4 the windows key) to next and play/pause, but it is not working anymore since I switched to Gnome 3. If I just bind the usual multimedia key or something like Alt+Down, it just works, so I assume the Mod4 is not being handled correctly by the shell because of the "exposé" effect.
Comment 1 qmax 2012-01-07 08:03:54 UTC 
This relates not to Mod4, but to any modifier assigned for "expose".
It's by default LeftWin = Super_L = mod4.

As for version 3.2.1-0ubuntu1.1 shortcuts with "ExposeKey"+AlphanumKey
work, but weirdo:
- hold down "Expose"
- first press of "Alphanum" yields unmodified Alphanum
- second press of "Alphanum" yields desired shortcut
Comment 2 Alex Hofbauer 2012-05-05 18:44:18 UTC 
This bug has gotten worse with the release of Gnome 3.4 completely breaking my workflow.

Before I was able to remove the binding of Super_L in gconf and bind Super_L to shortcuts. Now this is not possible any more. Even if I remove it in dconf, it will grab Super_L.


Please, make the overlay key configurable and stop it from grabbing all keybindings.
Comment 3 Jasper St. Pierre (not reading bugmail) 2012-05-05 18:56:23 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

It's a complicated bug.

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