GNOME Bugzilla – Bug 660566
Menu key cannot be assigned to a keyboard shortcut
Last modified: 2012-10-11 06:58:06 UTC
the report has been filed previously here: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/857623 "keyboard shortcuts that I assign to the Menu key are not obeyed. For example, I have set 'System Settings ▸ Keyboard ▸ Shortcuts ▸ Sound and Media ▸ Volume Mute' to 'Menu', but pressing the Menu key does not mute the volume; it opens a context menu."
The purpose of the shortcuts page is not to assign different meanings to keys that have well-established functions already.
If this behavior is by design, then the gnome-control-center GUI should: 1) not allow users to assign such keys, and 2) present an explanation of this limitation to users who try.
This bug affects me as well. When assigning the Menu key to any non-custom keyboard shortcut, it functions as expected. When assigning the Menu key to a custom keyboard shortcut, I am able to perform the assignment in the preferences menu, but it has no effect; the context menu still appears.
As per https://bugs.launchpad.net/gnome-control-center/+bug/932990 this also affects Print screen and Media play keys.
Also, as per https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/912933, does this also affects the Delete key?
In a way, this is a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=670579
Per https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/882180 it also affects Scroll lock. Also note that System Settings ▸ Keyboard ▸ Shortcuts ▸ Launchers ▸ Launch Terminal works with all these keys, so only some actions cannot be assigned to these keys. Also, it seems that key combinations such as Alt+Menu work for all actions.
ScreenLock is also affected. But why restrict and hardcode when we can make it customizable, can't we?
(In reply to comment #7) > Per https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/882180 > it also affects Scroll lock. > > Also note that System Settings ▸ Keyboard ▸ Shortcuts ▸ Launchers ▸ Launch > Terminal works with all these keys, so only some actions cannot be assigned to > these keys. Also, it seems that key combinations such as Alt+Menu work for all > actions. Keybindings handled inside the compositor (mutter) will work, but others instead handled by gnome-settings-daemon or a third-party program will not. We will be removing this distinction for 3.8.
The menu key works now. File separate bugs for the other keys. *** This bug has been marked as a duplicate of bug 685286 ***