Comment 18 for bug 602809

Revision history for this message
Joe Conway (a-mail-k) wrote :

FWIW I have been plagued with this same issue for a long time now and the libinput_debounce_time.patch above* fixes the problem for me.

Obviously hard coding these values is a bad idea -- will this ever get fixed properly?

* I had to adjust it to get it to apply on my LM20 system (libinput-1.15.5), and I used 60 ms and 30 ms instead of 100/50. Many thanks to Yei Gei (yzgyzg) for posting.