Comment 0 for bug 297264

kwant (kwant) wrote :

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, EmulateWheelInertia:
10, EmulateWheelTimeout: 200
(WW) 3Dconnexion SpacePilot: unable to handle keycode 265

I suspect, HAL did it, see Attachment (lshal.txt). Since I'm using spacenavd from, SpacePilot can't be configured in my X server - see FAQ:

How can I condigure 3Dconnexion SpacePilot in order to xorg ignore it???