Yeah -R was way too unstable to continue enabling and it was even
disabled in a SRU in natty (the one release that ever had it enabled)
because of it. This could be worked around easily by calling syndaemon
with -m 500 in gnome-settings-daemon which is responsible for spawning
it, with a patch like the attached one. The problem is the syndaemon man
page warns about pitfalls of too high values so getting this right might
take some trial and effort introducing bugs to people and I'm not sure 5
wakeups/second is worth it.
-m <poll-interval>
How many milliseconds to wait between two polling intervals.
If this value is too low, it will cause unnecessary wake-ups. If this
value is too high, some key presses (press and release happen
between two intervals) may not be noticed. This switch has no effect
when running with -R. Default is 200ms.
** Patch added: "launch syndaemon with an increased poll interval in
gnome-settings-daemon"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/906987/+attachment/2788500/+files/0001-Increase-syndaemon-poll-interval-to-500ms.patch
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
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/906987
Title:
syndaemon polls 5 times a second even though it is started with the -R
XRecord extension option
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/906987/+subscriptions
_______________________________________________
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
