After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 93445 - Allow setting smooth (threshold 0) mouse acceleration.
Allow setting smooth (threshold 0) mouse acceleration.
Product: gnome-control-center
Classification: Core
Component: Mouse
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 94208 557116 (view as bug list)
Depends on:
Blocks: 586238
Reported: 2002-09-17 00:17 UTC by Tuukka Tolvanen
Modified: 2015-08-06 07:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10

Description Tuukka Tolvanen 2002-09-17 00:17:16 UTC
If I wanted the pointer to jump erratically at a
certain treshold speed, I'd be using a kangaroo
instead of a mouse :) The control center "Mouse
Preferences" dialog should allow setting mouse
accel. 'treshold' a.k.a. 'sensitivity' value to 0,
and give more fine-grained control over the
'acceleration' value range 1...2.

Mouse Preferences currently seems to allow:
  acceleration: 3/10 4/10 5/10 6/10 7/10 8/10 9/10
10/10 1/1 3/2 2/1 5/2 3/1 7/2 4/1 9/2 5/1 11/2 6/1
   treshold: 1, 2, ... , 10

With treshold 0, the acceleration value should be
controllable by a granularity of say 1/10 at
least, preferably something like 1/20; all sane
settings would seem to fall within the range 1....2.

See also

GNOME Control Center (Debian experimental
Comment 1 Andrew Sobala 2002-11-25 21:47:00 UTC
See also bug 94208
Comment 2 Christian Neumair 2004-07-20 18:16:38 UTC
Nobody likes that threshold thingie. Why don't trash it and assume 0, adapting
the other slider to be our granularity switch?

Comment 3 Sebastien Bacher 2004-11-26 17:25:13 UTC
*** Bug 94208 has been marked as a duplicate of this bug. ***
Comment 4 Sebastien Bacher 2006-05-30 11:15:15 UTC
Ubuntu points that the sensitivity range might need to be adapted, users don't really notice the difference with the current values scale
Comment 5 Jens Granseuer 2008-12-01 20:39:49 UTC
*** Bug 557116 has been marked as a duplicate of this bug. ***
Comment 6 Jens Granseuer 2008-12-09 19:27:11 UTC
*** Bug 563777 has been marked as a duplicate of this bug. ***
Comment 7 bi2h5da02 2009-01-04 23:49:54 UTC
Setting threshold to 0 just means there is a constant speed, right?  So shouldn't this be a toggle for "turn off acceleration" rather than a setting on a slider?

Really, we need better acceleration than this two-speed hack built into X.  Is there a way to get an actual smooth curve for acceleration?
Comment 8 bi2h5da02 2009-01-05 00:40:25 UTC
Sorry, I guess there are different meanings of "change threshold to zero".

"xset m 5" seems to do a default threshold size and then 5 times the speed outside of that range.  Very jumpy

"xset m 5 0" uses the smooth acceleration that isn't jumpy.

"xset m 5 1" would do 5 times the speed almost constantly

Really we should be using the smooth acceleration all the time.
Comment 9 Ondrej Holy 2015-08-06 07:36:54 UTC
A lot of changed since the bug was reported. We have now libinput and only what can be set is pointer acceleration speed within a range of [-1, 1], see:

Please file a bug against libinput if you are not satisfied with the behavioral.