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 692437 - <Alt>Above_Tab does not cycle windows
<Alt>Above_Tab does not cycle windows
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
2.34.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2013-01-24 10:01 UTC by Jeffrey Knockel
Modified: 2015-01-07 21:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proposed patch to fix <Alt>Above_Tab not cycling through windows (586 bytes, patch)
2013-01-24 10:01 UTC, Jeffrey Knockel
none Details | Review

Description Jeffrey Knockel 2013-01-24 10:01:56 UTC
Created attachment 234289 [details] [review]
Proposed patch to fix <Alt>Above_Tab not cycling through windows

When the "switch_group" keyboard binding is set to <Alt>Above_Tab (the default), you cannot cycle through any of the application's windows.  Namely, when you

Press <Alt>
Press, release Backtick
Press, release Backtick
. . .
Release <Alt>

The first press/release of Backtick will bring up the group cycle dialog as expected, but the second press/release of Backtick does not cycle to the next window.  Rather, it dismisses the dialog.

Setting the "switch_group" keyboard binding to <Alt>Backtick works around this issue.

The problem appears to be in display_get_keybinding_action(), where the pressed keysym is compared to all of the registered keybindings.  However, the stored keysym for the "switch_group" keybinding is the special keysym META_KEY_ABOVE_TAB, and so the pressed keysym never matches it.

The proposed patch I've attached fixes the issue by ignoring the pressed keysym when a registered keybinding's keysym is META_KEY_ABOVE_TAB, in which case only compare the pressed keycode and mask to that of that keybinding.
Comment 1 Jeffrey Knockel 2013-01-24 10:17:06 UTC
Correction: Setting the "switch_group" keybinding to <Alt>grave (ensure the 'g' is lowercase) works around this issue, not <Alt>Backtick as originally reported.  Then 'metacity --replace' for the new setting to be picked up.
Comment 2 Timo Jyrinki 2014-02-13 09:15:36 UTC
This seems to fix alt+grave behavior in gnome fallback session for me. Switching between multiple windows now works, and I can't spot any regressions.
Comment 3 Alberts Muktupāvels 2015-01-07 21:24:09 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.