BUG: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"

Graphics / Linux Linux
1

I have sort of hoped that someone else would have reported this by now.

This bug happens only on laptops with dual GPUs installed, and which have a high resolution high refresh rate and optionally HDR attached, and only when running Wayland as a compositor on the iGPU.

On my specific system, the following text is displayed in the journal at irregular intervals:
```
Mar 11 07:14:36 Evert.Scar kwin_wayland[2020]: 0x500: GL_INVALID_ENUM error generated. Invalid .
Mar 11 07:14:36 Evert.Scar kwin_wayland[2020]: Invalid framebuffer status: “GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT”
Mar 11 07:14:36 Evert.Scar kwin_wayland[2020]: Failed to create framebuffer: Invalid argument
Mar 11 07:14:36 Evert.Scar kwin_wayland[2020]: Failed to create framebuffer: Invalid argument

```
The system seems stable and performant most of the time. Any instabilities in the system cannot be purely ascribed to this issue, so I am not going to speculate.

A bug report has been raised with KDE:

And with freedesktop:

There is a workaround described in the Arch Linux forums:

But this workaround just has the nVdia GPU do the composing, which defeats the purpose of Optimus graphics.

My hunch is that kwin_wayland is calling something in the nVidia driver in a way that is not properly implemented.

nvidia-bug-report.log.gz (1.6 MB)

2

With the latest nvidia drivers, this problem got way worse.
I get this error on every screen update now, and with a display rate of 144Hz, this makes for some pretty big logs.

My current workaround is to run the system in AsusMuxDgpu mode when the external monitor is plugged in.

Unfortunately suspend is broken in AsusMuxDgpu mode, so I had to turn that off as well.

3

Arch nvidia-open-dkms is now on 595.58.03 and believe it or not, it’s got even worse.

Previously I was able to more or less to ignore them. Now I have to use QT_LOGGING_RULES=kwin_scene_opengl=false.

4

I can confirm this on a similar hybrid AMD+NVIDIA laptop setup.

System:

  • Fedora 43
  • KDE Plasma 6.6.4
  • KWin Wayland
  • NVIDIA driver 580.126.18
  • AMD Radeon 680M iGPU + NVIDIA dGPU (3080)

It is really bad on the Firefox’s renderer/gpu path. It is completely hammered and raises my cpu’s temp to 80c just on the browser

kwin_wayland starts spamming these errors, and
normal browsing or video playback can drive CPU temperatures to around 80C.

The journal shows the same errors:

kwin_wayland: 0x500: GL_INVALID_ENUM error generated. Invalid .
kwin_wayland: Invalid framebuffer status: “GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT”
kwin_wayland: Failed to create framebuffer: Invalid argument
kwin_wayland: Failed to create framebuffer: Invalid argument

From what I can tell, the problem is tied to the hybrid Wayland setup itself, especially when the internal panel is on the AMD iGPU and at
least one external display is active on the NVIDIA GPU.

When I switch from 240hz to 60hz - it helps but it does not fix the problem

5

Just had an update of the Nvidia drivers to 595.71.05, and this issue is still present.

6

System freezes when moving mouse

I ended up here because on my laptop (multi-GPU with NVIDIA GeForce GTX 1660 Ti) with external monitor running Ubuntu 25.10 (nvidia-driver-580.142) and (now) Ubuntu 26.04 (nvidia-driver-595.58) with KDE plasma+Wayland I experienced a complete system freeze when trying to move my mouse from internal laptop display to external monitor. A discussion with an AI did not provide a solution. The link posted above saved my day, because setting ‘KWIN_FORCE_SW_CURSOR=1’ did it for me. Nevertheless AI suggested it being a NVIDIA issue not an KDE issue. Thats why I wanted to add that reply here. Maybe that can be of any help?

For some unknown reason I cannot upload the log of the nvidia-bug-report.sh… Keeps hanging on “processing upload”

PS: I’m not a dev. Sorry for sneeking in ;-)

journal.log.gz (1.8 KB)

7

Thanks for posting this here. I’ll post it with the KDE bug report, and hopefully someone will get to the bottom of why this is happening.
Confirmed that forcing a software cursor fixes the issue on my system too.

8

i have the same problem on fedora 44 KDE

intel+nvidia

i had to disable logging because it was writing to my SSD constantly i only noticed the issue because i noticed my NVME heating to 60 on idle which wasn’t normal

nvidia-bug-report.log.gz (2.0 MB)