*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.1.0 (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION After an update today, by chance, I shook the mouse strongly towards the sides of my PC screen and the result was that the cursor enlarged until it looked pixelated, unless it was a new function that I found to be of little use in the OS, I have not configured anything different, so I can assume that it is a small bug, nothing serious or to make drama but well, I discovered it by chance and it had never happened to me before, I will add a small video where you can see the cursor bug, thank you .
Thank you for the bug report. This is a new feature in KDE Plasma 6.1, allowing the user to help find the cursor on large screens and if it is required for accessibility reasons. This is documented in the Plasma 6.1 release announcement here: https://kde.org/announcements/plasma/6/6.1.0/ You can configure or disable this feature in System Settings > Accessibility > Shake Cursor.
Created attachment 170706 [details] Cursor Bug I had to compress it since you can't upload more than 4MB of a file anyway.
(In reply to cwo from comment #1) > Thank you for the bug report. This is a new feature in KDE Plasma 6.1, > allowing the user to help find the cursor on large screens and if it is > required for accessibility reasons. This is documented in the Plasma 6.1 > release announcement here: https://kde.org/announcements/plasma/6/6.1.0/ > > You can configure or disable this feature in System Settings > Accessibility > > Shake Cursor. Ahhh haha, thank you, I understand, well, since it appeared like that out of nowhere I thought it was a system bug, thank you and as always, very attentive.