Seems this is a wireless mouse. Is that correct? (I’m not sure because some microsoft product lines keep the same name across years and hardware revisions).
Only thing I can find repeatedly on an internet search suggests that the solution is to unplug/replug the receiver. (which points to some hardware/driver malfunction; these should all use the same HID driver nowadays, which leaves hardware).
This sort of thing does not appear to be due to any configuration feature that I could find any mention of, so seems likely this is pure bug…
It would be interesting to know if one tick of the scroll wheel is actually sending multiple click events. Some would recommend testing with xev, but that generates so much output that it’s hard on the eyes…
Here’s what works for me when investigating this sort of thing.
- Find the special file for this device - something like, /dev/input/event5 (varies with what you’ve got plugged in)
- sudo hexdump /dev/input/event5
- generate events, look for patterns
In my experience (with both mice and gamepads) a single button click or tick should normally produce 48 bytes; 24 for the press and 24 for the release. (3 lines of hexdump output) I don’t know if this is a set structure for the HID/event driver or not, but it’s what I’ve always seen. I’d recommend comparing regular button clicks with individual scroll ticks.
Now whether this helps you solve the issue remains to be seen. But the first thing is to find out where the problem lies…
EDIT: forgot to mention - find the /dev/input/event# device representing your mouse by either combing through Xorg logs (/var/log/Xorg.#.log) or through xinput (void package xinput).