FS#29573 - [xf86-input-synaptics] Fix coasting friction

Attached to Project: Arch Linux
Opened by Butcher Blues (Butcher) - Monday, 23 April 2012, 15:01 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 27 April 2012, 13:02 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Coasting has been always disabled, but now it seems that it's enabled by default. For me, and I suppose that for more users too, it's a pain in the ass: it generally scrolls when you don't want to, i.e., it starts scrolling when you're not doing it on purpose. It should be an opt-in feature.

Please disable it by default: «Option "CoastingSpeed" "0"» in /etc/X11/xorg.conf.d/10-synaptics.conf.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Friday, 27 April 2012, 13:02 GMT
Reason for closing:  Fixed
Comment by Ionut Biru (wonder) - Monday, 23 April 2012, 16:16 GMT
+1 for disabling coasting by default.
Comment by Andrea Scarpino (BaSh) - Monday, 23 April 2012, 18:03 GMT
I agree too.
Comment by Andrea Scarpino (BaSh) - Wednesday, 25 April 2012, 12:37 GMT
  • Field changed: Task Type (Feature Request → Bug Report)
  • Field changed: Category (Packages: Extra → Upstream Bugs)
This is upstream: https://bugs.freedesktop.org/show_bug.cgi?id=48855

Patch: http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?id=1c155f644824133315ac5b3dac9076db71430eb6
Comment by Ben Morgan (uv.sound) - Wednesday, 25 April 2012, 13:10 GMT
The default coasting value seems quite reasonable to me;
the main problem was the upstream bug, was it not?
Comment by Andrea Scarpino (BaSh) - Wednesday, 25 April 2012, 13:12 GMT
  • Field changed: Summary ([xf86-input-synaptics] Disable CoastingSpeed by default → [xf86-input-synaptics] Fix coasting friction)
@Ben
Yes
Comment by Andreas Radke (AndyRTR) - Friday, 27 April 2012, 12:10 GMT
Can we close this as "fixed" with 1.5.99.904 release?
Comment by Simonas (nagi) - Friday, 27 April 2012, 12:21 GMT
Yup, it is fixed.

Loading...