Alright, I hit this bug EIGHT times today and it REALLY pissed me off. Hope you find the root cause and fix this, by the way. All cases were only fixed by a FORCED SHUTDOWN... While on a trip, I wanted to use my laptop to play music while the screen was turned off, so I gone to Battery > set both "When inactive" and "When laptop lid closed" to "Do Nothing", used Elisa to play music, locked the screen and pressed Esc to softly turn off the screen without suspending as always, and boom. The music kept playing, but after a while, when I wanted to use my computer, turns out Plasma decided to stop rendering ABSOLUTELY anything. Black screen, no matter if I switched TTYs or press whatever button (including power), Plasma would not render anything to the screen even though I could change tracks with my Bluetooth's airbuds buttons. Then the logs are flooded with: dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: src QRectF(0,0 2560x1440) -> dst QRect(0,0 2560x1440) dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Failed to create framebuffer: Invalid argument dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Rendering a layer failed! dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Failed to find a working output layer configuration! Enabled layers: dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: src QRectF(0,0 2560x1440) -> dst QRect(0,0 2560x1440) dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Failed to create framebuffer: Invalid argument dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Rendering a layer failed! dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Failed to find a working output layer configuration! Enabled layers: dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: src QRectF(0,0 2560x1440) -> dst QRect(0,0 2560x1440) dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Failed to create framebuffer: Invalid argument dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Rendering a layer failed! dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Failed to find a working output layer configuration! Enabled layers: dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: src QRectF(0,0 2560x1440) -> dst QRect(0,0 2560x1440) STEPS TO REPRODUCE 1. Play music through Elisa 2. Set both "When inactive" and "When laptop lid closed" to "Do Nothing" (preferably on battery, but I also hit this TWICE while being on AC) 3. Lock the screen (Meta + L) 4. Press Esc and watch the render not come back to life OBSERVED RESULT Graphics frost in a black screen even though the system is still "technically working", and the logs flooded with framebuffer fails: dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: src QRectF(0,0 2560x1440) -> dst QRect(0,0 2560x1440) dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Failed to create framebuffer: Invalid argument dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Rendering a layer failed! dic 27 10:48:51 malasdecisiones kwin_wayland[3379]: Failed to find a working output layer configuration! Enabled layers: EXPECTED RESULT A simple innocent screen lock while playing music MUST NOT bring down the entire graphics pipeline 💀 SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.21.0 Qt Version: 6.10.1 ADDITIONAL INFORMATION CPU: Ryzen 9 6900 HX, 16 threads Memory: 16 GiB DDR5 iGPU: AMD Radeon 680M dGPU: RTX 3050 Laptop (Plasma DOES NOT USE THE DGPU to render the desktop at all according to nvtop and nvidia-smi) Laptop model: ASUS Zenbook Pro 17
Created attachment 188026 [details] Failed to create framebuffer!!! Log flood
Can you reproduce this everytime?
Unfortunately, yes. Just letting the first song so it's about to finish is enough to trigger this bug. Actually, you can rule the "Elisa needs to be playing music part" as it can also be triggered after a cold boot while not playing audio and Elisa isn't opened yet. Here are some videos where I reproduced it. Please listen to the voice over so you can get a closer reference on what's happening. https://imgur.com/a/LcYRde8
The invalid argument log lines were also in bug 500038 Looking at the logs, it looks like there are also a ton of systemd coredumps, for example: dic 27 10:41:52 malasdecisiones drkonqi-coredump-launcher[4080]: Unable to find file for pid 93620 expected at "kcrash-metadata/file.fec530af61ab42e9a0423a2182975e28.93620.ini" dic 27 10:41:52 malasdecisiones systemd[1957]: Started Launch DrKonqi for a systemd-coredump crash (PID 2352/UID 1000). dic 27 10:41:52 malasdecisiones systemd[1957]: Started Launch DrKonqi for a systemd-coredump crash (PID 2352/UID 1000). dic 27 10:41:52 malasdecisiones systemd[1957]: Started Launch DrKonqi for a systemd-coredump crash (PID 2352/UID 1000). dic 27 10:41:52 malasdecisiones drkonqi-coredump-launcher[4082]: Unable to find file for pid 93341 expected at "kcrash-metadata/file.fec530af61ab42e9a0423a2182975e28.93341.ini" dic 27 10:41:52 malasdecisiones drkonqi-coredump-launcher[4083]: Unable to find file for pid 93360 expected at "kcrash-metadata/file.fec530af61ab42e9a0423a2182975e28.93360.ini" ... dic 27 10:41:52 malasdecisiones drkonqi-coredump-launcher[4093]: Unable to find file for pid 93560 expected at "kcrash-metadata/file.fec530af61ab42e9a0423a2182975e28.93560.ini" dic 27 10:41:54 malasdecisiones systemd[1957]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection. dic 27 10:41:54 malasdecisiones systemd[1957]: drkonqi-coredump-launcher.socket: Too many incoming connections (16), dropping connection. ... This also seems related dic 27 10:42:27 malasdecisiones plasma_waitforname[3616]: WaitForName: Service was not registered within timeout dic 27 10:42:27 malasdecisiones systemd[1957]: dbus-:1.1-org.kde.KSplash@1.service: Main process exited, code=exited, status=1/FAILURE dic 27 10:42:27 malasdecisiones systemd[1957]: dbus-:1.1-org.kde.KSplash@1.service: Failed with result 'exit-code'. dic 27 10:44:27 malasdecisiones kscreenlocker_greet[3897]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/MediaControls.qml:31:13: QML Image: Blocked request. dic 27 10:44:28 malasdecisiones kscreenlocker_greet[3897]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/MediaControls.qml:31:13: QML Image: Blocked request. dic 27 10:44:29 malasdecisiones kscreenlocker_greet[3897]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/MediaControls.qml:31:13: QML Image: Blocked request. dic 27 10:44:30 malasdecisiones kscreenlocker_greet[3897]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/MediaControls.qml:31:13: QML Image: Blocked request. dic 27 10:44:32 malasdecisiones kscreenlocker_greet[3897]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/MediaControls.qml:31:13: QML Image: Blocked request. dic 27 10:44:34 malasdecisiones kscreenlocker_greet[3897]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/MediaControls.qml:31:13: QML Image: Blocked request. dic 27 10:44:36 malasdecisiones kscreenlocker_greet[3897]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/MediaControls.qml:31:13: QML Image: Blocked request. ... dic 27 10:45:49 malasdecisiones kwin_wayland[3379]: drmPrimeFDToHandle() failed dic 27 10:45:49 malasdecisiones kwin_wayland[3379]: Failed to create framebuffer: Invalid argument dic 27 10:45:49 malasdecisiones kwin_wayland[3379]: Rendering a layer failed! dic 27 10:45:49 malasdecisiones kwin_wayland[3379]: Failed to find a working output layer configuration! Enabled layers: dic 27 10:45:49 malasdecisiones kwin_wayland[3379]: src QRectF(0,0 2560x1440) -> dst QRect(0,0 2560x1440) dic 27 10:45:49 malasdecisiones kwin_wayland[3379]: src QRectF(0,0 256x256) -> dst QRect(595,1439 256x256) dic 27 10:45:50 malasdecisiones kwin_wayland[3379]: drmPrimeFDToHandle() failed