GNOME Bugzilla – Bug 567339
F10 invokes terminal menu even if not enabled in "Keyboard shortcuts" dialog
Last modified: 2009-02-25 18:27:19 UTC
Please describe the problem: It seems that for some people (amd64?) not enabling F10 as shorcut for terminal menu still makes F10 invoke the terminal menu. It is annoying, since some F10 is not passed to terminal apps (aptitude, mc). Steps to reproduce: 1. Launch gnome-terminal 2. Go Edit/Keyboard Shortcuts, UNcheck "Enable the menu shortcut key (F10 by default)" 3. Run midnight commander or aptitude in that terminal 4. Press F10 Actual results: Terminal menu is brought up. Expected results: Program-specific menu should be invoked, but it doesn't happen as terminal eats the keypress. Does this happen every time? Yes. Other information: https://bugs.launchpad.net/gnome-terminal/+bug/198628 is the original bugreport in ubuntu, which also contains workaround (to be put in ~/.gtkrc-2.0). This bug doesn't affect everybody, though it is not clear who is affected -- perhaps amd64 systems, as suggested above.
Not reproducible here. There's nothing in this code path that seems to be 64bit specific... First, please verify that you're running gnome-terminal at least version 2.24.x (from Help, About menu). Then look up this gconf value: gconftool-2 --get /apps/gnome-terminal/global/use_menu_accelerators and see if it corresponds to what the Edit, Keybindings dialogue thinks the value is. Please try this: Close all gnome-terminal windows, make sure g-t isn't running (check using the "ps" command in an xterm), then start gnome-terminal from an xterm. Is there any output from gnome-terminal on the xterm? Now toggle the setting from the Edit, Keybindings dialogue, on and off and off and on. Any output? Still not working? Using gdb, step through terminal_screen_class_enable_menu_bar_accel_notify_cb to see a) if it's executed at all (it should be), and b) the values of the enable and is_enabled values.
No response; closing. Please re-open if you can provide the necessary information.