GNOME Bugzilla – Bug 747179
App menu accelerators not working when using gear menu
Last modified: 2016-05-21 03:05:37 UTC
Distro: Arch DE/WM: Awesome 3.5.6 Since upgrading to Geary 0.10, CTRL+Q no longer quits Geary under AwesomeWM. Prior to the 0.10 release, CTRL+Q functioned properly under AwesomeWM. It is worth noting that CTRL+Q functions properly on Gnome 3.14.3.
Does AwesomeWM provide an application menu, or does Geary provide it itself through the "gear" icon? Do the F1 or Ctrl+M shortcuts work on AwesomeWM?
Geary falls back onto providing a "gear" icon with the menu option. None of the shortcuts defined in the menu work [CTRL+M, CTRL+Q, CTRL_E]
The problem is likely 98be06db, where we changed how that menu was created. That fixed another bug, so we can't just revert it. The fix may be easy though. Let me see what I can find.
I can trigger this by inverting the sense of the gtk_shell_shows_app_menu tests. It's not a window manager thing; it's triggered by the app menu not being an app menu, but being used in the gear menu instead. Don't know why though. GTK accelerators have always struck me as a bit magic, and that seems to be the case again here.
This was also fixed by the fix for Bug 759980, i.e. by removing the gear menu and allowing GTK to manage when the shell isn't displaying the app menu.