Bug 504320

Summary: TrackPoint not working and mouse cursor stuttering after reboot (Wayland, ThinkPad L460)
Product: [Plasma] kwin Reporter: yaroslavfis4
Component: libinputAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: normal CC: nate
Priority: NOR Keywords: regression, wayland-only
Version First Reported In: 6.3.90   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: 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

Description yaroslavfis4 2025-05-16 09:11:39 UTC
Created attachment 181369 [details]
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
Comment 1 Nate Graham 2025-05-16 14:10:22 UTC
Thanks for the journal log; that's helpful.

I don't see any messages from Libinput that the compositor was being too slow and discarding events, which means this is most likely not a KWin issue. I'd recommend you report it at https://gitlab.freedesktop.org/libinput/libinput/-/issues, following the instructions in the template to generate input logs as needed.

Thanks!