Control: tags -1 +moreinfo Hi, thanks for your bugreport. The interesting bit here is what greeter you use to start your KDE session. As the greeter is responsible to start wayland and set the environment variables. Please share the name and logs of the greeter. At least from my point of view everything looks working. I checked: * I am running a KDE Wayland session started by SDDM ( the default greeter used by task kde) and I see the environment variables. (But any other greeter with wayland support should work. ) If you use any other greeter please try to test with sddm. * The live images tests are able to start session (and they use wayland session): https://openqa.debian.net/tests/overview?distri=debian-live&version=trixie&build=20250731&groupid=18 Regards, hefee -- On Sonntag, 3. August 2025 20:59 arthur.p.vincent@proton.me wrote: > Hi, > This is a follow-up to my submitted bug report (#1110357). > > Here is more context: > > I am using Debian 13 RC2, fresh install with KDE. > > Logging into the Plasma Wayland session fails to initialize > $WAYLAND_DISPLAY. That variable is completely missing (echo > $WAYLAND_DISPLAY outputs nothing), while XDG_SESSION_TYPE=wayland is set. > > As a result, critical KDE daemon services like kded6 crash in a loop. > Qt-based applications and KDE components log the error: > > Failed to create wl_display (No such file or directory) > qt.qpa.plugin: Could not load the Qt platform plugin "wayland" > > kglobalaccel never starts → global keyboard shortcuts (e.g. Fn key) are > broken. > > The KDE session appears half-loaded, with icons and panel, but no core > functionality. > > Workaround: > > Logging in via Plasma X11 works properly — all daemons and shortcuts OK. > > Attached log is from: > > journalctl -b | grep -Ei '(wl_display)' > > Let me know if you'd like me to attach that file or preview its contents. > > Arthur
Attachment:
signature.asc
Description: This is a digitally signed message part.