OS: CachyOS
Kernel: 6.19.7-1
DE: KDE Plasma 6.6.2
CPU: i7-10700K
GPU: Nvidia 4080 Super
A couple days ago, I did my normal update as I was logging off for the night. I came back last night to play some games and after logging in my computer appears to hard lock up. I tried to Alt+F3 to get into a TTY console but even that wasn’t working. I hold the power button and restart the machine and confirm that this is a consistent issue. After another restart I get the login screen and get the TTY console from there and I started poking around.
From what me and a friend could find out there was something that was updated recently that isn’t playing well with a couple different versions of the nvidia drivers. We learned that my machine wasn’t actually hard locking up because I could still SSH into it and the machine was responding as expected just no display output at all. I removed what I could for the drivers from my system and was able to reboot and log-in to my machine and get to the DE without issue without any drivers.
Before calling it a night I reinstalled the Nvidia open drivers with pacman, rebooted and logged in. Then I SSH’ed in with my other machine and extracted a journalctl log for that boot.
I just confirmed that this is a wayland issue, using the TTY console I installed the X11 filesets and was able to use my DE again.
Mar 15 23:06:53 LIN-TARDIS kwin_wayland[1122]: No backend specified, automatically choosing drm
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Atomic modeset test failed! Invalid argument
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Atomic modeset test failed! Invalid argument
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Atomic modeset test failed! Invalid argument
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Atomic modeset test failed! Invalid argument
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Atomic modeset test failed! Invalid argument
[...]
Mar 15 23:06:54 LIN-TARDIS rtkit-daemon[966]: Successfully made thread 1194 of process 1194 owned by '1000' high priority at nice level -11.
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 15 23:06:54 LIN-TARDIS rtkit-daemon[966]: Successfully made thread 1201 of process 1194 owned by '1000' RT at priority 20.
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 15 23:06:54 LIN-TARDIS rtkit-daemon[966]: Successfully made thread 1195 of process 1195 owned by '1000' high priority at nice level -11.
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 15 23:06:54 LIN-TARDIS rtkit-daemon[966]: Successfully made thread 1212 of process 1195 owned by '1000' RT at priority 20.
[...]
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 15 23:06:54 LIN-TARDIS kwin_wayland[1122]: Applying output configuration failed!