https://bugs.kde.org/show_bug.cgi?id=443341
--- Comment #6 from nyanpasu64 <nyanpas...@tuta.io> --- I'm on Plasma 5.23.1 now, on nvidia-dkms 470.74-1. When I sleep and resume with compositing off (which corrupts VRAM because lol nvidia http://download.nvidia.com/XFree86/Linux-x86_64/470.74/README/powermanagement.html), I cannot enable compositing anymore. If I run kwin_x11 in a terminal, I get the following output (but no display hang) when attempting to enable compositing after sleep-wake: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 470.74 OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 470.74 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.20.13 Linux kernel version: 5.14.14 Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no libkwinglutils: GL error: context lost kwin_scene_opengl: OpenGL 2 compositing setup failed kwin_scene_opengl: OpenGL driver recommends QPainter based compositing. Falling back to QPainter. kwin_scene_opengl: To overwrite the detection use the environment variable KWIN_COMPOSE kwin_scene_opengl: For more information see https://community.kde.org/KWin/Environment_Variables#KWIN_COMPOSE kwin_core: Failed to initialize compositing, compositing disabled qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5156, resource id: 671, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 5157, resource id: 671, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5163, resource id: 65011714, major code: 18 (ChangeProperty), minor code: 0 Oddly it mentions "OpenGL 2 compositing setup failed" regardless if I'm in OpenGL 2.0 or 3.1 mode. If I kill and restart kwin_x11, I *can* enable compositing. If I enable compositing then sleep/wake, compositing seems to continue working properly, and I can then disable and reenable compositing *after* sleep-wake. I haven't reproduced the flickering so far in my limited testing, so I'm not sure if it can still happen. -- You are receiving this mail because: You are watching all bug changes.