Created attachment 140088 [details] Photo SUMMARY Sometimes second mouse cursor appears on screen center. May be it belongs to screen lock or something about it. But, I'm not sure. Ok, the second cursor doesn't move. It say on top off all. It can't be captured by KDE screenshot program. It disappears after reboot. STEPS TO REPRODUCE 1. Use KDE 2. Give the result OBSERVED RESULT - additional mouse cursor on top of all, on screen center EXPECTED RESULT - no additional frozen cursors on the screen SOFTWARE Operating System: Arch Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.12.15-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 15.5 ГиБ of RAM Graphics Processor: Mesa Intel® HD Graphics 520/OS VERSIONS ADDITIONAL INFORMATION Regular system updates. Also, sometimes a moving cursor becomes black square. I can return it back to normal moving it to Tasks (the bottom panel) and it's ok. May be related. Attached photo: https://pic4a.ru/17/DI_.jpg
Also, switching to waiting mode and back hides the frozen cursor. Seems, it's belongs to screen lock. Cursor just doesn't disappear entering system.
Not sure it's about kwin. I just don't know enough to choose a correct category.
Is anyone here?
Very annoying. Makes KDE useless. Critical.
Same situation on my archlinux KDE Wayland machine. Though I have 'Lock screen automatically' disabled, I also get the second fixed cursor every time after waking my screen up from energy saving.
KWin probably falls back to a software cursor and fails to un-set the hardware cursor. Can you attach ~/.local/share/sddm/wayland-session.log?
Created attachment 141173 [details] ~/.local/share/sddm/wayland-session.log Hello, Zamundaaa. Here you are.
It seems like we're not printing the error messages without debug logging. Could you please enable it with the environment variable QT_LOGGING_RULES="kwin_*.debug=true" (just put that into /etc/environment) and upload the log after the bug happens again?
Created attachment 141206 [details] ~/.local/share/sddm/wayland-session.log with debug logs With debug logs in attachment $ env | grep QT QT_LOGGING_RULES=kwin_*.debug=true QT_QPA_PLATFORMTHEME=qt5ct PLASMA_USE_QT_SCALING=1 QT_WAYLAND_FORCE_DPI=96 QT_AUTO_SCREEN_SCALE_FACTOR=0
I'm affected. I have a laptop with NVidia prime configuration, with both a touchpad and a connected USB mouse, if that's relevant. It happens every time when computer goes to sleep automatically due to inactivity timeout. After resuming, I always have an extra dead cursor permanently displayed. "kwin_wayland --replace" is somewhat a workaround, faster than rebooting, but it still kills the running apps. Any better (less drastic) workaround while it is not fixed?
> Any better (less drastic) workaround while it is not fixed? You can try the environment variable "KWIN_FORCE_SW_CURSOR" to force KWin to never use the hardware cursor. Please report back if that works as I can't reproduce this bug on 5.22.5 or git master.
> You can try the environment variable "KWIN_FORCE_SW_CURSOR" to force KWin to never use the hardware cursor. Please report back if that works With KWIN_FORCE_SW_CURSOR=1 two days works fine. I keep monitoring. > I can't reproduce this bug on 5.22.5 or git master. May be it affects NVidia cards only.
> With KWIN_FORCE_SW_CURSOR=1 two days works fine. I keep monitoring. Hm. No, it doesn't help. I've got one frozen cursor. Seems, auto screen lock with fullscreen video increases the chance of the bug. $ env | grep KWIN_FORCE_SW_CURSOR KWIN_FORCE_SW_CURSOR=1
I think I found the cause of the issue (which can only be observed when using a software cursor, like we always do with NVidia), and I'm pretty sure it's already fixed in 5.23. Feel free to re-open if I'm mistaken
5.23 works fine.