3Dconnexcion SpacePilot works like a mouse (TrackPoint in laptop)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-input-evdev (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Binary package hint: xorg
After connection SpacePilot it starts to act as a mouse (TrackPoint), however, it souldn't. SpacePilot is automatically recognized as a mouse. There is no any configuration in /etc/xorg.conf (see Attachment), however found the following line in /var/log/Xorg.0.log (see Attachment):
(II) config/hal: Adding input device 3Dconnexion SpacePilot
(**) 3Dconnexion SpacePilot: always reports core events
(**) 3Dconnexion SpacePilot: Device: "/dev/input/event6"
(II) 3Dconnexion SpacePilot: Found x and y relative axes
(II) 3Dconnexion SpacePilot: Found 21 mouse buttons
(II) 3Dconnexion SpacePilot: Configuring as mouse
(II) XINPUT: Adding extended input device "3Dconnexion
SpacePilot" (type: MOUSE)
(**) 3Dconnexion SpacePilot: YAxisMapping: buttons 4 and 5
(**) 3Dconnexion SpacePilot: EmulateWheelButton: 4, EmulateWheelIne
10, EmulateWheelTim
(WW) 3Dconnexion SpacePilot: unable to handle keycode 265
I suspect, HAL did it, see Attachment (lshal.txt). Since I'm using spacenavd from http://
How can I condigure 3Dconnexion SpacePilot in order to xorg ignore it???
Kwant!
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c)
Subsystem: Lenovo Device [17aa:20b1]
01:00.0 VGA compatible controller [0300]: nVidia Corporation Quadro NVS 140M [10de:0429] (rev a1)
Subsystem: Lenovo Device [17aa:20d8]
description: | updated |
[This is an automated message]
Hi kwant,
Please attach the output of `lspci -vvnn` too.