In the meantime i also spent some time on analysing, and found out, that Option "SHMConfig" "On" (not "true") solved the issue of not beeing able to adjust fingerHigh/fingerLow with synclient for me. The sensitivity settings one can make in the kde-gui-touchpad are still not useful and when the notebook heats up, one might have to change sensitivity again. The SHMConfig flag and some related settings have been deactivated by the update process, according to the comments inserted in xorg.conf due to HAL things.
...so it's now just snd-hda-intel (mic) that forces me to use Windows. Zitat von Jonas Petersson <240...@bugs.launchpad.net>: > @itismike > Well, it might be sort of related. I'm pretty sure it worked when I booted > from the live CD (as did the screen backlight keys, but I'm not sure it was > using nvidia at the time), so something is different from that state and it > may well be that the difference is the SHMConfig flag. If so, it makes fair > sense that without SHMConfig the syndaemon will be unable to adjust the > touchpad. > > -- > You received this bug notification because you are a direct subscriber > of a duplicate bug (577764). > https://bugs.launchpad.net/bugs/240738 > > Title: > syndaemon sometimes fails to disable the touchpad > > Status in âxserver-xorg-input-synapticsâ package in Ubuntu: > Confirmed > > Bug description: > Binary package hint: xserver-xorg-input-synaptics > > syndaemon does not always disable the touchpad when a key is pressed. > > Steps to reproduce: > > * Turn on SHMConfig in /etc/X11/xorg.conf and restart X. > * $ killall syndaemon > * $ syndaemon -i 3 -k -t > * Run another application such as gedit and press a single key (not a > modifier key) while watching the syndaemon window. It should print > 'Disable', wait 3 seconds, and then 'Enable'. Most of the time this works as > expected, but a small percentage of the time nothing new is displayed in the > syndaemon window (the gedit window displays the key as expected). The timing > seems important; if the key is pressed between 1 and 3 seconds after > syndaemon displays 'Enable' then the key is more likely to be missed by > syndaemon. > > This problem sounds minor but has been a major source of aggravation > while typing on my laptop because a few times a day I find myself > typing in another part of the document or in a different application > altogether. Depending on the application which is incorrectly > receiving the key presses, the consequences could be serious. > > This is on Ubuntu 8.04 and xserver-xorg-input-synaptics > 0.14.7~git20070706-mactel1, but I believe this problem has existed for > many months. The hardware is an Apple MacBook 2nd generation. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/240738/+subscribe > > -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/240738 Title: syndaemon sometimes fails to disable the touchpad _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
