Comment 3 for bug 281669

Revision history for this message
Matt Zimmerman (mdz) wrote :

The attached log shows the output from input-events when pressing shift+numlock twice consecutively.

/dev/input/event1
   bustype : BUS_I8042
   vendor : 0x1
   product : 0x1
   version : 43860
   name : "AT Translated Set 2 keyboard"
   phys : "isa0060/serio0/input0"
   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

waiting for events
[...I release the enter key from running the command...]
11:20:38.277176: EV_MSC code=4 value=42
11:20:38.277200: EV_KEY KEY_LEFTSHIFT pressed
11:20:38.277207: EV_SYN code=0 value=0
[...repeated many times...]
11:20:39.280132: EV_MSC code=4 value=69
11:20:39.280152: EV_KEY KEY_NUMLOCK pressed
11:20:39.280160: EV_SYN code=0 value=0
11:20:39.280170: EV_LED code=0 value=1
11:20:39.280176: EV_SYN code=0 value=0
11:20:39.359822: EV_MSC code=4 value=69
11:20:39.359845: EV_KEY KEY_NUMLOCK released
11:20:39.359852: EV_SYN code=0 value=0
11:20:39.720412: EV_MSC code=4 value=42
11:20:39.720435: EV_KEY KEY_LEFTSHIFT released
11:20:39.720441: EV_SYN code=0 value=0
[...then I press it a second time...]
11:20:41.397847: EV_MSC code=4 value=42
11:20:41.397874: EV_KEY KEY_LEFTSHIFT pressed
11:20:41.397881: EV_SYN code=0 value=0
[...repeats many times...]
11:20:42.206978: EV_MSC code=4 value=42
11:20:42.207005: EV_KEY KEY_LEFTSHIFT released
11:20:42.207011: EV_SYN code=0 value=0

No KEY_NUMLOCK or EV_LED event is seen for the second press.