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

2010-12-01 Thread Bryce Harrington
Looks like this already got fixed a while back.  Only difference is
instead of setting Device Enabled it sets Synaptics Off, which I assume
is sufficient else we'd have a lot more people complaining about broken
touchpads.  ;-)

I kinda suspect this setting should be done via a udev rule rather than
an acpi script, but that's a whole other kettle of fish...

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: Confirmed = Fix Released

-- 
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


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

2010-11-24 Thread 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
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


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

2009-09-02 Thread Bryce Harrington
** Tags added: intrepid

-- 
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


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

2009-04-07 Thread Bryce Harrington
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: Incomplete = Confirmed

-- 
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


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

2009-01-17 Thread Bryce Harrington
** Description changed:

  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=948250page=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.
+ 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]

-- 
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


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

2008-12-05 Thread Derek Monner

** Attachment added: output of `lspci -vvnn`
   http://launchpadlibrarian.net/20235288/lspci.out

-- 
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


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

2008-12-05 Thread Derek Monner
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


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

2008-12-04 Thread Bryce Harrington
[This is an automated message]

Hi dmonner,


Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log 
file from after reproducing this issue.  If you've made any customizations to 
your /etc/X11/xorg.conf please attach that as well.


** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: New = Incomplete

-- 
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