GNOME Bugzilla – Bug 453193
accels sent to the terminal if the corresponding gtkaction is insensitive
Last modified: 2011-07-29 11:28:30 UTC
[ forwarded from http://bugs.debian.org/429890 by Tyler MacDonald ] Ctrl-+ normally increases the font size and does not echo anything to the terminal. However, if you are at the maximum font size, pressing Ctrl-+ causes gnome-terminal to echo a "+" keypress to the terminal. I am certain this is not the intended behaviour, and it can be problematic for spastic people like me who like to do things like hold down Ctrl and loudly bash "+" a few dozen times.
I got this behaviour with every part of the menu that has a shortcut and is not sensitive. Shift+Ctrl+C does the same as Ctrl+C (terminates process) if nothing selected; Shift+Ctrl+PageUp scrolls the terminal the same way of Shift+PageUp. I don't think this is intended either, but I'd like some feedback from a developer, as the behaviour is default and widespread among the whole app (btw, i checked out other gnome apps, and none of them behaves this way).
*** Bug 499934 has been marked as a duplicate of this bug. ***
*** Bug 526088 has been marked as a duplicate of this bug. ***
*** Bug 534953 has been marked as a duplicate of this bug. ***
I ran into this bug from the other end... I usually use vim on remote systems via gnome-terminal. I want to be able to press ctrl+pgup/dn to change tabs. Until 2.22.0 this worked fine, but since that version, ctrl+pgdn does not work any longer! It looks like there is a bug that causes the 'next tab' action to be enabled in a new gnome-terminal window, even though there is only one tab available; creating a new tab and then destroying it causes the action to become insensitive, and thus ctrl+pgdn works again. But my point is that I want to keep being able to switch to different (vim) tabs with the default keybindings, so I don't think it is appropriate to block keypresses from being sent through to VTE in all cases, if there are insensitive actions that would normally capture them.
(In reply to comment #5) > It looks like there is a bug that causes the 'next tab' action to be enabled in > a new gnome-terminal window Have you tried this in svn trunk ?
I just tried it and it seems my bug is fixed. This bug, of course, is still valid, though I would prefer it remain that way forever. :)
I have this problem on my Gentoo system (with Gnome 2.22.3), and on Ubuntu Hardy 8.04 (should be Gnome 2.22.1): when using vim, I was able to use PageUp, but not PageDown. After creation of a new tab, and its deletion, it was working fine. Today, I tried the svn trunk version (rev 2963), and it solved this bug for me.
Can someone please point me at the commit that fixed the problem where PageDown does not work until a tab is closed? I'd hate to be stuck with this bug during the entire release cycle of the next stable Debian release.
Sam: use the git mirror of gnome svn, and git-bisect to find the commit.
*** Bug 546237 has been marked as a duplicate of this bug. ***
*** Bug 553129 has been marked as a duplicate of this bug. ***
*** Bug 138609 has been marked as a duplicate of this bug. ***
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report. This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
I'm still seeing this in 2.30.
Don't add comments to closed bugs, they just get lost. If you can repro this on g-t 3.0 *with a gtk3 build*, *without* any buggy gtk modules (like ubuntu menuproxy, specifically) loaded, then open a new bug please.