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 664619 - gdk_keymap_get_num_lock_state() returns wrong value
gdk_keymap_get_num_lock_state() returns wrong value
Status: RESOLVED NOTGNOME
Product: gtk+
Classification: Platform
Component: Backend: X11
3.3.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2011-11-23 10:00 UTC by Aaron Sowry
Modified: 2014-01-25 02:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Aaron Sowry 2011-11-23 10:00:58 UTC
Even when numlock is switched off, the warning message is displayed. Toggling numlock has no effect.

This is on a ThinkPad T410i, gnome-screensaver-3.2.0-1.fc16.x86_64.
Comment 1 Vincent Untz 2012-02-14 13:44:01 UTC
Seeing this too.
Comment 2 Vincent Untz 2012-02-14 13:53:36 UTC
I think this is actually a gtk+ bug. It's really easy to reproduce:

python -c "from gi.repository import Gdk; Gdk.init(()); d = Gdk.Keymap.get_default(); print d.get_num_lock_state()"

It always outputs True here.

It's worth mentioning I'm on a Lenovo T400. So could be an issue with Lenovo only?
Comment 3 Vincent Untz 2012-02-14 14:08:59 UTC
I'm thinking it's an issue at the kernel level, see https://bugzilla.novell.com/show_bug.cgi?id=746917
Comment 4 Matthias Clasen 2012-02-14 15:06:57 UTC
Yeah, X (and the hw) just lie about num lock. Not much we can do about it, unfortunately. 

I'm thinking that we probably should remove the numlock warning, since we can't make it work right.
Comment 5 Ray Strode [halfline] 2012-02-14 15:37:12 UTC
Still, there was a recent bug in g-s-d that might be related:

