[Bug 300523] Re: syndaemon turns disabled touchpad back on after typing

[Gursimran singh Mohar]

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Importance: Undecided => Low

-- 
syndaemon turns disabled touchpad back on after typing
https://bugs.launchpad.net/bugs/300523
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in “xserver-xorg-input-synaptics” package in Ubuntu: Confirmed

Bug description:
When I upgraded to Ubuntu 8.10, the button on my Asus laptop that toggled the touchpad on and off stopped working. The button is controlled by the included /etc/acpi/asus-touchpad.sh, which uses synclient to toggle the touchpad state. I turned on SHMConfig in my Xorg.conf and the button started working again.

Now, however, when I have the touchpad disabled, syndaemon (run with -i 0.5) will re-enable it after I type something. This behavior was not observed in Ubuntu 8.04; I expect that syndaemon will set the touchpad back to its previous state after the typing timeout, as opposed to always returning it to the "enabled" state. My current workaround for this is to run syndaemon with -S, which apparently causes it to use the SHMConfig-based system instead of the new XInput-based system (reference: http://ubuntuforums.org/showthread.php?t=948250&page=2).

So, it seems to me that the XInput-based syndaemon should get this behavior right too, unless of course the asus-touchpad.sh script is toggling the touchpad status in an incorrect way.
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 04)
    	Subsystem: ASUSTeK Computer Inc. Device [1043:1882]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04)
    	Subsystem: ASUSTeK Computer Inc. Device [1043:1882]