SUMMARY When scrolling speed is reduced to a value less than the default, mouse wheel movements will generate inconsistent wl_pointer axis events for Wayland clients. This seems to affect scrolling in WezTerm, Qt5/6/GTK3 list views, Firefox (Wayland), and Chromium tab strip. STEPS TO REPRODUCE 1. Reset the "scrolling speed" of the current mouse to its default (5th tick on the slider) 2. Start wev from a terminal, move the wheel while hovering the window, and observe the output. 3. Reduce the scrolling speed 4. Repeat step 2 OBSERVED RESULT When the scrolling speed is at its default value, wl_pointer axis events with the following values can be observed: 15, 15, 15, 15, ... When it is lower than the default, one of the following repeat sequences can be seen (x = empty frame): - x, 22, 11, ... - x, 15, ... - x, x, x, 18, x, x, 13, x, x, 13, ... - x (repeat 9 times), 15, ... EXPECTED RESULT I'm not sure what the expected (correct) outcome should be, but I guess every wheel movement should generate an axis event with the same value. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.5-arch1-1 (64-bit) Graphics Platform: Wayland
Can reproduce on Plasma 5.27 (can't test on 6 right now because the mouse KCM doesn't open); probably it's being rounded down do nothing. We should always ensure that a single scroll tick adjusts the axis by at least 1.
This bug is not caused by rounding errors or wl_pointer axis events. It's caused by axis_discrete & axis_value120 events being handled incorrectly after https://invent.kde.org/plasma/kwin/-/merge_requests/3900
So we're back to the original error state, darn.
*** Bug 471396 has been marked as a duplicate of this bug. ***
*** Bug 462517 has been marked as a duplicate of this bug. ***
*** Bug 487831 has been marked as a duplicate of this bug. ***
*** Bug 489123 has been marked as a duplicate of this bug. ***
*** Bug 488936 has been marked as a duplicate of this bug. ***
*** Bug 500875 has been marked as a duplicate of this bug. ***