EX-11: Prepping for Plasma’s Last X11-Supported Release

When we first announced the transition to Plasma Wayland, one of Martin's slides from stated, "It's done when it's done!"


This is a companion discussion topic for the original entry at http://blog.davidedmundson.co.uk/blog/596/
9 Likes

I’m glad that there is such strong progress on this. Hats off to all the devs.
I just have one issue with it, there is no headless remote access using Wayland, x11 is the only option.
I would love to switch over but I use my PC with my multiple screens to remote into my work laptop (with it’s one screen), and I can only use x11 for that.
Is there a solution to this coming up? I’m hoping I don’t have to stay on 6.7 indefinitely.

1 Like

There is something coming out! It’s targeted for Plasma 6.8.

1 Like

Its Plasma 6.8 still target for 2027 as promised?

Im still using X11 and i still rely on it, it is important for my Nvidia GPU and my Monitor because there is no Nvidia X-Server GPU Control’s available for Wayland.

When Wayland hit the market i’m forced to replace my GPU and or my Monitor.

Fake News. I see massive user’s still on X11 on many other Distro’s that data is pure propaganda.

Yes.

Well yeah, On Wayland there’s no X server. But the NVIDIA control panel software works fine on Wayland, or at least it’s supposed to. I don’t have an NVIDIA GPU, so I can’t personally verify that. But give it a try.

2 Likes

I gave it a try already, there is sadly absolute no option and no adjustment’s available in Nvidia X-Server Settings, the console is working and showing some minor GPU Info’s on Wayland but all the important stuff is complettly missing, absolute no adjustment are possible in Wayland with Nvidia GPU’s, GPU related bash scripts also no longer working for my Nvidia Card.

Im using Wayland on my AMD Laptop total fine, but for my PC it is a complet different story.

That you guys want to clean all X11 stuff from the Desktop Environment, is to early!

Im forced to buy new hardware when Plasma 6.8 rolled out in my Distro and i also asked in my Distro for assistant already… there is no way to use Wayland with my Monitor without the option to make adjustment, the whole screen has color grading issues and my Topic is unsolved till this day:

If that is the tool’s name then it will likely be an X11 application, which means on a Wayland session it will connect to the nested XWayland server.

Since that is not the main display server it will probably only expose interfaces that it can actually either handle internally (X server specific settings) or things that any Wayland client can ask the compositor to do.

Controlling GPU/driver settings will need a tool that actually talks to the driver.
This might originally have been integrated in to the X-Server tool but this part of the functionality might somehow assume things that are no longer true when used with XWayland.

The Nvidia will likely have a tool that is not tied to any specific display server and can directly talk to the GPU. Their chips are quite common for high end embedded systems which often don’t even run a display server as they only have a single application in control of the full screen.

At some point Nvidia might even fix their GUI tool to be able to talk to the driver when running on Wayland (directly or through XWayland).

1 Like

The Nvidia settings app on Wayland can actually do this - you can still use it to set fan speeds and overclocking / undervolting.

What isn’t in the Wayland app (to my understanding) is the kind of display adjustments that can’t be done in a compositor-independent way on Wayland.

I would also expect it to be able to do things like gamma correction since even monitors can do that. Or enabling/disabling G-Sync.

Quite surprising!

Could be a limitation of their desktop stack and their embedded drivers/tools are more tailored for being display server agnostic since most of them don’t even run any.

Maybe their desktop setup still requires a hardware specific X11 backend rather than having a fully capable kernel driver the way Intel’ and AMD’s setup work.

Or their GUI tool needs some not-yet-ported user space component in order to make certain driver adjustments.

Sadly their settings tool is likely as closed source as their driver and nobody but them can investigate further, let alone address these shortcomings.

I have a question would an Electron application launched with --ozone-platform=x11 still run as an X11 client under XWayland, even though Plasma itself is running on Wayland after the X11 drop?

Yes.

The “X11 drop” is only for components of Plasma, e.g. the ability to run them as X11 clients.

For example when Plasma desktop shows the “Window overview” it has different means of communication with kwin_x11 and kwin_wayland. From 6.8 onwards only the latter.

2 Likes

The settings tool is open-source, but yeah, trace the breadcrumbs of the API calls and eventually you’ll get to something closed.

That said, Plasma on X11 offers gamma correction by writing to xorg config files, rather than leaving it to the Nvidia (or other vendor) app.

Quite interesting.

That would at least allow research into why certain settings are hidden/disabled and how they are, at least in principle, communicating with their driver.

A quick glance seems to indicate that they are actually not communicating with the driver much but mostly with some Nvidia specific X11 extension.

I am not really used to reading X11 code so I might be wrong but if they are indeed using some vendor specific extension then the tool wouldn’t even work on a regular X server and this fails on XWayland.

True, there will be limits on what others can do.

Right, this can probably be done on many levels.
Since it appears some monitors can do it regardless of graphics card, it should also be doable by the graphics card regardless of which software handles the output content.