https://bugs.kde.org/show_bug.cgi?id=494108
--- Comment #4 from Michał Dybczak <michal.dybc...@gmail.com> ---
I'm staring to believe that this bug has nothing to do with framebuffer status.
In only happens that sometimes this bug is there, but the fact that it's never
timely matched with the stuttering effect or that in last two bug events there
was no such frambuffer error in journald. In fact, there is no error that would
match the issue. In last journald, I had plenty of libinput bugs, and they even
end when the stuttering starts, but there is no other error at that time.
Here is some fragment of the last jounrald log:
paź 08 15:52:29 Sirius16-Manjaro kwin_wayland[1754]: kwin_libinput: Libinput:
event19 - PNP0C50:0b 0911:5288 Touchpad: kernel bug: Touch jump detected and
discarded.
See
https://wayland.freedesktop.org/libinput/doc/1.26.2/touchpad-jumping-cursors.html
for details
paź 08 15:52:29 Sirius16-Manjaro kwin_wayland[1754]: kwin_libinput: Libinput:
event19 - PNP0C50:0b 0911:5288 Touchpad: WARNING: log rate limit exceeded (5
msgs per 24h). Discarding future messages.
paź 08 16:15:40 Sirius16-Manjaro kwin_wayland[1754]: kwin_libinput: Libinput:
event19 - PNP0C50:0b 0911:5288 Touchpad: client bug: event processing lagging
behind by 21ms, your system is too slow
paź 08 20:10:02 Sirius16-Manjaro kwin_wayland[1754]: kwin_libinput: Libinput:
event19 - PNP0C50:0b 0911:5288 Touchpad: client bug: event processing lagging
behind by 30ms, your system is too slow
paź 08 20:17:02 Sirius16-Manjaro kwin_wayland[1754]: kwin_libinput: Libinput:
event19 - PNP0C50:0b 0911:5288 Touchpad: libinput bug: invalid gesture event
GESTURE_EVENT_HOLD_TIMEOUT in state GESTURE_STATE_HOLD
paź 08 20:42:15 Sirius16-Manjaro kwin_wayland[1754]: kwin_libinput: Libinput:
client bug: timer event19 hold: scheduled expiry is in the past (-73ms), your
system is too slow
Exactly and 20:42 the display stuttering happened. I did nothing usual, was
watching some video, and it happened in the middle of it. Other time I was just
browsing files in Dolphin when it happened. So there is no distinctive trigger,
and it lately happens daily, in the evening, which is weird.
So how to debug it in another way, if the bug is not written in journald?
--
You are receiving this mail because:
You are watching all bug changes.
