Yesterday I made a fresh install of Slowroll with KDE-Plasma. I thought everything went OK and could make some configs but today when I log in with Wayland, the desktop freezes after a few seconds and the only way out is a “savage” shutdown.
This problem does not happen with X11 where everything seems to work as expected.
Anyone any idea at what I should look?
To start with please share the graphics hardware, driver, and environment details reported via inxi -SGaz
Also, when you mention the configs you made, were these desktop-related, like themes, panels, or other Plasma settings?
Try forcing software rendering to see if the crash is caused by GPU/driver issues. Open a TTY (Ctrl+Alt+F2) and run:
export KWIN_DRM_NO_MODES=1
export KWIN_OPENGL_INTERFACE=software
startplasma-wayland
Does that result in a usable session?
inxi -SGaz gives this:
System:
Kernel: 6.19.6-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.19.6-1-default
root=UUID=560d7e24-aacd-4c39-9498-fa1172eabc62 splash=silent
resume=/dev/disk/by-uuid/890a425e-9efa-4cdf-ac21-1289c28cde65 quiet
security=apparmor mitigations=auto rd.driver.blacklist=nouveau
Desktop: KDE Plasma v: 6.6.2 tk: Qt v: N/A info: frameworks v: 6.23.0
wm: kwin_x11 tools: avail: xscreensaver vt: 2 dm: SDDM Distro: openSUSE
Tumbleweed-Slowroll 20260302
Graphics:
Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Acer Incorporated ALI
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: eDP-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:9bc4 class-ID: 0300
Device-2: NVIDIA TU106M [GeForce RTX 2070 Mobile / Max-Q Refresh]
vendor: Acer Incorporated ALI driver: nvidia v: 580.142
alternate: nouveau,nvidia_drm non-free: 550-580.xx+ status: current (as
of 2025-11; EOL~2026-12-xx) arch: Turing code: TUxxx process: TSMC 12nm FF
built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s ports: active: none off: HDMI-A-3 empty: DP-4
bus-ID: 01:00.0 chip-ID: 10de:1f14 class-ID: 0300
Device-3: Chicony HD User Facing driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:3 chip-ID: 04f2:b64f
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia unloaded: vesa
alternate: fbdev,intel,nouveau,nv dri: iris
gpu: i915,nvidia,nvidia-nvswitch display-ID: :0 screens: 1
Screen-1: 0 s-res: 4480x1440 s-dpi: 96 s-size: 1185x381mm (46.65x15.00")
s-diag: 1245mm (49.01")
Monitor-1: HDMI-A-3 mapped: HDMI-1-0 note: disabled pos: left
model: Philips PHL27E1N5600A serial: <filter> built: 2023 res:
mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 109 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 640x480
Monitor-2: eDP-1 pos: primary,right model: ChiMei InnoLux 0x175c
built: 2018 res: mode: 1920x1080 hz: 144 scale: 100% (1) dpi: 128 gamma: 1.2
size: 381x214mm (15x8.43") diag: 437mm (17.2") ratio: 16:9
modes: 1920x1080
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia x11: drv: iris inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 26.0.1 glx-v: 1.4
direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
device-ID: 8086:9bc4 memory: 15.09 GiB unified: yes
API: Vulkan v: 1.4.341 layers: 3 device: 0 type: integrated-gpu name: Intel
UHD Graphics (CML GT2) driver: mesa intel v: 26.0.1 device-ID: 8086:9bc4
surfaces: N/A device: 1 type: discrete-gpu name: NVIDIA GeForce RTX 2070
with Max-Q Design driver: nvidia v: 580.142 device-ID: 10de:1f14
surfaces: N/A device: 2 type: cpu name: llvmpipe (LLVM 21.1.8 256 bits)
driver: mesa llvmpipe v: 26.0.1 (LLVM 21.1.8) device-ID: 10005:0000
surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Mod edit: Preformatted text for code output
Trying this
export KWIN_DRM_NO_MODES=1
export KWIN_OPENGL_INTERFACE=software
startplasma-wayland
gives the same result as logging in via sddm: after 2 seconds the screen (and the entire computer) freezes.
The system is a hybrid graphics setup (Intel iGPU + NVIDIA RTX 2070) .
Check
cat /sys/module/nvidia_drm/parameters/modeset and see if it reports “Y”. If it reports “N” then add nvidia_drm.modeset=1 kernel parameter to GRUB, and reboot.
Once the Plasma Wayland ession freezes, are you still able to access a VT?
If so, examining the logs from journalctl -b -1 | grep -Ei "kwin|drm|nvidia" might be useful.
I also happen to note that the NVIDIA card is idle as expected.
Please show the output from
nvidia-smi
switcherooctl list
Hopefully, we can get someone familiar with hybrid graphics to chime in here.
On cat /sys/module/nvidia_drm/parameters/modeset I get a “Y” (which was to be expected as I have no problem with X11 sessions).
When Pasma Wayland freezes I have no access to the virtual terminals. In fact the only thing I can do is
nvidia-smi gives
Sat Mar 14 21:31:57 2026
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.142 Driver Version: 580.142 CUDA Version: 13.0 |
+-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 2070 ... On | 00000000:01:00.0 On | N/A |
| N/A 39C P5 12W / 80W | 115MiB / 8192MiB | 32% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 1541 G /usr/bin/Xorg.bin 97MiB |
+-----------------------------------------------------------------------------------------+
Mod edit: Preformatted text for ouptut.
switcherooctl list gives
Device: 0
Name: Intel® UHD Graphics
Default: yes
Discrete: no
Environment: DRI_PRIME=pci-0000_00_02_0 VK_LOADER_DRIVERS_SELECT=*intel*
Device: 1
Name: NVIDIA Corporation TU106M [GeForce RTX™ 2070 Mobile / Max-Q Refresh]
Default: no
Discrete: yes
Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only VK_LOADER_DRIVERS_SELECT=*nvidia*In this case, you can still check what happened after rebooting back into your working X11 session and examining the previous boot…
journalctl -b -1 | grep -Ei "kwin|wayland|drm|nvidia"
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
mar 14 21:26:39 gwerlas kwin_x11[1971]: The theme "KDE-Story" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 14 21:26:39 gwerlas kwin_x11[1971]: The theme "KDE-Story" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 14 21:26:39 gwerlas kwin_x11[1971]: The theme "KDE-Story" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 14 21:26:45 gwerlas kwin_x11[1971]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kwin'")
mar 14 21:26:45 gwerlas kwin_x11[1971]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kwin'")
mar 14 21:26:56 gwerlas kwin_x11[1971]: QDBusConnection: couldn't handle call to Teardown, no slot matched
mar 14 21:26:56 gwerlas kwin_x11[1971]: QDBusConnection: couldn't handle call to Teardown, no slot matched
mar 14 21:26:56 gwerlas kwin_x11[1971]: Could not find slot Krunner1Adaptor::Teardown
mar 14 21:26:57 gwerlas kinfocenter-vulkan-helper[2584]: Physical device 0: 'NVIDIA GeForce RTX 2070 with Max-Q Design' 580.568.0 (api 1.4.312 vendor 0x10DE device 0x1F14 type 2)
mar 14 21:28:50 gwerlas sudo[4344]: thibaud : TTY=pts/0 ; PWD=/home/thibaud ; USER=root ; COMMAND=/usr/bin/cat /sys/module/nvidia_drm/parameters/modeset
mar 14 21:43:19 gwerlas kwin_x11[1971]: Could not delete render time query because no context is current
mar 14 21:43:19 gwerlas kwin_x11[1971]: Could not delete framebuffer because no context is current
mar 14 21:43:19 gwerlas systemd[1798]: plasma-kwin_x11.service: Main process exited, code=exited, status=15/n/a
mar 14 21:43:19 gwerlas systemd[1798]: plasma-kwin_x11.service: Failed with result 'exit-code'.
mar 14 21:43:19 gwerlas systemd[1798]: plasma-kwin_x11.service: Consumed 26.642s CPU time.
mar 14 21:43:45 gwerlas systemd[6263]: Starting KDE Wayland Compositor...
mar 14 21:43:45 gwerlas systemd[6263]: Started KDE Wayland Compositor.
mar 14 21:43:45 gwerlas kwin_wayland[6359]: No backend specified, automatically choosing drm
mar 14 21:43:47 gwerlas kwin_wayland[6359]: XKB: [XKB-595] Unrecognized RMLVO layout "ir" was ignored
mar 14 21:43:47 gwerlas kwin_wayland[6359]: XKB: [XKB-595] Unrecognized RMLVO variant "pes_keypad" was ignored
mar 14 21:43:47 gwerlas kwin_wayland[6359]: XKB: Multiple definitions of group 3 name in map 'basic'; Using 'Romanian', ignoring 'English (US)'
mar 14 21:43:47 gwerlas kwin_wayland[6359]: XKB: [XKB-107] inet:243:58: unrecognized keysym "XF86AudioBassBoost"
mar 14 21:43:48 gwerlas kwin_wayland[6359]: The theme "KDE-Story" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 14 21:43:48 gwerlas kwin_wayland[6359]: The theme "KDE-Story" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 14 21:43:48 gwerlas kwin_wayland[6359]: The theme "KDE-Story" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6456]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6456]: > Warning: Multiple symbols for level 1/group 1 on key <FK23>
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6456]: > Using F23, ignoring XF86TouchpadOff
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6456]: > Warning: Symbol map for key <FK23> redefined
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6456]: > Using last definition for conflicting fields
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6456]: > Warning: Symbol map for key <FK24> redefined
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6456]: > Using last definition for conflicting fields
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6456]: Errors from xkbcomp are not fatal to the X server
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6459]: The XKEYBOARD keymap compiler (xkbcomp) reports:
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6459]: > Warning: Unsupported maximum keycode 709, clipping.
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6459]: > X11 cannot support keycodes above 255.
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6459]: > Warning: Virtual modifier Hyper multiply defined
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6459]: > Using 0, ignoring 0
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6459]: > Warning: Virtual modifier ScrollLock multiply defined
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6459]: > Using 0, ignoring 0
mar 14 21:43:49 gwerlas kwin_wayland_wrapper[6459]: Errors from xkbcomp are not fatal to the X server
mar 14 21:43:53 gwerlas systemd[6263]: Reached target plasma-workspace-wayland.target.
mar 14 21:43:53 gwerlas kwin_wayland[6359]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/6359/root")
mar 14 21:43:53 gwerlas kwin_wayland[6359]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/6359/root")
mar 14 21:43:54 gwerlas kwin_wayland[6359]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
mar 14 21:43:54 gwerlas kwin_wayland[6359]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"The last two lines are of interest here. They appear while kwin_wayland is initializing the compositor. The Wayland compositor fails to create a framebuffer , which explains the freeze of the graphic stack you observe.
I can only speculate here, but perhaps KWin chooses the wrong device (NVIDIA drm)…
mar 14 21:43:45 gwerlas systemd[6263]: Starting KDE Wayland Compositor...
mar 14 21:43:45 gwerlas systemd[6263]: Started KDE Wayland Compositor.
mar 14 21:43:45 gwerlas kwin_wayland[6359]: No backend specified, automatically choosing drm
Check ls -l /dev/dri/ and report back.
I’d expect /dev/dri/card0 to be the Intel device and /dev/dri/card1 to be the NVIDIA device.
If that is the case try starting the Plasma Wayland session from a VT using
export KWIN_DRM_DEVICES=/dev/dri/card0
startplasma-wayland
Does that succeed?
1 Like
ls -l /dev/dri
total 0
drwxr-xr-x 2 root root 120 14 mar 22:04 by-path
crw-rw----+ 1 root video 226, 0 14 mar 22:05 card0
crw-rw----+ 1 root video 226, 1 14 mar 22:05 card1
crw-rw----+ 1 root render 226, 128 14 mar 22:05 renderD128
crw-rw----+ 1 root render 226, 129 14 mar 22:05 renderD129This works better. I am now answering your question from Plasma Wayland. I have two monitors, one with the VT and one with Plasma Wayland. Not perfect but a nice step forward.
Ok, good. After a bit of digging I’ve turned up a post which may be of help here
So…
sudo nano /etc/profile.d/kwin_drm.sh
and add
export KWIN_DRM_DEVICES="/dev/dri/card0:/dev/dri/card1"
Save and reboot. See how that goes.
1 Like
it seems to work. Thank you very much for your help!
Thanks for the update, and confirming that this works for you.
It would be worth filing a bug report with KDE Plasma / KWin (Wayland backend) so the developers can investigate why the compositor is picking the NVIDIA device by default and triggering the framebuffer errors. Include the hybrid hardware details, and logs you shared here, as well as the workaround used to get a working Plasma Wayland session.
Classification: Plasma
Product: KWin
Component: wayland-generic
Version: 6.6.2 (as per your inxi output)
Severity: crash (or major as it locks the system)
Bug reported https://bugs.kde.org/show_bug.cgi?id=517608
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.