Bug#624397: xserver-xorg-input-synaptics: ALPS GlidePoint no longer working properly
On 04/28/2011 12:15 AM, Julien Cristau wrote:
> On Wed, Apr 27, 2011 at 23:48:18 -0700, Ludovico Cavedon wrote:
> Looks like udev b0rkage to me.
>
>> [ 24.500] (II) config/udev: Adding input device AlpsPS/2 ALPS GlidePoint (/dev/input/event2)
>> [ 24.500] (**) AlpsPS/2 ALPS GlidePoint: Applying InputClass "evdev keyboard catchall"
>> [ 24.500] (**) AlpsPS/2 ALPS GlidePoint: always reports core events
>> [ 24.500] (**) AlpsPS/2 ALPS GlidePoint: Device: "/dev/input/event2"
>> [ 24.500] (--) AlpsPS/2 ALPS GlidePoint: Found 3 mouse buttons
>> [ 24.500] (--) AlpsPS/2 ALPS GlidePoint: Found absolute axes
>> [ 24.500] (--) AlpsPS/2 ALPS GlidePoint: Found x and y absolute axes
>> [ 24.500] (--) AlpsPS/2 ALPS GlidePoint: Found absolute touchpad.
>> [ 24.500] (II) AlpsPS/2 ALPS GlidePoint: Configuring as touchpad
>> [ 24.500] (**) AlpsPS/2 ALPS GlidePoint: YAxisMapping: buttons 4 and 5
>> [ 24.500] (**) AlpsPS/2 ALPS GlidePoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
>> [ 24.500] (II) XINPUT: Adding extended input device "AlpsPS/2 ALPS GlidePoint" (type: TOUCHPAD)
>> [ 24.500] (II) AlpsPS/2 ALPS GlidePoint: initialized for absolute axes.
>
> It's being added as a keyboard (using the evdev driver) instead of a
> touchpad (using synaptics).
Uhm
> Make sure you don't have a /run directory in your root filesystem.
Well, I actually did...
I removed it and it fixed my issue! Thanks!
I guess I should reassign this issue to udev, right? Is there any
additional information that you think would be relevand for udev
maintainers?
Thanks,
Ludovico
Reply to: