SUMMARY One or two times per day, when I not use my notebook for some time (5-10 minutes) entire desktop UI become unresposible (only mouse moving is works). Killing plasma from tty (tty switching is still works) just set screen to black, but hotkeys is still not working. SO I have to restart sddm or reboot to be able to continue working. Maybe, this is something related to proprietary nvidia drivers, but with previous Neon releases such error was not exists. STEPS TO REPRODUCE 1. Appeared randomly when system is idle for a short time such as 5-10 minutes 2. After freezing, only mouse moving and not keycodes, which is not related to X11 is working OBSERVED RESULT System's UI is not resposible EXPECTED RESULT Normal working SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.19 User edition, plasma 5.19.5 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Nvidia driver version: 450.66 This bug is reproduces both in my home and work computers (all of them uses nvidia driver, but with different versions)
Does it still happen if you temporarily uninstall the proprietary NVIDIA driver and switch to the FOSS Nouveau driver?
Maybe I can test this later, but for now I need Nvidia driver for my everyday tasks (working with Unity game engine)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Seems to be fixed after upgrade to 5.20 version
Thanks for the update; changing status.