(In reply to Wolfgang Bauer from comment #3) > This seems to be the exact same problem as in > https://bugs.kde.org/show_bug.cgi?id=424592, and it's apparently a > bug/regression in the nvidia driver. To quote: Comment 11 David Edmundson 2020-08-21 10:52:29 UTC Created attachment 131075 [details] Test case of the bug at hand Report for the nvidia people: Attached is a test case that creates a context and immediately calls glGetGraphicsResetStatusARB() On boot if I run this as an application I get GL_NO_ERROR and this app will quit and exit. This happens for every time the program is run - as expected. Now with this program *NOT RUNNING* suspend and resume. Every new invocation of the app will print "Graphics reset status! : 37563" This appears to be new with nvidia 450. Subsequent calls appear to be correct, but it still doesn't make sense for us to be told context has been lost when it wasn't lost whilst we were running. Comment 12 Erik Kurzinger 2020-08-25 01:06:20 UTC Dang. Yes, this is indeed a regression in the 450 NVIDIA driver. Thank you for narrowing it down, David. I've identified the root cause and will try to get a fix included in the next minor version.