Thanks. So it seems the MS keyboard indeed is like two input devices in
one, one for the normal keys, one for the hotkeys. This is very similar
to Sony or Thinkpad modules, which also have a separate "input module"
for their hotkeys. The input-events output for device 3 looks fine. The
EV_MSC ones are MSC_SCAN events (for the scan code), which also happen
on normal keys, also on my system. I don't see any EV_BTN. I don't see
any EV_KEY BTN_* events on this device, and input_id also doesn't say
that it's a mouse, so it looks correct from the kernel and udev
perspective.

Chris, any idea what causes the xorg evdev driver to think that this
device is a mouse? What properties does it check for?

-- 
Keyboard special keys interfere with mouse
https://bugs.launchpad.net/bugs/636311
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to     : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

Reply via email to