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 742470 - window menu: alt+space keyboard accelerators not available
window menu: alt+space keyboard accelerators not available
Status: RESOLVED DUPLICATE of bug 733297
Product: gnome-shell
Classification: Core
Component: window-management
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2015-01-06 17:21 UTC by Kartik Subbarao
Modified: 2016-10-14 14:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kartik Subbarao 2015-01-06 17:21:48 UTC 
In earlier versions of GNOME, it was possible to type (for example) alt+space, followed by 'a', to select "Always on visible workspace". Similarly, 'n' was an accelerator for minimize, and so on. These keyboard accelerators don't seem to be available on 3.14. I found the following explanation:

https://bbs.archlinux.org/viewtopic.php?id=189255

It states that the window menu was handled by gtk in previous releases, but is now being handled by gnome-shell, and that this functionality was probably missed during the transition.

Can this functionality be restored?
Comment 1 sandeep 2015-10-11 05:05:39 UTC 
is there an update on this ? how hard is this to implement.
Comment 2 pierotiste 2016-03-06 05:33:18 UTC 
Any news on this? These shortcuts are really convenient!!
Comment 3 Kristian Nygaard Jensen 2016-10-14 14:14:58 UTC 
I have the same issue even in gnome 3.20
Comment 4 Kristian Nygaard Jensen 2016-10-14 14:17:23 UTC 
Where would I start to look. If I wanted to implement a patch?
Comment 5 Florian Müllner 2016-10-14 14:21:38 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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