Created attachment 159217 [details] The right screen turns white SUMMARY I connect two monitors to my PC. Recently, after I wake up the monitors from power saving, the right one of them (which is set to non-primary) sometimes goes white and blank. Only mouse cursor is visible. Please see the attachment for picture. When I move the cursor, it still interacts with windows on that screen. I can notice changes of cursor shapes, and even pull windows out from that screen. Turning off+on / Unplugging+Plugging the screen doesn't fix. "killall -9 kwin_wayland" fixes the screen at the cost of losing all windows. STEPS TO REPRODUCE 1. Let the screens sleep. 2. Wake them up. OBSERVED RESULT The right one of the two screens sometimes becomes white. EXPECTED RESULT Both screens are usable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.3-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Graphics: Device-1: NVIDIA TU117 [GeForce GTX 1650] driver: nvidia v: 530.41.03 Device-2: AMD Raphael driver: amdgpu v: kernel Device-3: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1 compositor: kwin_wayland driver: X: loaded: modesetting dri: radeonsi gpu: nvidia,amdgpu resolution: 1: 1920x1080 2: 1920x1080 API: OpenGL v: 4.6 Mesa 23.0.3 renderer: AMD Radeon Graphics (gfx1036 LLVM 15.0.7 DRM 3.52 6.3.3-arch1-1) The two screens are both connected to the integrated AMD GPU. The left one is connected to the DisplayPort, the right one to the HDMI port.
Created attachment 159225 [details] Flickering There is also a chance the screen enter the state where it flickers between white and normal video when I move the cursor on that screen.
Eek
I think it's amdgpu driver's issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2354 I'm trying amdgpu.sg_display=0 kernel parameter mentioned in that thread. The system has been running half a day without issue. Before finding this, I had tried downgrading kwin before and that didn't work. So this is not likely caused by kwin.
Makes sense, I don't know why I didn't remember that. We've gotten tons of reports about it in the recent past. Thanks!