Bug 407541 - maximum sensitivity is too low (< 1.0)
maximum sensitivity is too low (< 1.0)
Product: Fedora
Classification: Fedora
Component: system-config-mouse (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Denise Dumas
Depends On:
  Show dependency treegraph
Reported: 2007-12-01 16:55 EST by Mikel Ward
Modified: 2009-01-09 00:23 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 00:23:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mikel Ward 2007-12-01 16:55:01 EST
I have a touchpad on my laptop.  I tried to set the motion sensitivity to
maximum so I could get across my screen in one pass, but even at maximum
sensitivity it's far too slow.

I found out that the "maximum" setting sets something in xorg.conf to about 0.35
and 0.70 (my laptop's battery is flat, will confirm later).  If I manually
change them to 1.0 and 1.0, it is much better.

It should be possible to do this using the mouse configuration applet.
Comment 1 Mikel Ward 2007-12-02 20:30:26 EST
Section "InputDevice"
    Identifier  "Synaptics"
    Driver      "synaptics"
    Option      "Device" "/dev/input/mice"
    Option      "Protocol" "auto-dev"
    Option      "Emulate3Buttons" "yes"
    Option      "LeftEdge" "120"
    Option      "RightEdge" "830"
    Option      "TopEdge" "120"
    Option      "BottomEdge" "650"
    Option      "FingerLow" "14"
    Option      "FingerHigh" "15"
    Option      "MaxTapMove" "110"
    Option      "VertScrollDelta" "20"
    Option      "HorizScrollDelta" "20"
    Option      "MinSpeed" "0.3"
    Option      "MaxSpeed" "0.75"

MinSpeed and MaxSpeed set to 1.0 gives much better results.

I installed gsynaptics to try to configure this, but it's not currently enabled,
and doesn't seem to influence the sensitivity anyhow.  (It controls things like
the touch sensitivity and scrolling settings, but not the motion speed.)
Comment 2 Mikel Ward 2008-02-07 18:39:59 EST
Any thoughts on this?  Should I file it upstream?
Comment 3 Bug Zapper 2008-11-26 03:46:32 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Bug Zapper 2009-01-09 00:23:18 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.