Kwin crashing frequently

Help
,
1

In the past few months, I’ve experienced that only my main screen would freeze up, usually while using a browser (doesn’t seem to matter which one). I could still move windows from my main screen onto one of my other screens but the freeze would only be “fixable” by rebooting or turning off my main screen which would lead to kwin crashing completely and restarting as a result, closing all currently running applications in the process.
Now, this was already very annoying, especially during meetings.
However, now it has gotten even worse. When this happens now and I turn off my main screen, the other screens go black too and I can only see my cursor. This has only been fixable using a reboot.

Here are my logs from the last time this happened.

Is this known and is there a fix for it?

2

Hi! To help folks best guide you, could you please provide your basic system information from the Info Center app? The Copy Details button is the easiest way to get that ready to paste in:

Screenshot_20250121_011438
Screenshot_20250121_0114381022×274 34.9 KB

Also, based on the messages in those logs:

Mar 09 21:19:31 archlinux kwin_wayland[936]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
Mar 09 21:19:31 archlinux kwin_wayland[936]: kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux

Have you reported this to NVIDIA?

3

Hi, of course. Here’s the information from the Info Center app:

Operating System: Arch Linux 
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.3-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER

I have not yet reported it to NVIDIA but will now, thanks.

4

Sounds good - I’d suspect a graphics driver issue, but in the meantime, it might also make sense to try using a standard Linux kernel (as opposed to the zen one) to see if it helps, and running a system update just to double-check? Arch started providing Plasma 6.3.2 back at the end of February, so if you haven’t updated since then, it’s possible some components impacting that issue might have been updated as well :slight_smile: