Summary: | libinput ignores xinput settings regarding mouse wheel (quick fix included) | ||
---|---|---|---|
Product: | Wayland | Reporter: | Stefan B <sblachmann> |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED NOTOURBUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | peter.hutterer, sblachmann |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Stefan B
2018-03-31 00:38:33 UTC
libinput doesn't do button mapping, that's handled in the X server. Likewise with the scroll axis to button emulation. This "fix" here is like hacking glibc because you don't want to resolve a specific hostname - less than ideal and, despite your eye-roll in the debian user forum comment, this is not a bug in libinput.
The fix would have to be in the server, specifically in emulate_scroll_button_events() which doesn't appear to take the button mapping into account.
The main question here though is: why do you need to disable the mouse wheel? Apparently:
> The problem is that the cat hairs in the mice make them "scroll" even without
> touching the wheel - highly annoying!
So yeah, nah. Not going to hack libinput for this. Feel free to open a bug against the X server when you've verified that button mapping isn't taking into account for scroll button emulation, but don't expect anyone to have the time to fix this right now. I suggest to get a new mouse, because the amount of effort required on our side to keep your cat hairs off your wheel is disproportional to the money a new mouse costs.
|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.