GNOME Bugzilla – Bug 661822
F10 invokes the context menu even if it is not enabled in the "Keyboard shortcuts" dialog
Last modified: 2011-10-30 10:40:18 UTC
Steps to reproduce: * Launch gnome-terminal. * Go Edit/Keyboard Shortcuts, UNcheck "Enable the menu shortcut key (F10 by default)." * Press F10. Actual results: The context menu of gnome-terminal is brought up below the mouse pointer. The character "~" is printed in the terminal. Expected results: Nothing. If gnome-terminal runs Midnight Commander, Midnight Commander also reacts to F10. This bug is introduced in versions >2.30 and <=3.2. Bug #567339 looks similar.
F10 is not supposed to show the context menu; that's what usually happens using Shift-F10. Are you using ubuntu's global menu, perhaps? If so, try without, and try to repro using either metacity or gnome-shell (unity is NOT supported).
*** This bug has been marked as a duplicate of bug 661973 ***
I am using Arch Linux. Shift-F10 has no effect at all on "gnome-terminal". Though I never used this key combination. metacity 2.34.1-1 python-metacity 2.32.0-8 xkeyboard-config 2.4.1-1 No "gnome-shell". Should I run "gnome-terminal" without other Gnome programs, in a clean Xorg?
After downgrading "xkeyboard-config" to 2.2.1-1, "gnome-terminal" responds to F10 with no menu and with "~" and to Shift-F10 with the menu and ";2~"! But is the garbage ";2~" supposed to be?
Yes, when the UI isn't handling these keys they're forwarded to the app running in the terminal; bash just doesn't do anything with them.
*** Bug 662531 has been marked as a duplicate of this bug. ***
*** Bug 663040 has been marked as a duplicate of this bug. ***