Unity Compiz plugin captures F10 for menu even when explicitly disabled in gnome-terminal

Bug #750700 reported by Paul Ortyl
134
This bug affects 31 people
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).

Revision history for this message
Paul Ortyl (ortylp) wrote :
Revision history for this message
Paul Ortyl (ortylp) wrote :

Cleaning gconf entries and reboot does not help, the F10 is still captured.

Revision history for this message
Paul Ortyl (ortylp) wrote :

The offending "plugin" has been found...

"CompizConfig Settings Manager"/"Ubuntu Unity Plugin"/"Key to open the first panel menu"

Revision history for this message
Thomas Krause (krause) wrote :

This bug is explicitly annoying when using midnight commander (mc) or htop regulary.

Revision history for this message
Samuel Hangouët (samuel-hangouet) wrote :

Same problem for me : vim users are used to map F1->F12 keys for shortcuts.

Revision history for this message
Yury V. Zaytsev (zyv) wrote :

People are already complaining to us about it. For now you can use Esc + 0 to quit mc if F10 is captured by gnome-terminal.

Revision history for this message
Yury V. Zaytsev (zyv) wrote :

I am re-assigning this to Unity since apparently it is the root cause of all these problems.

Changed in gnome-terminal (Ubuntu):
status: New → Invalid
Revision history for this message
Yury V. Zaytsev (zyv) wrote :

To be more specific, I think that

> "CompizConfig Settings Manager" / "Ubuntu Unity Plugin" /
> "Key to open the first panel menu"

should be deactivated by default, because it causes a lot of trouble to quite a bit of unsuspecting people. Otherwise, if F10 is disabled in gnome-terminal it should also disable Unity binding. I don't know if this is feasible though.

Revision history for this message
Cristi (mcvconsult) wrote :

you have my vote on disabling the F10 in ubuntu unity plugin.

Yury V. Zaytsev (zyv)
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
Revision history for this message
David (daplappert) wrote :

bump this up ... this is one of those little annoying things.

Thanks!!

Revision history for this message
Paul Ortyl (ortylp) wrote :

Does the "Invalid" status mean, that nobody cares? I understand, that it is not a problem of gnome-terminal, but the bug must not disappear without a trace in a bag of other "Invalid" bugs.
Shouldn't there be new bug for Unity about this issue?
A bug, that would be referenced here somehow?

Revision history for this message
Yury V. Zaytsev (zyv) wrote :

Invalid means that it is not a bug in gnome-terminal. It has the status "New" in Unity.

Alex Launi (alexlauni)
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
Revision history for this message
joopbraak (joopbraak) wrote :

Alex, why is this being marked Incomplete (what more info do you need t solve this ) and why Wishlist?

It's not Wishlist, Unity is interfering with the terminal so function keys are not disabled for menu's even if you tell it to do so, and that's a Bug, it's even a regression because it used to work in Maverick.

By the way, I think it's bad practice to bind function keys (without Alt or Ctrl, that is) to desktop environment commands, they should be reserved for applications.

One of those bad Unity design decisions, I guess...

Revision history for this message
Sergey K (koblin) wrote :

Wishlist?
I agree with joopbraak, this is a bug of unity or gnome-terminal or both.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.