[kde] [Bug 498280] New: KDE suddenly become laggy
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Sun Jan 5 14:23:59 GMT 2025
https://bugs.kde.org/show_bug.cgi?id=498280
Bug ID: 498280
Summary: KDE suddenly become laggy
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: jackyzy823 at gmail.com
Target Milestone: ---
Created attachment 177126
--> https://bugs.kde.org/attachment.cgi?id=177126&action=edit
redacted-journal-log.txt
SUMMARY
I'm not sure what happened. But suddenly the mouse / touchpad 's move speed is
far slower than normal. The keyboard's input speed is slow too.
However the audio output is at normal speed. The CPU/Memory usage is normal in
the System Monitor.
I tried to unplug and plug the receiver of the mouse. it doesn't help
I tried `kwin_wayland --replace` and it doesn't help.
I tried `systemctl restart sddm` and then re-login . it doesn't help.
Only reboot solves the problem.
This is the second time i encountered this issue.
OBSERVED RESULT
Random laggy
EXPECTED RESULT
No random laggy
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 40
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.7.2
ADDITIONAL INFORMATION
The log around the time when laggy happens , shows
```
Jan 05 21:21:53 MACHINE_NAME kwin_wayland[1932]: kwin_libinput: Libinput:
event14 - PNP0C50:00 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
Jan 05 21:23:52 MACHINE_NAME kwin_wayland[1932]: kwin_libinput: Libinput:
client bug: timer event14 keyboard: scheduled expiry is in the past (-70ms),
your system is too slow
Jan 05 21:24:07 MACHINE_NAME kwin_wayland_wrapper[2032]: Key repeat discarded,
Wayland compositor doesn't seem to be processing events fast enough!
```
I guess this might be related to libinput.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list