Further investigation of this issue has seen me return to the vanilla Xorg.conf (without SHMConfig turned on). The issue can be described more simply as follows.
1. syndaemon, as launched by the default Intrepid install, is using XInput to change the touchpad properties. 2. synclient uses SHMConfig to change touchpad properties, and requires SHMConfig to be set in Xorg.conf, even though it isn't by default. 3. /etc/acpi/asus-touchpad.sh uses synclient to toggle the enabled state of the touchpad. Trying to use a mixed SHMConfig/XInput solution to control touchpad properties caused the issue I described initially. There are two solutions to this that I can see. One is to update synclient to use XInput instead of SHMConfig, to be in line with the recently-updated syndaemon. The other, which I have implemented as a workaround, is to edit the asus-touchpad.sh script to use XInput to toggle the touchpad on and off. The modified asus-touchpad.sh is attached; it now works correctly with syndaemon. ** Attachment added: "modified asus-touchpad.sh, works through `xinput` instead of `synclient` now" http://launchpadlibrarian.net/20235392/asus-touchpad.sh -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
