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 158993 - Incorrect behavior for ctrl+shift + keypad keys when numlock is off
Incorrect behavior for ctrl+shift + keypad keys when numlock is off
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
2.4.x
Other Linux
: Normal normal
: Small fix
Assigned To: gtk-bugs
gtk-bugs
: 342645 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-11-21 22:21 UTC by Omry Yadan
Modified: 2018-05-02 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Omry Yadan 2004-11-21 22:21:57 UTC 
in most text editors (eclipse. gedit, firefox text area), ctrl + shift +
left/right selects a word left/right.
however, when I try it with the keypad, when numlock is off it inserts a unicode
character with the value 4 or 6 instead of selecting left/right.
When my numlock of off, I expect the keypad keys to behave the same way as the
arrow keys.
Comment 1 Omry Yadan 2004-11-23 22:53:51 UTC 
another varient of the same problem:
with num-lock off, pressing shift + kpdown prints '2' instead of acting like
shift + down.
Comment 2 Omry Yadan 2005-01-08 08:36:41 UTC 
guys, sorry to nudge, but this bug is really annoying me.
I am used to selecting words with ctrl + shift + keypad keys, and it won't work
because of this bug.
Comment 3 Omry Yadan 2005-10-02 21:58:53 UTC 
pong.
Comment 4 Frank Raiser 2005-10-03 00:00:46 UTC 
I have the same behavior here, but want to add that it depends on whether the
left or right ctrl key is being used.
With NumLock off I have the same problems with the left ctrl key being used.
Switching NumLock on simply inverses this and gives the same problems for the
right ctrl key.
In both scenarios the other ctrl key works fine however.
Comment 5 Ken Chau 2006-04-15 19:37:19 UTC 
This has to do with the gtk immodule. If you did a GTK_IM_MODULE=xim, you can turn off the GTK input module - though you lose a bunch of functionality. I actually have confirmed this with a command like this:

GTK_IM_MODULE=xim gedit

What the devs should do is to pay attention to the numlock state when the Ctrl-Shift is used.
Comment 6 Daniel Boles 2017-08-24 22:40:07 UTC 
*** Bug 342645 has been marked as a duplicate of this bug. ***
Comment 7 GNOME Infrastructure Team 2018-05-02 14:04:55 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/239.