[kde] [Bug 504320] New: TrackPoint not working and mouse cursor stuttering after reboot (Wayland, ThinkPad L460)
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Fri May 16 10:11:39 BST 2025
https://bugs.kde.org/show_bug.cgi?id=504320
Bug ID: 504320
Summary: TrackPoint not working and mouse cursor stuttering
after reboot (Wayland, ThinkPad L460)
Classification: I don't know
Product: kde
Version First unspecified
Reported In:
Platform: openSUSE
OS: Linux
Status: REPORTED
Keywords: regression, wayland-only
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: yaroslavfis4 at gmail.com
Target Milestone: ---
Created attachment 181369
--> https://bugs.kde.org/attachment.cgi?id=181369&action=edit
Full journal log from the boot where the issue occurred (generated with
`journalctl -b -1`). Contains system messages from the session where the
TrackPoint was not working and the cursor was stutterin
### SUMMARY
After rebooting my ThinkPad L460 following a system update, on the next startup
the mouse cursor was stuttering and moving very slowly, and the red TrackPoint
was completely unresponsive. After one more reboot, everything started working
normally.
### STEPS TO REPRODUCE
1. Install system updates
2. Reboot the system
3. Observe mouse/TrackPoint behavior on next boot
4. Reboot again — issue goes away
### OBSERVED RESULT
- Mouse cursor was jittery and very slow
- TrackPoint (red dot) was not working at all
- After rebooting again, both issues disappeared
### EXPECTED RESULT
- Cursor should move smoothly after any reboot
- TrackPoint should work immediately every time
### SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250508
KDE Plasma Version: 6.3.90
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.0
Kernel Version: 6.14.5-1-default (64-bit)
Graphics Platform: Wayland
### ADDITIONAL INFORMATION
- Laptop: ThinkPad L460 (LENOVO 20FVS20700)
- CPU: Intel® Core™ i3-6100U @ 2.30GHz ×4
- RAM: 8 GiB
- GPU: Intel® HD Graphics 520
- The issue occurred **after rebooting once post-update**, not immediately
after the update
- Input devices may have failed to initialize properly during that boot
- Not reproducible consistently, but could affect others
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list