How to disable XWayland for the Plasma Wayland Session?

kenning · July 29, 2024, 11:32am

There is interest in being able to remove the XWayland capability, including XWaylandVideobridge.

This may save RAM and reduce attack surface.

github.com/secureblue/secureblue

[FEAT] Disable XWayland by default whenever possible

opened 05:53PM - 28 Jul 24 UTC

TommyTran732

enhancement

**Describe the benefit this feature would provide to the project** This helps… against: - Any kind of bugs/design issues with sandboxing solutions that still expose the x11 socket to apps - Apps accidentally using the x11 socket **Describe the solution you'd like** At least on GNOME, this can be done by creating `/etc/systemd/user/org.gnome.Shell@wayland.service.d/override.conf` with: ``` [Service] ExecStart= ExecStart=/usr/bin/gnome-shell --no-x11 ``` We should a ujust command or something to allow users to reenable XWayland. **Describe alternatives you've considered** None. There is none that I can think of. **Declaration** - [x] I declare that I have read the README and my feature request is in-scope.

People generally agree that having control over these things helps a lot.

Having a way to disable these (apart from a Flatpak override, for all apps) would help.

redstrate · July 29, 2024, 3:20pm

You need to turn off this CMake option: CMakeLists.txt · master · Plasma / KWin · GitLab

davidre · July 30, 2024, 9:02am

Edit plasma-kwin_wayland.service to it doesn’t use the --xwayland commmand line option.

No recompilation needed.

kenning · August 26, 2024, 1:09pm

thanks! that is the right answer, for now

skarpinis · September 24, 2024, 8:42am

Hi, after edit splash screen taking long time to show desktop any fix? thanks

kenning · September 25, 2024, 12:06am

You edited the desktop file and now it takes forever?

davidre · October 9, 2024, 7:19am

I think this could be because startup may be waiting for ksmserver to start which needs XWayland (its our x session manager).

Since xwayland less start right now is not something we do upstream I guess the only workaround I can think of is disabling splash?

Oleg · October 31, 2024, 2:19pm

I’ll tell what worked for me to those of you that run a non-systemd OS, such as FreeBSD, and want to run the fully featured GUI without the Xwayland-on-demand feature: I replaced StartServiceJob kwinWaylandJob(QStringLiteral(“kwin_wayland_wrapper”), {QStringLiteral(“–xwayland”)}, QStringLiteral(“org.kde.KWinWrapper”)); line with StartServiceJob kwinWaylandJob(QStringLiteral(“kwin_wayland_wrapper”), {QStringLiteral(“”)}, QStringLiteral(“org.kde.KWinWrapper”)); line in https://invent.kde.org/plasma/plasma-workspace/-/raw/master/startkde/plasma-session/startup.cpp , rebuilt plasma-workspace, and typed “ck-launch-session /usr/local/lib/libexec/plasma-dbus-run-session-if-needed startplasma-wayland”, which made kwin load. I typed Super+W to open kwin’s search bar, typed plasmashell , and finally, the fully featured GUI loaded. To gain access to power management, I typed “/usr/local/lib/libexec/org_kde_powerdevil”. I have no idea why plasmashell and org_kde_powerdevil have to be loaded manually in this setup, but the point is that I ended up with the fully featured GUI that had the Xwayland-on-demand feature disabled. The suggestion that was made in this thread about turning off CMakeLists.txt · master · Plasma / KWin · GitLab didn’t work for me.

Oleg · November 6, 2024, 5:11am

Well, after replacing things such as “ksmserver”, “org.kde.ksmserver”, and “/KSMServer” with “” in that file, plasmashell and other things no longer have to be started manually.