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 677911 - overlay-key only partly respected
overlay-key only partly respected
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: general
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2012-06-12 02:47 UTC by Daniel Wagner
Modified: 2021-07-05 13:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Wagner 2012-06-12 02:47:55 UTC
I have org.gnome.mutter.overlay-key set to "Super_L" (the default), and have mapped two physical keys (my laptop keyboard's windows key and my external keyboard's windows key) to Super_L:

~% xmodmap -pke | grep Super
keycode 133 = Super_L NoSymbol Super_L NoSymbol Super_L
keycode 134 = Super_L NoSymbol Super_L NoSymbol Super_L
keycode 206 = NoSymbol Super_L NoSymbol Super_L NoSymbol Super_L

Pressing the laptop keyboard's Windows key (keycode 133) correctly starts the overlay. I have confirmed that my external keyboard's Windows key (keycode 134) correctly sends Super_L with xev; however, the overlay does not start when I press this key.

This is similar but distinct from bug 665547, which discusses the gnome-shell overlay's incorrect handling of overlay-key, rather than mutter's incorrect handling of overlay-key.
Comment 1 Jonas Ådahl 2018-02-01 08:44:39 UTC
Does this still reproduce? Lots of changes has gone into the keybindings code in recent years, including things related to keycode resolving.
Comment 2 GNOME Infrastructure Team 2021-07-05 13:46:04 UTC
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/mutter/-/issues/

Thank you for your understanding and your help.