SUMMARY I installed a relatively simple plasma 6 RC2 environment, including only plasma (6) environment & apps, plus firefox. In summary, nothing that should require xwayland explicitly. After running "startplasma-wayland," xwayland is observed as always running, without any way to disable. STEPS TO REPRODUCE 1. Install plasma 6 2. Check running processes 3. OBSERVED RESULT xwayland is loaded EXPECTED RESULT Similar to gnome, I'd expect xwayland to start on-demand.
Right, we don't yet support launching XWayland on demand. It's something we want and are looking into, but it's not here yet.
(In reply to Nate Graham from comment #1) > Right, we don't yet support launching XWayland on demand. It's something we > want and are looking into, but it's not here yet. Thanks, I guess I misunderstood this commit. Sad, I was looking forward to running a Wayland only plasma experience! https://invent.kde.org/plasma/kwin/-/merge_requests/3527
Yeah, that's what this part is all about: > For a full desktop plasma session this patch effectively does nothing too useful as we still start kcminit and make xrdb calls on startup which in turn will launch X What David is saying is that *in principle* we now support loading XWayland on demand, but it doesn't actually happen yet because Plasma includes components that still always demand X11 stuff, so XWayland always gets loaded.