GsdDeviceManager recognizes my keyboard as mouse
@felipeborges
Submitted by Felipe Borges Link to original bug (#757016)
Description
I have a Cherry GmbH CyMotion Master Linux Keyboard G230, which gets recognized as mouse when I run gnome-settings-daemon/plugins/common/gsd-test-input-helper
./gnome-settings-daemon/plugins/common/gsd-test-input-helper Has touchpad: yes Has touchscreen: no Has trackball: no Device 'TPPS/2 IBM TrackPoint' is a mouse Device 'HID 046a:0023' is a mouse Device 'ThinkPad USB Laser Mouse' is a mouse Device 'Integrated Camera' is a keyboard Device 'ThinkPad Extra Buttons' is a keyboard Device 'Video Bus' is a keyboard Device 'Video Bus' is a keyboard Device 'HID 046a:0023' is a keyboard Device 'AT Translated Set 2 keyboard' is a keyboard Device 'Power Button' is a keyboard Device 'Sleep Button' is a keyboard Device 'SynPS/2 Synaptics TouchPad' is a touchpad
My keyboard does not have any mouse capabilities, although evtest shows that it can send Event code 6 (RHEL_HWHEEL) event. More on http://fpaste.org/282857/95134144/
The implication of that is that control-center/mouse thinks I have a mice even when I don't have any plugged in. control-center/mouse gets its devices from a gsd_device_manager_list_devices list.
For xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=16 [slave pointer (2)] ⎜ ↳ ThinkPad USB Laser Mouse id=11 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Video Bus id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ Integrated Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=17 [slave keyboard (3)] ↳ HID 046a:0023 id=13 [slave keyboard (3)]
It might be a bug deeper in the stack.