I wanted to run this past the forums first because I’m not sure if it’s worthy of a bug report, I’m quite new to Linux (I’ve dabbled over the years but nothing really serious) so I’m not particularly experienced in getting debug information.
I’m running an update to date version of OpenSUSE Tumbleweed on a Desktop PC running a 7950X3D CPU and an RTX4090 GPU, I have the latest NV drivers installed (G06 Open) and I’m running KDE Plasma 6.3.5 (Frameworks 6.14.0) in Wayland.
Wayland runs great, however whenever I enable the 4th monitor in my config (Which is an Onkyo NR7100 AV Receiver connected to an LG C1 in another room) I get a hard crash where my display (including the mouse cursor) completely freezes.
This persists with a reboot, as soon as I log into SDDM (which I believe is running under X11 so works fine) my monitors instantly lose signal.
The only thing I can do from there is either a) Login under X or b) delete ~/.config/kwinoutputsettings.json and reboot.
The desktop works fine if I only have 3 monitors enabled, it’s just as soon as I enable the AV Reciever (connected via a known good HDMI 2.1 cable). I believe I can get it running if I disable the 3 monitors connected to my PC.
There’s not much info to gather because it’s a hard crash but I see this constantly spamming in the last boot of journalctl:
May 29 21:08:23 localhost.localdomain kwin_wayland[5282]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. and are incompatible
May 29 21:08:23 localhost.localdomain kwin_wayland[5282]: kwin_scene_opengl: Invalid framebuffer status: “GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT”
This seems to repeat for every frame until I reboot the machine.
Does anyone have any ideas? I know there’s a Plasma 6.4 beta but I’m not too sure if it’s possible for me to install and see if it’s fixed there.
Just to add, I can reproduce this no matter what the fourth monitor is, I tried it with two PC monitors and the AV receiver and when I enabled the third PC monitor I got the same result.
coredumpctl gdb -1 kwin_wayland can give you a nice stack trace to diagnose this.
This will require to download a bunch of stuff, here “Enter” until you see (gdb)
Type bt then enter and share the last output.
Then Ctrl+D to exit.
I guess this means there’s no crash dump? I don’t think it actually crashes unfortunately, it’ll spam the log with the GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT forever until I reboot. If I’m in a Wayland session, the screen will freeze though.
Thanks! I saw that, there’s nothing relevant crashing unfortunately, when my machine freezes it looks like it just spams the logs indefinitely until I restart. Audio still plays in the background.
I bound a shortcut to plasmashell —replace and nothing happens, REISUB works fine though.
I tried a clean install of openSUSE tumbleweed and it worked fine on Nouveau and an older Kernel, but as soon as I updated with zypper dup I got the same issue on boot and a bunch of other problems even running zypper dup. I will try Fedora 42 and see if I have the same issue, but without any crash dumps I’m a bit stuck, should I open a bug report?
OpenSUSE was having some mirror issues, so I’ve only been able to test recently, but I clean reinstalled. Worked fine until I installed NVIDIA drivers and now I get the hang every time I login to Wayland. X is unaffected.
Is there anything I can do further to help diagnose this?
Report the bug at Log in to KDE Bugtracking System with detailed information about software and hardware as well as steps to reproduce, and the KWin developers will reach out if they need further information.