| Summary: | Mouse scrolling ignores every n-th step of scroll wheel on lower scroll speed settings | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Patrik <idvert3x> |
| Component: | input | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | nate, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.11 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Patrik
2024-05-31 09:57:47 UTC
Using libinput debug-events, I'm able to see that mouse wheel steps are being received: -event13 POINTER_SCROLL_WHEEL +3.259s vert -15.00/-120.0* horiz 0.00/0.0 (wheel) event13 POINTER_SCROLL_WHEEL +3.934s vert -15.00/-120.0* horiz 0.00/0.0 (wheel) event13 POINTER_SCROLL_WHEEL +4.622s vert -15.00/-120.0* horiz 0.00/0.0 (wheel) event13 POINTER_SCROLL_WHEEL +5.279s vert -15.00/-120.0* horiz 0.00/0.0 (wheel) event13 POINTER_SCROLL_WHEEL +6.006s vert -15.00/-120.0* horiz 0.00/0.0 (wheel) event13 POINTER_SCROLL_WHEEL +6.663s vert -15.00/-120.0* horiz 0.00/0.0 (wheel) event13 POINTER_SCROLL_WHEEL +7.303s vert -15.00/-120.0* horiz 0.00/0.0 (wheel) event13 POINTER_SCROLL_WHEEL +7.953s vert -15.00/-120.0* horiz 0.00/0.0 (wheel) event13 POINTER_SCROLL_WHEEL +8.541s vert -15.00/-120.0* horiz 0.00/0.0 (wheel) event13 POINTER_SCROLL_WHEEL +9.175s vert -15.00/-120.0* horiz 0.00/0.0 (wheel) But when using wev, only every 2nd one causes an actual scroll to occur: [13: wl_pointer] axis_source: 0 (wheel) [13: wl_pointer] axis_stop: axis: 0 (vertical), discrete: -1 [13: wl_pointer] axis: time: 901017; axis: 0 (vertical), value: -7.000000 [13: wl_pointer] frame [13: wl_pointer] frame [13: wl_pointer] axis_source: 0 (wheel) [13: wl_pointer] axis_stop: axis: 0 (vertical), discrete: -1 [13: wl_pointer] axis: time: 902380; axis: 0 (vertical), value: -15.000000 [13: wl_pointer] frame [13: wl_pointer] frame [13: wl_pointer] axis_source: 0 (wheel) [13: wl_pointer] axis_stop: axis: 0 (vertical), discrete: -1 [13: wl_pointer] axis: time: 903764; axis: 0 (vertical), value: -15.000000 [13: wl_pointer] frame [13: wl_pointer] frame [13: wl_pointer] axis_source: 0 (wheel) [13: wl_pointer] axis_stop: axis: 0 (vertical), discrete: -1 [13: wl_pointer] axis: time: 905061; axis: 0 (vertical), value: -15.000000 [13: wl_pointer] frame [13: wl_pointer] frame [13: wl_pointer] axis_source: 0 (wheel) [13: wl_pointer] axis_stop: axis: 0 (vertical), discrete: -1 [13: wl_pointer] axis: time: 906299; axis: 0 (vertical), value: -15.000000 [13: wl_pointer] frame [13: wl_pointer] frame *** This bug has been marked as a duplicate of bug 484309 *** @Nate Graham: I noticed you marked the issue as duplicate, but the referenced issue seems to describe a different problem in a different context. In my case, all programs running under KDE Wayland are affected (all Qt and GTK apps, not just Kirigami apps), and scroll steps are being ignored, instead of some issue with animations mentioned in issue 484309. Was this issue marked as duplicate due to the root cause (underlying technical problem) being the same, or could it be a mistake? Hmm, if GTK apps are affected too, indeed it would be a different issue. In fact I wonder if that bug is actually caused by this one... From the logs I managed to collect (included in a comment above), it seems that Wayland server isn't correctly passing scroll events (visible in libinput's debug output) to wayland clients (wev debug tool in this case). I did some searching, and I found at least one other person experiencing this problem: https://discussion.fedoraproject.org/t/scroll-issue-skipping-steps/112622 This is intentional-ish, caused by https://invent.kde.org/plasma/kwin/-/merge_requests/3900. *** This bug has been marked as a duplicate of bug 470746 *** |