Bug 511852

SUMMARY
This seems somewhat similar to https://bugs.kde.org/show_bug.cgi?id=496898, but there does not seem to be any memory leak. 
Kwin is at version 6.5.2, but the picker above did not allow me to pick that version, so I picked the closest one.

After the latest nVidia driver update, to version 580-105, I am seeing the following lines in my journal at regular intervals:
```
Nov 09 09:37:09 Evert.Scar kwin_wayland[1497]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Nov 09 09:37:09 Evert.Scar kwin_wayland[1497]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Nov 09 09:37:09 Evert.Scar kwin_wayland[1497]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Nov 09 09:37:09 Evert.Scar kwin_wayland[1497]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Nov 09 09:37:09 Evert.Scar kwin_wayland[1497]: Failed to create framebuffer: Invalid argument
Nov 09 09:37:09 Evert.Scar kwin_wayland[1497]: Failed to create framebuffer: Invalid argument
```

I'm reporting it here, because it is kwin_wayland that is throwing the error, and the system seems to be running fine. In fact, with the latest nVidia drivers there are a lot of bugs that have simply gone away. 
Specifically this bug was affecting this system the worst: 
https://forums.developer.nvidia.com/t/bug-external-monitor-fails-to-wake-up-from-powersave-mode-if-refresh-rate-is-higher-than-30hz/316612

Again, to be perfectly clear, this error does not seem to be affecting my system in any way. It is rock stable and running fast. However, kwin is reporting an error, and I would like to make you aware of it.

Over the web, it seems that people were having this exact error reported, and that it had gone away by setting nvidia modeset and fbdev to true with kernel parameters. Both these are now set by default with the nVidia drivers without the need for kernel parameters:
```
evert@Evert ~ [1]> sudo cat /sys/module/nvidia_drm/parameters/modeset
Y
evert@Evert ~> sudo cat /sys/module/nvidia_drm/parameters/fbdev 
Y
```

I can only conclude that nVidia is doing something different now, and because it is working so well (for me at least) people are going to be both unwilling to change their drivers, and bombarding you with bug reports. 

STEPS TO REPRODUCE:
Just run your system normally.

OBSERVED RESULT
Errors reported in the journal

EXPECTED RESULT
No errors reported in the journal

SOFTWARE/OS VERSIONS
      /\          evert@Evert
     /  \         -----------
    /    \        OS: Arch Linux x86_64
   /      \       Host: ROG Strix G733PYV_G733PYV (1.0)
  /   ,,   \      Kernel: Linux 6.17.7-3-cachyos
 /   |  |   \     Uptime: 17 mins
/_-''    ''-_\    Packages: 1665 (pacman), 7 (flatpak)
                  Shell: fish 4.1.2
                  Display (NE173QHM-NZ2): 2560x1440 @ 1.33x in 17", 240 Hz [Built-in]
                  Display (BenQ EX3210U): 3840x2160 @ 1.5x in 32", 144 Hz [External] *
                  DE: KDE Plasma 6.5.2
                  WM: KWin (Wayland)
                  WM Theme: Oxygen
                  Theme: Oxygen (Oxygen) [Qt], Breeze [GTK2/3/4]
                  Icons: oxygen [Qt], oxygen [GTK2/3/4]
                  Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
                  Cursor: Oxygen-22-White-Valentine (48px)
                  Terminal: konsole 25.8.3
                  Terminal Font: Hack (12pt)
                  CPU: AMD Ryzen 9 7945HX3D (32) @ 5.46 GHz
                  GPU 1: AMD Radeon 610M [Integrated]
                  GPU 2: NVIDIA GeForce RTX 4090 Laptop GPU [Discrete]
                  Memory: 5.90 GiB / 62.00 GiB (10%)
                  Swap: 0 B / 100.00 GiB (0%)
                  Disk (/): 131.44 GiB / 150.00 GiB (88%) - btrfs
                  Disk (/home): 2.72 TiB / 3.40 TiB (80%) - btrfs
                  Disk (/home/evert/Videos): 2.76 TiB / 3.39 TiB (81%) - btrfs
                  Local IP (enp7s0u2u2c2): 192.168.88.88/24
                  Battery (GA50358): 69% [AC Connected]
                  Locale: en_GB.UTF-8

ADDITIONAL INFORMATION
Full journal for this boot:
http://0x0.st/K9yy.txt

Also worth noting is that while this is an Arch install, I am using CachyOS packages specifically optimized for my laptop.

I did see some screen freezes on the internal panel of the laptop which may or may not be related to this, but this was cured by setting amdgpu.dcdebugmask=0x10.