This started happening before 5.11 and so I've been using another os in the meantime. I realize it could be something else but I don't know where to start debugging this. I'm not using wayland. On my desktop the GPU is GTX980 with 384 proprietary drivers. My laptop is Intel HD 5500 drivers. It seems to happen when an OpenGL context is started or destroyed. When it happens the task bar becomes darker (I think when toggling the compositor the task bar goes dark like this for a frame and then back to normal) When the rendering is frozen I can still input text, drag windows around, etc. I can tell because the cursor changes depending on where I put it, and I've also written in a chat while everything was frozen and pressing enter sent the message and all that. Here's a short youtube video of when it's frozen. (not very important, my description should be enough) https://www.youtube.com/watch?v=LY2VdGgo6b4
please provide output of: qdbus org.kde.KWin /KWin supportInformation super awesome would be if you can get it from the "frozen" state (e.g. ssh in). But also from running state could help me.
*** Bug 385324 has been marked as a duplicate of this bug. ***
Created attachment 108157 [details] non frozen state I've attached the non frozen output to this comment. I'll try to post the output when it's frozen as soon as it happens. (also I meant to say I have a gtx 970 not a gtx 980)
Just for the record: I started into X11 yesterday and tried to reproduce by toggling compositing. I was not able to reproduce the problem.
It doesn't always happen but it can happen when you manually toggle the compositor. Most of the times it happens when I launch or exit games, but these games never turned off the compositor in my experience. The only application I have that turned off the compositor was my own opengl application. But recently that stopped turning it off for some reason. I'm not sure how plasma decides when to turn off the compositor, but this is irrelevant. As I was writing this comment I toggled the compositor multiple times and everything froze, but the output from the command I was told to run was nothing. It might have been my mistake so I'll try again. (I have Yakuake with "qdbus org.kde.KWin /KWin supportInformation > frozen.txt" written in it so when it happens I can press f12 and enter.)
Created attachment 108274 [details] qdbus log I made a tmux session on tty7 (main) and when it froze I attached to it from tty1. From the tmux session I added sleep 5 to the beginning of the command, switched to tt7 again which was semi-frozen and waited for output.
So from output: compositing is clearly not active. I fear this is a bug in a different stack. When compositing is not active the X server is responsible for rendering. That seems to not work any more.
Do you get a NVRM message in dmesg when this happens?
[ 561.969560] NVRM: GPU at PCI:0000:01:00: GPU-993ef86b-cac0-cdc9-2118-c2e8e45ee121 [ 561.969563] NVRM: Xid (PCI:0000:01:00): 31, Ch 00000020, engmask 00000101, intr 10000000
Please have a look at the bug 385324, I added a description of the NVRM error and also a workaround that worked for me. Maybe you can confirm.
I'll try the workaround. I mentioned that this happens to my laptop as well but so far I've only been testing this on my desktop. It's kinda time consuming as sometimes it doesn't happen for a whole day and sometimes it happens right after reboot. I'll try to use my laptop as well and post the qdbus and dmesg output when it happens.
I have the same issue on AMD threadripper platform with GTX1080Ti card and also a Dell XPS 8910 desktop with NVIDIA 1070 card. Just wonder to know is this the error caused by driver or the application which invoke some opengl functions?
For me this happens whenever I create a new document in Krita (Uses Opengl) My card is nvidia gtx 750ti
To better reflect the cause of the bug, I think the summary should be changed to something like this: "Nvidia (Xid 31): applications cause graphics reset" I'm experiencing the same thing with kwin 5.12.4 and Nvidia driver 390.48. I can reliably reproduce this bug by just starting the following applications a couple of times: * VSCode (https://code.visualstudio.com) * Shotcut (https://shotcut.org) I think this is a bug in kwin, because I tested this also under GNOME and there I see no crashes/resets (same base system: Ubuntu 18.04).
I had forgotten about this issue. I'm currently only using my laptop and KDE Neon as I've chucked away my main computer. It doesn't seem to happen anymore the way I described it. Maybe it never happened on my laptop in the first place. But I've noticed that sometimes kwin crashes when launching an OpenGL application but that's for another issue I guess.
It seems like version 390.67 contains a fix: http://www.nvidia.com/download/driverResults.aspx/134859/en-us "Fixed a bug that caused kwin OpenGL compositing to crash when launching certain OpenGL applications."
User reported issue fixed.