Created attachment 30839 [details] Xorg log file With recent versions my touchpad stopped accepting taps. I can change that manually by calling synclient -s TapButton1=1 ... although I have entered these values into the xorg.conf file: Section "InputDevice" Identifier "ALPS Touchpad" Driver "synaptics" Option "Protocol" "auto-dev" ... Option "TapButton1" "1" ... Interestingly the Xorg.0.log somehow seems to mention two touchpad devices: (II) Synaptics touchpad driver version 1.1.2Now (--) 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 later on (II) config/hal: Adding input device AlpsPS/2 ALPS GlidePoint (II) Synaptics touchpad driver version 1.1.2 (**) Option "Device" "/dev/input/event7" Now what I don't understand why my settings are not honoured in this case. Furthermore, somehow related, switching to the console and back to X makes tapping again disappear, with log lines like: (II) AIGLX: Suspending AIGLX clients for VT switch (II) Open ACPI successful (/var/run/acpid.socket) (II) AIGLX: Resuming AIGLX clients after VT switch (II) intel(0): No memory allocations (--) ALPS Touchpad: touchpad found (WW) AlpsPS/2 ALPS GlidePoint can't grab event device, errno=16 (--) AlpsPS/2 ALPS GlidePoint: touchpad found (II) Sony Vaio Keys: Device reopened after 1 attempts. (II) AT Translated Set 2 keyboard: Device reopened after 1 attempts. (II) UVC Camera (05ca:18b0): Device reopened after 1 attempts. (II) Power Button: Device reopened after 1 attempts. (II) Video Bus: Device reopened after 1 attempts. (II) PS/2 Mouse: Device reopened after 1 attempts. In case you need more software information: Debian/unstable kernel 2.6.32-rc5 synaptics-input 1.1.2 (debian release -2) I attache the xorg.conf and Xorg.0.log file Hope that helps. Please let me know if you need more information. All the best Norbert
Created attachment 30840 [details] xorg config file
This issue has been fixed in release 1.2.0 of the driver. The touchpad is added twice, once when the xorg.conf section is parsed with the options you specified, and once when the device is listed by HAL. Only the xorg.conf device has the options you want, the other is started with the default options. The "cant grab event device error" signals that the device has already been added, in 1.2.0 we fail to add the second one and skip that device. The simplest way to fix this is to move your configuration to HAL or to update the driver to version 1.2.0.
Thanks Peter, I confirm that this is fixed with the 1.2 release. I have build my own module and it now works as expected. In fact there were two issues here, one was the double device, the other was the not working taps. That came from something different as it turned out, namely that some gnome program (gnome-settings-daemon) suddenly wants to configure the touchpad itself and does not honor the already made settings in xorg.conf. I have filed a Debian bug (552279) against it. Thanks a lot for your work and all the best Norbert
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.