Some random 2c (I don't run wayland on debian... or systemd at all):
Your systemd-nonsense wall-of-text begins going pear-shaped with some errors regarding not being able to find xdg-desktop-portal on the (d)bus.
kwin_wayland then fails to start, pertinent errors likely being the "display :0" noise. That looks like x11 display notation, so it probably refers to xwayland... Which, IIRC, relies on xdg-desktop-portal.
Everything else then fails because it can't connect to the wayland compositor (kwin_wayland), and falling back to xcb (xwayland) also dies because no kwin_wayland means no xwayland either.
So... Is xdg-destop-portal[kde,gtk] stuff installed?
Is env being correctly populated by your display-manager (particularly the XDG_whatever stuff)?
What happens if you try starting plasma from the CLI, without a DM (e.g. /usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland)?
Does this also occur on bare-metal? I don't know how your VMs are configured, but wayland is kinda picky about KMS & GPU drivers...
Is anything setting XDG_SESSION_TYPE, GDK_BACKEND, QT_QPA_PLATFORM etc. to force x11 rather than wayland?
Your systemd-nonsense wall-of-text begins going pear-shaped with some errors regarding not being able to find xdg-desktop-portal on the (d)bus.
kwin_wayland then fails to start, pertinent errors likely being the "display :0" noise. That looks like x11 display notation, so it probably refers to xwayland... Which, IIRC, relies on xdg-desktop-portal.
Everything else then fails because it can't connect to the wayland compositor (kwin_wayland), and falling back to xcb (xwayland) also dies because no kwin_wayland means no xwayland either.
So... Is xdg-destop-portal[kde,gtk] stuff installed?
Is env being correctly populated by your display-manager (particularly the XDG_whatever stuff)?
What happens if you try starting plasma from the CLI, without a DM (e.g. /usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland)?
Does this also occur on bare-metal? I don't know how your VMs are configured, but wayland is kinda picky about KMS & GPU drivers...
Is anything setting XDG_SESSION_TYPE, GDK_BACKEND, QT_QPA_PLATFORM etc. to force x11 rather than wayland?
Statistics: Posted by steve_v — 2024-10-11 04:19