http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=ebca1ce1287679c5cb470804abfcc8de3c2d740c
Comment 6 Ray Strode [halfline] 2012-02-14 15:40:22 UTC
(related in that it may be the reason some users are seeing fishy numlock behavior, not related in the sense that there aren't other legitimate issues like those mentioned in comment 3 and comment 4)
Comment 7 Aaron Sowry 2012-02-14 15:48:39 UTC
> It always outputs True here.

Not for me. I do get some strange behaviour from evtest, however:

<snip>
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	Lid Switch
/dev/input/event1:	Sleep Button
/dev/input/event10:	HDA NVidia HDMI/DP,pcm=8
/dev/input/event11:	HDA NVidia HDMI/DP,pcm=7
/dev/input/event12:	HDA NVidia HDMI/DP,pcm=3
/dev/input/event2:	Power Button
/dev/input/event3:	AT Translated Set 2 keyboard
/dev/input/event4:	SynPS/2 Synaptics TouchPad
/dev/input/event5:	Video Bus
/dev/input/event6:	TPPS/2 IBM TrackPoint
/dev/input/event7:	ThinkPad Extra Buttons
/dev/input/event8:	Integrated Camera
/dev/input/event9:	HDA NVidia HDMI/DP,pcm=9
Select the device event number [0-12]: 3
Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x1 product 0x1 version 0xab54
Input device name: "AT Translated Set 2 keyboard"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 1 (KEY_ESC)
    Event code 2 (KEY_1)
    Event code 3 (KEY_2)
    Event code 4 (KEY_3)
    Event code 5 (KEY_4)
    Event code 6 (KEY_5)
    Event code 7 (KEY_6)
    Event code 8 (KEY_7)
    Event code 9 (KEY_8)
    Event code 10 (KEY_9)
    Event code 11 (KEY_0)
    Event code 12 (KEY_MINUS)
    Event code 13 (KEY_EQUAL)
    Event code 14 (KEY_BACKSPACE)
    Event code 15 (KEY_TAB)
    Event code 16 (KEY_Q)
    Event code 17 (KEY_W)
    Event code 18 (KEY_E)
    Event code 19 (KEY_R)
    Event code 20 (KEY_T)
    Event code 21 (KEY_Y)
    Event code 22 (KEY_U)
    Event code 23 (KEY_I)
    Event code 24 (KEY_O)
    Event code 25 (KEY_P)
    Event code 26 (KEY_LEFTBRACE)
    Event code 27 (KEY_RIGHTBRACE)
    Event code 28 (KEY_ENTER)
    Event code 29 (KEY_LEFTCTRL)
    Event code 30 (KEY_A)
    Event code 31 (KEY_S)
    Event code 32 (KEY_D)
    Event code 33 (KEY_F)
    Event code 34 (KEY_G)
    Event code 35 (KEY_H)
    Event code 36 (KEY_J)
    Event code 37 (KEY_K)
    Event code 38 (KEY_L)
    Event code 39 (KEY_SEMICOLON)
    Event code 40 (KEY_APOSTROPHE)
    Event code 41 (KEY_GRAVE)
    Event code 42 (KEY_LEFTSHIFT)
    Event code 43 (KEY_BACKSLASH)
    Event code 44 (KEY_Z)
    Event code 45 (KEY_X)
    Event code 46 (KEY_C)
    Event code 47 (KEY_V)
    Event code 48 (KEY_B)
    Event code 49 (KEY_N)
    Event code 50 (KEY_M)
    Event code 51 (KEY_COMMA)
    Event code 52 (KEY_DOT)
    Event code 53 (KEY_SLASH)
    Event code 54 (KEY_RIGHTSHIFT)
    Event code 55 (KEY_KPASTERISK)
    Event code 56 (KEY_LEFTALT)
    Event code 57 (KEY_SPACE)
    Event code 58 (KEY_CAPSLOCK)
    Event code 59 (KEY_F1)
    Event code 60 (KEY_F2)
    Event code 61 (KEY_F3)
    Event code 62 (KEY_F4)
    Event code 63 (KEY_F5)
    Event code 64 (KEY_F6)
    Event code 65 (KEY_F7)
    Event code 66 (KEY_F8)
    Event code 67 (KEY_F9)
    Event code 68 (KEY_F10)
    Event code 69 (KEY_NUMLOCK)
    Event code 70 (KEY_SCROLLLOCK)
    Event code 71 (KEY_KP7)
    Event code 72 (KEY_KP8)
    Event code 73 (KEY_KP9)
    Event code 74 (KEY_KPMINUS)
    Event code 75 (KEY_KP4)
    Event code 76 (KEY_KP5)
    Event code 77 (KEY_KP6)
    Event code 78 (KEY_KPPLUS)
    Event code 79 (KEY_KP1)
    Event code 80 (KEY_KP2)
    Event code 81 (KEY_KP3)
    Event code 82 (KEY_KP0)
    Event code 83 (KEY_KPDOT)
    Event code 85 (KEY_ZENKAKUHANKAKU)
    Event code 86 (KEY_102ND)
    Event code 87 (KEY_F11)
    Event code 88 (KEY_F12)
    Event code 89 (KEY_RO)
    Event code 90 (KEY_KATAKANA)
    Event code 91 (KEY_HIRAGANA)
    Event code 92 (KEY_HENKAN)
    Event code 93 (KEY_KATAKANAHIRAGANA)
    Event code 94 (KEY_MUHENKAN)
    Event code 95 (KEY_KPJPCOMMA)
    Event code 96 (KEY_KPENTER)
    Event code 97 (KEY_RIGHTCTRL)
    Event code 98 (KEY_KPSLASH)
    Event code 99 (KEY_SYSRQ)
    Event code 100 (KEY_RIGHTALT)
    Event code 102 (KEY_HOME)
    Event code 103 (KEY_UP)
    Event code 104 (KEY_PAGEUP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 107 (KEY_END)
    Event code 108 (KEY_DOWN)
    Event code 109 (KEY_PAGEDOWN)
    Event code 110 (KEY_INSERT)
    Event code 111 (KEY_DELETE)
    Event code 112 (KEY_MACRO)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 117 (KEY_KPEQUAL)
    Event code 118 (KEY_KPPLUSMINUS)
    Event code 119 (KEY_PAUSE)
    Event code 121 (KEY_KPCOMMA)
    Event code 122 (KEY_HANGUEL)
    Event code 123 (KEY_HANJA)
    Event code 124 (KEY_YEN)
    Event code 125 (KEY_LEFTMETA)
    Event code 126 (KEY_RIGHTMETA)
    Event code 127 (KEY_COMPOSE)
    Event code 128 (KEY_STOP)
    Event code 140 (KEY_CALC)
    Event code 142 (KEY_SLEEP)
    Event code 143 (KEY_WAKEUP)
    Event code 155 (KEY_MAIL)
    Event code 156 (KEY_BOOKMARKS)
    Event code 157 (KEY_COMPUTER)
    Event code 158 (KEY_BACK)
    Event code 159 (KEY_FORWARD)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 166 (KEY_STOPCD)
    Event code 172 (KEY_HOMEPAGE)
    Event code 173 (KEY_REFRESH)
    Event code 183 (KEY_F13)
    Event code 184 (KEY_F14)
    Event code 185 (KEY_F15)
    Event code 217 (KEY_SEARCH)
    Event code 226 (KEY_MEDIA)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
  Event type 17 (EV_LED)
    Event code 0 (LED_NUML)
    Event code 1 (LED_CAPSL)
    Event code 2 (LED_SCROLLL)
  Event type 20 (EV_REP)
Testing ... (interrupt to exit)
Event: time 1329234233.947826, type 17 (EV_LED), code 0 (LED_NUML), value 0
Event: time 1329234233.947827, -------------- SYN_REPORT ------------
Event: time 1329234233.999219, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1c
Event: time 1329234233.999224, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1329234233.999225, -------------- SYN_REPORT ------------
Event: time 1329234240.193177, type 4 (EV_MSC), code 4 (MSC_SCAN), value 45
Event: time 1329234240.193182, type 1 (EV_KEY), code 69 (KEY_NUMLOCK), value 1
Event: time 1329234240.193183, -------------- SYN_REPORT ------------
Event: time 1329234240.319625, type 4 (EV_MSC), code 4 (MSC_SCAN), value 45
Event: time 1329234240.319631, type 1 (EV_KEY), code 69 (KEY_NUMLOCK), value 0
Event: time 1329234240.319631, -------------- SYN_REPORT ------------
Event: time 1329234241.779498, type 4 (EV_MSC), code 4 (MSC_SCAN), value 45
Event: time 1329234241.779503, type 1 (EV_KEY), code 69 (KEY_NUMLOCK), value 1
Event: time 1329234241.779504, -------------- SYN_REPORT ------------
Event: time 1329234241.779781, type 17 (EV_LED), code 0 (LED_NUML), value 1
Event: time 1329234241.897845, type 4 (EV_MSC), code 4 (MSC_SCAN), value 45
Event: time 1329234241.897850, type 1 (EV_KEY), code 69 (KEY_NUMLOCK), value 0
Event: time 1329234241.897850, -------------- SYN_REPORT ------------
</snip>

This shows the result of toggling the numlock key twice - I'm not sure where the first two SYN_REPORTs come from, as I hadn't pressed anything. After pressing the numlock key twice, I get the final output you see above and then evtest stops responding to numlock toggles.

This is on Fedora 16.