SUMMARY When I set my 4k screen to 120Hz, the system stops responding to keyboard/mouse and all screens are frozen. I cannot do Ctrl+Alt+F2 to switch to another VT. However I can be monitoring journalctl over ssh while this happens and there is no crash or error messages indicated, but it will not respond to initiate a new ssh connection. With that active ssh connection, if I try to kill kwin_wayland it will block and not respond. This is with an Nvidia RTX2080. If I swap that out for a Radeon RX6600, there are no issues. Also I found that if I use kscreen-doctor and set the mode of all screens at once, it works fine only until I try to log out or change any screen mode again, where it will hang with the same behaviour as described above. Frustratingly there is no segfault or crash data due to how it locks up. STEPS TO REPRODUCE 1. Install RTX2080 as the only graphics card 2. start plasma wayland session 3. for the 4k screen, set it's refresh rate to 120Hz OBSERVED RESULT - system stops responding to keyboard/mouse and all screens are frozen - `journalctl -f ` from an existing ssh connection doesn't show any errors - trying to kill kwin_wayland over this ssh connection hangs - cannot initiate new ssh connection - If using kscreen-doctor instead of system settings gui, can succeed at setting the screen to 120Hz, but then the system will lock up in a similar way if you try to a) log out, b) change a screen mode again. EXPECTED RESULT system doesn't hang SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.6.57-1-lts (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Core™ i9-9900K CPU @ 3.60GHz Memory: 62.7 GiB of RAM ADDITIONAL INFORMATION Maybe I can try attaching gdb to kwin_wayland over ssh before the lockup happens. Let me know if you have any ideas.
> I can be monitoring journalctl over ssh while this happens and there is no crash or error messages indicated, but it will not respond to initiate a new ssh connection Then this is a kernel problem, not something we can fix. Most likely it's in the driver; to check that, please attach the output of > sudo dmesg if that still works after triggering the hang, or > journalctl -k --boot -1 after power cycling the PC if it doesn't.
Interestingly... I'm having a very similar issue where after the update to 6.2.2 I can no longer use Wayland. NVIDIA RTX 3060. R7 5800X. 64GB of ram. Keyboard doesn't function. kwin is the only thing that starts. Mouse rarely moves. Journal does not log. Kernel 'magic' syskeys still function. The last log in the journal was me switching to the TTY and it being initiated. There is no log of the command being sent. I'm not sure if its the exact same bug but I'm willing to bet that it's a similar one. If you think the issue is the same issue or a relevant one I can attach my log.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.