Comment 9 for bug 124440

There are multiple issues here that make the "Wishlist" importance a mistake, IMHO.

If you read the link for more information in the bug description, you'll see that the problem isn't just adjusting wheel sensitivity... the very real problem is that many wireless mice (all MS Wireless?) report MULTIPLE EVENTS on each unit scroll if the system is ever booted into Windows. The mouse should only report two events (one press, one release), but instead reports multiple such.

That makes it *impossible* to scroll only one unit in any application that does not have a scroll sensitivity *divisor*, which exactly ZERO applications do that I'm aware of.

There are two possible solutions to this:

- Implement proper sensitivity adjustment accessible in Gnome.

or, better,

- Figure out what the hell is going on with the mouse/transceiver and send commands to it to fix it.

This is essentially a driver issue and should be handled as such (option 2). That doesn't exclude ALSO implementing option 1, but option 1 is properly set to "Wishlist", whereas the real issue here is the faulty driver for oddly-behaving wireless mice. It *appears* that booting into Windows causes some sort of hardware level sensitivity to be changed, resulting in multiple events per unit scroll.

The "workaround" is to unplug the transceiver (which appears to reset it to the sane 1 press + 1 release per unit scroll), but one cannot expect dual-booters to unplug their wireless transceiver every single time they boot into Windows.