You are not logged in.

#1 2025-03-01 14:00:47

TieMajor
Member
Registered: 2022-02-04
Posts: 28

[SOLVED] KDE Wayland is broken after update (Nvidia GPU)

A recent update seems to have broken KDE Wayland on Nvidia GPU.

Right now with Plasma at `6.3.2-1` with kwin at `6.3.2.1-1`, Nvidia at `570.124.04-1` and kernel `6.13.5.arch1-1`,
starting Plasma Wayland gives a black screen and errors related to `gl_framebuffer_incomplete_attachment`.

Note that X11 still works correctly.

I can provide specific logs or troubleshooting if needed.

Last edited by TieMajor (2025-03-05 15:13:42)

Offline

#2 2025-03-01 14:15:08

TieMajor
Member
Registered: 2022-02-04
Posts: 28

Re: [SOLVED] KDE Wayland is broken after update (Nvidia GPU)

Excerpt of the errors generated by kwin under wayland

Mar 01 22:01:09 arch-desktop kwin_wayland[13261]: No backend specified, automatically choosing drm
Mar 01 22:01:09 arch-desktop baloo_file[13260]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkRequested(QString)
Mar 01 22:01:09 arch-desktop baloo_file[13260]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkDone(Solid::ErrorType, QVariant, QString)
Mar 01 22:01:09 arch-desktop baloo_file[13260]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkRequested(QString)
Mar 01 22:01:09 arch-desktop baloo_file[13260]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkDone(Solid::ErrorType, QVariant, QString)
Mar 01 22:01:09 arch-desktop wireplumber[2064]: spa.bluez5: BlueZ system service is not available
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_core: Applying output config failed!
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:10 arch-desktop systemd[1898]: Created slice Slice /app/dbus-:1.2-org.fcitx.Fcitx5.
Mar 01 22:01:10 arch-desktop systemd[1898]: Started dbus-:1.2-org.fcitx.Fcitx5@0.service.
Mar 01 22:01:10 arch-desktop fcitx5[13327]: I2025-03-01 22:01:10.646426 instance.cpp:1394] Override Enabled Addons: {}
Mar 01 22:01:10 arch-desktop fcitx5[13327]: I2025-03-01 22:01:10.646455 instance.cpp:1395] Override Disabled Addons: {}
Mar 01 22:01:10 arch-desktop fcitx5[13327]: I2025-03-01 22:01:10.648281 addonmanager.cpp:205] Loaded addon wayland
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_core: Applying output config failed!
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:10 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_core: Applying output config failed!
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_core: Applying output config failed!
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:11 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kwin_core: Applying output config failed!
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kf.svg: The theme "Sweet" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kf.svg: The theme "Sweet" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kf.plasma.core: The theme "Sweet" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Mar 01 22:01:12 arch-desktop kwin_wayland[13261]: kf.plasma.core: The theme "Sweet" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Mar 01 22:01:12 arch-desktop kcminit_startup[13265]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
Mar 01 22:01:12 arch-desktop kcminit_startup[13265]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13353]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13353]: > Warning:          Could not resolve keysym XF86RefreshRateToggle
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13353]: > Warning:          Could not resolve keysym XF86Accessibility
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13353]: > Warning:          Could not resolve keysym XF86DoNotDisturb
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13353]: Errors from xkbcomp are not fatal to the X server
Mar 01 22:01:12 arch-desktop systemd[1898]: Starting Accessibility services bus...
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13361]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13361]: > Warning:          Unsupported maximum keycode 708, clipping.
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13361]: >                   X11 cannot support keycodes above 255.
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13361]: > Warning:          Could not resolve keysym XF86RefreshRateToggle
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13361]: > Warning:          Could not resolve keysym XF86Accessibility
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13361]: > Warning:          Could not resolve keysym XF86DoNotDisturb
Mar 01 22:01:12 arch-desktop kwin_wayland_wrapper[13361]: Errors from xkbcomp are not fatal to the X server

Offline

#3 2025-03-01 16:23:58

TieMajor
Member
Registered: 2022-02-04
Posts: 28

Re: [SOLVED] KDE Wayland is broken after update (Nvidia GPU)

The issue seems to be linked to the 6.3.2 release of Plasma (more specifically kwin).

https://bugs.kde.org/show_bug.cgi?id=500819

Offline

#4 2025-03-03 00:56:07

Salkay
Member
Registered: 2014-05-22
Posts: 674

Re: [SOLVED] KDE Wayland is broken after update (Nvidia GPU)

Thanks @TieMajor. I'm also hitting this bug. No NVIDIA for me, just integrated Intel. KDE is a pain to downgrade, so I reverted all packages to 2025/02/26. I can confirm that kwin 6.3.1 works for me. Hopefully they fix it soon!

Offline

#5 2025-03-05 00:51:43

Salkay
Member
Registered: 2014-05-22
Posts: 674

Re: [SOLVED] KDE Wayland is broken after update (Nvidia GPU)

This has been patched by the Arch maintainer (thanks Antonio Rojas!). I can confirm that 6.3.2.1-4 fixes the problem for me!

Offline

#6 2025-03-05 15:13:11

TieMajor
Member
Registered: 2022-02-04
Posts: 28

Re: [SOLVED] KDE Wayland is broken after update (Nvidia GPU)

@Salkay thanks. I was about to post the news as well x). Marking as solved.

Offline

Board footer

Powered by FluxBB