Bug#552279: xserver-xorg-input-synaptics: synaptics does not match config in xorg.conf with the real device
On Sun, Oct 25, 2009 at 12:21:21 +0900, Norbert Preining wrote:
> Package: xserver-xorg-input-synaptics
> Version: 1.1.2-1
> Severity: important
>
> I found the reason why my tapping disappeared: the synaptics driver
> does not recognize my input device section:
> Section "InputDevice"
> Identifier "ALPS Touchpad"
> Driver "synaptics"
> Option "Protocol" "auto-dev"
> ...
> (see below) with the real device. So I end up with two devices, one
> called "AlpsPS/2 ALPS GlidePoint" which is the auto-detected one,
> and one is "ALPS Touchpad" from the xorg.conf:
>
> from the log file below, first the touchpad from the config file:
> (II) Synaptics touchpad driver version 1.1.2
> (--) ALPS Touchpad auto-dev sets device to /dev/input/event7
> (**) Option "Device" "/dev/input/event7"
> (II) ALPS Touchpad: x-axis range 0 - 1023
> (II) ALPS Touchpad: y-axis range 0 - 767
> and then suddenly HAL starts again to f*** around and add a device that is
> already there (same device node)
> (II) config/hal: Adding input device AlpsPS/2 ALPS GlidePoint
> (II) Synaptics touchpad driver version 1.1.2
> (**) Option "Device" "/dev/input/event7"
> Now somehow the latter one from HAL overrides my own one. That should
> be forbidden! Unfortunately I have no idea how to hack these horrible .fdi
> files.
>
Wrong. The device file is grabbed by the driver when the first device
(the xorg.conf one) is initialized. The automatically added device then
just sits idle because it doesn't get any events.
Cheers,
Julien
Reply to: