Bug 723446

Summary: Scrollwheel too fast using Microsoft IntelliMouses
Product: [Fedora] Fedora Reporter: PhilippP <philipp.press>
Component: mousetweaksAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 19CC: belegdol, homer.xing, jah, mclasen, peter.hubbard.2010, trevor
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 556275 Environment:
Last Closed: 2015-02-18 13:35:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description PhilippP 2011-07-20 08:26:36 UTC
+++ This bug was initially created as a clone of Bug #556275 +++

Description of problem:
Scrolling with a newer Microsoft mouse is too fast. The tracking


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Run 'xev' 
2. Move the scrollwheel up or down a small amount
3. Note how approx. 5 entries are displayed per 'notch' of the scrollwheel.
  
Actual results:
ButtonPress event, serial 33, synthetic NO, window 0x5600001,
    root 0x142, subw 0x0, time 7029513, (167,126), root:(176,221),
    state 0x0, button 5, same_screen YES

ButtonRelease event, serial 33, synthetic NO, window 0x5600001,
    root 0x142, subw 0x0, time 7029513, (167,126), root:(176,221),
    state 0x1000, button 5, same_screen YES

ButtonPress event, serial 33, synthetic NO, window 0x5600001,
    root 0x142, subw 0x0, time 7029513, (167,126), root:(176,221),
    state 0x0, button 5, same_screen YES

ButtonRelease event, serial 33, synthetic NO, window 0x5600001,
    root 0x142, subw 0x0, time 7029513, (167,126), root:(176,221),
    state 0x1000, button 5, same_screen YES

ButtonPress event, serial 33, synthetic NO, window 0x5600001,
    root 0x142, subw 0x0, time 7029513, (167,126), root:(176,221),
    state 0x0, button 5, same_screen YES

ButtonRelease event, serial 33, synthetic NO, window 0x5600001,
    root 0x142, subw 0x0, time 7029513, (167,126), root:(176,221),
    state 0x1000, button 5, same_screen YES

ButtonPress event, serial 33, synthetic NO, window 0x5600001,
    root 0x142, subw 0x0, time 7029513, (167,126), root:(176,221),
    state 0x0, button 5, same_screen YES

ButtonRelease event, serial 33, synthetic NO, window 0x5600001,
    root 0x142, subw 0x0, time 7029513, (167,126), root:(176,221),
    state 0x1000, button 5, same_screen YES


Expected results:
Only one ButtonPress/ButtonRelease event per 'notch' of the scrollwheel.


Additional info:
The problem exists in Windows as well. Apparently the 'delta' for the scrollwheel was changed in newer drivers, to support more finegrained control of the scrollwheel in future devices. This delta always used to be '120'. A code solution for Windows explains this better: http://nwn2forums.bioware.com/forums/viewtopic.html?topic=622848&forum=116

"with the Microsoft Mouse driver (other drivers may also be involved, but the latest MS drivers is certain), it is possible to receive rotation values UNDER 120. For example, if the wheel is moved slowly, you'll get two 60's instead, or a 54 and 72, etc. So if your code was something like:

scrollby = ((short)HIWORD(wParam)) / 120;

Then you'd be screwed, as the rounding would give you zero. Only big scroll events would exceed the 120 mark, slow scrolling would get dropped - with very bad results.



Interestingly, the very latest MSDN docs still have the above line in them, but have added:

The delta was set to 120 to allow Microsoft or other vendors to build finer-resolution wheels in the future, including perhaps a freely-rotating wheel with no notches. The expectation is that such a device would send more messages per rotation, but with a smaller value in each message. To support this possibility, you should either add the incoming delta values until WHEEL_DELTA is reached (so for a delta-rotation you get the same response), or scroll partial lines in response to the more frequent messages. You could also choose your scroll granularity and accumulate deltas until it is reached."

--- Additional comment from triage.org on 2010-11-03 20:44:13 EDT ---


This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from triage.org on 2010-12-03 19:16:09 EST ---


Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

Comment 1 Julian Sikorski 2011-11-26 22:48:24 UTC
I am not sure if you are seeing a similar issue as me, but I am observing something similar with Wireless Mouse 6000, and Explorer Touch Mouse I replaced it with. Whenever I booted into Windows and then reboot into Fedora, the scroll wheel would be way too fast. A workaround is to disconnect and reconnect the mouse, but obviously it would be much nicer if this step weren't necessary.

Comment 2 Julian Sikorski 2011-11-26 22:57:56 UTC
The most technically detailed info is in comment 34 of this launchpad entry:
https://answers.launchpad.net/ubuntu/+question/9200

Comment 3 Fedora End Of Life 2012-08-07 17:13:06 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Julian Sikorski 2012-08-20 18:29:35 UTC
Still a problem in F-17.

Comment 5 Fedora End Of Life 2013-07-04 06:16:07 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 6 Trevor Cordes 2013-09-29 08:11:30 UTC
PhilippP and Julian, is this the same bug as what I see with my IBM ScrollPoint mouse in bug #807493.  That bug still is not fixed for me (Fedora 19), but we were making some headway until it closed and I couldn't reopen.  If it's fundamentally the same problem (needing to scale back scroll events for sensitive devices) then we can combine the bugs/resources to create a proper solution to this problem.

(In the IBM mouse, you get dozens/hundreds of events for a millisecond of scroll wheel movement!)

Comment 7 Trevor Cordes 2015-01-09 08:02:15 UTC
Hooray!  This bug is fixed upstream and the fix is now in stock Fedora 21.  I am running it now and it is 100% fixed and working perfect!

To use this fix, make a file:
/etc/X11/xorg.conf.d/99-scrollpoint.conf

with the contents:

Section "InputClass"
  Identifier "ScrollPoint"
  MatchUSBID "04b3:3100|04b3:3103|04b3:3105|04b3:3108|04b3:3109"
  Option "VertScrollDelta" "24"
  Option "HorizScrollDelta" "24"
EndSection

and restart X (ie reboot for most people).

If your mouse is different from mine (different USB ID), get its USB ID with lsusb or something and change the line above.  You may have to play with the *Delta line values to suit your taste.

Thanks to everyone involved in getting this bug fixed for those of us who love the IBM ScrollPoint mice (to go with our IBM clicky keyboards!).

I am not sure if the bug is fixed in F19 or F20 (it wasn't working for me in F19 and I didn't try F20, not sure when the commit hit Fedora).

Please close this bug against F21, or whatever.

Comment 8 Trevor Cordes 2015-01-09 08:03:45 UTC
Upstream bug link:
https://bugs.freedesktop.org/show_bug.cgi?id=48118

Also, component was/should be xorg-x11-drv-evdev or parent package.

Comment 9 Fedora End Of Life 2015-01-09 21:50:57 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 10 Fedora End Of Life 2015-02-18 13:35:22 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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