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