After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 669935 - Disable menu shortcut key (F10) does not work correctly
Disable menu shortcut key (F10) does not work correctly
Status: RESOLVED DUPLICATE of bug 661973
Product: gnome-terminal
Classification: Core
Component: general
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-12 18:20 UTC by Tony Houghton
Modified: 2012-02-12 18:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tony Houghton 2012-02-12 18:20:20 UTC
When the "Enable menu shortcut key (F10)" option is disabled the menu still gets opened when you press F10. The only difference is that with the option disabled additional characters are sent to the terminal, and it prints the message "Gtk-CRITICAL **: gtk_device_grab_add: assertion `GDK_IS_DEVICE (device)' failed" to the parent console, if any.

This bug was reported for roxterm, in Debian and Arch Linux at least, but as it uses a similar technique to (try to) disable the menu as gnome-terminal I thought I'd try reporting it against g-t before GTK3 in case it's because we've both made a similar mistake and you might know how to fix it. roxterm-gtk2 is not affected, and it doesn't report the additional error message about gtk_device_grab_add.
Comment 1 Tony Houghton 2012-02-12 18:34:53 UTC
Sorry, I should have checked gtk3 bugs first.

*** This bug has been marked as a duplicate of bug 661973 ***