Bug 480638

Summary:	xwayland always loaded in simple plasma-wayland session
Product:	[Plasma] kwin	Reporter:	Andrew Brouwers <abrouwers>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED LATER
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	5.93.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Andrew Brouwers 2024-01-31 22:37:46 UTC

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.

Comment 1 Nate Graham 2024-02-06 22:59:36 UTC

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.

Comment 2 Andrew Brouwers 2024-02-06 23:27:05 UTC

(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

Comment 3 Nate Graham 2024-02-06 23:30:42 UTC

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.