Unity Compiz plugin captures F10 for menu even when explicitly disabled in gnome-terminal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ayatana Design |
New
|
Undecided
|
Unassigned | ||
Unity |
Incomplete
|
Wishlist
|
Unassigned | ||
gnome-terminal (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Incomplete
|
Wishlist
|
Unassigned |
Bug Description
There is menu item in Edit / "Keyboard Shortcuts" which says "Enable the menu shortcut key (F10 by default)". The F10 key is captured by gnome-terminal regardless of the checkbox described above.
In this case, F10 does not come through to gnome-terminal and is captured by the window manager which in turn shows the menu. The configuration option available via gnome-terminal menu DOES NOT WORK IN THE DEFAULT Ubuntu CONFIGURATION. It cannot be expected from the "average / target" user to hunt for the application capturing F10 and disabling it.
The workaround is to disable F10 binding in Ubuntu Unity Compiz plugin:
> "CompizConfig Settings Manager" / "Ubuntu Unity Plugin" /
> "Key to open the first panel menu"
Either this binding should be disabled by default, or somehow cooperate with programs that require to free it (i.e. gnome-terminal).
summary: |
- gnome-terminal captures F10 for menu even when explicitely disabled + Unity Compiz plugin captures F10 for menu even when explicitly disabled + in gnome-terminal |
description: | updated |
Changed in unity: | |
status: | New → Incomplete |
Changed in unity (Ubuntu): | |
status: | New → Incomplete |
Changed in unity: | |
importance: | Undecided → Wishlist |
Changed in unity (Ubuntu): | |
importance: | Undecided → Wishlist |
Cleaning gconf entries and reboot does not help, the F10 is still captured.