"Hostage" and "sabotage" are a little excessive. I don't think Nvidia is doing anything purposefully nefarious. Rather, I suspect they don't see much benefit in supporting that right now. Wayland usage is relatively small in an already small Linux market.

This is definitely tied to the chicken/egg issue. They probably don't want to put all this effort into adding support for Wayland when it isn't really being used, but it's hard to use Wayland if you don't have the drivers from your GPU manufacturer that support it.

It's just like saying that governments are sabotaging electric cars because they haven't set up a massive charging infrastructure to support easy charging of the vehicles.

1 members found this post helpful.

It's there a how-to on how to run wayland on -current?

Simply choosing kde (or weston) in sddm fails to log in. Running wayland from console as user seems to fail. However I was able to run wayland as root, launched from console.

Do I need to add the user to some group?

I have to admit that I obviously do not have a clear understanding of just what the hell Wayland is supposed to be. I was under the impression that yes it is not xorg at all, and it is its own thing - but then you still need xorg itself, so it ..runs ontop of xorg? So - then you have xorg -> wayland -> and your DE? I honestly don't know at this point. I honestly was and still am considering the "full Wayland (shown in this screenshot) - which again I guess I misunderstood - it is still xorg just a wayland 'compositor' then?


However I also still have to consider if my NVIDIA chipset (GT710 - driverwise) , is even going to properly support it? Also someone said replacing xorg completely is not possible, probably because there was apps that are solely written to support xorg then most likely.

This should interest you :

https://www.secjuice.com/wayland-vs-xorg/

https://linuxiac.com/xorg-x11-waylan...ols-explained/

A clean install of -current will give you 2 options in SDDM for KDE.
- Plasma with X
- Plasma with Wayland


If you are using AMD/Intel graphics then both of these work out of the box. If something fails then there might be a problem with your installation.

Also note that KDE uses many of the same config files for Wayland and X11 so if you already started it under X and you switch to wayland, strange things can happen. Making sure everything is up-to-date and trying with a new ~/.kde is a good idea.

So, that implies that Wayland *IS* already installed and no further installation of Wayland or full-Wayland is needed, correct?

Yes it is installed. Wayland is actually a dependency of a Wayland Compositor. You don't start wayland and then start kde in the same way you would with an X server.

KWin, the window manager for KDE Plasma can act as an X client or a Wayland compositor, depending on how you start it. The launcher scripts have been added to /usr/share/xsessions so most display managers will pick them both up automatically.
The wayland people aren't very good at explaining the differences between X and Wayland. I presume this is because they are too busy bragging about how great their ideas are.

1 members found this post helpful.

Yea I am just trying to still figure Wayland out, and your command listed is even more bizarre to me now, as because if you start KDE manually with Wayland it is:
Also though, I am in inittab 4 though, with SDDM - but I have to assume if I choose the full Wayland option for KDE, it runs that too 'startkwayland' - but as you seem to have stated, it is still a 'compositor' , and not actual full Wayland.... So to someone like me it just seems rather confusing as I am taking it for face value that Wayland is already there, but no it isn't really the full Wayland.

As I understand it, the "division of labour" is different in wayland from what it is in X. With X, Xorg paints the screen and the applications are its clients. The window manager/compositor is also an X-client which coordinates the applications. With Wayland, the compositor is the server. The applications are its clients and do their own rendering using drm, while input is handled by evdev. It seems a lot simpler.

1 members found this post helpful.

..Y-..yea ok , but see now I am getting the impression that we have a server-running-ontop-another-server(?) - only because to me thats what it comes across which I know I am wrong, but again 1st impression. As shown in my last screenshot I chose the very bottom option:

Which then I have to assume the description is misleading - because the full actual Wayland is not actually installed to begin with, as per OP's post then, and essentially I am still using X11.....

Wayland as one of its goals is supposed to be its own server, at least thats what the articles presented to me implied - but right now as I see how Slackware is handling it - Wayland is just implemented as a 'compositor' then.....? I am also sure I am overthinking and making this more complicated than it needs to be; but then again going by OP's post ...I have to still conclude it is still just a protocol/compositor, and X11 is still the base..

It's basically just layers of abstraction, and wayland is trying to remove one of those layers.

So for both of them you start at the bottom and work your way up to the application layer.

For Xorg
- X Server
- Window Manager
- Application

For Wayland
- Window Manager as Wayland Compositor
- Application.

When running in Wayland mode, think of the window manager as if it were the X server. In the perfect world envisioned by the wayland devs you would never need to run X, but due to the fact that we all live in the real world, some sort of X server must run in order for most applications to work.

1 members found this post helpful.

In the Wayland/Plasma5 the display server is KWin. It is the boss and controls even the clipboard.

BUT, every Wayland desktop has its own display server, like Mutter on Gnome3 or Weston on, well... Weston. And everyone has its own set of features.

I would say that Wayland solves the dictate of Xorg server, where everybody shall run the same display server.

The XWayland is just a X11 server (and a Wayland client itself) which runs in rootless mode. So, for example, if you run a Firefox window, it's a X11 window, but the rest are still Wayland windows.

However, it's also possible to run XWayland in the traditional window root mode, and I managed to run (as experiment) our stock XFCE on Wayland, via Weston and Xweston. Believe or not, it works.

That's for applications that can run directly under Wayland. For those that can't, you need an extra layer:
- Window manager as Wayland compositor
- XWayland client acting as Xorg server
- Xorg clients

1 members found this post helpful.

But...isn't the Windows Manager still running under xorg at that point? Yea I am just slipping further and further into this entire rabbit-hole now I guess. I mean, hell not to intentionally derail the thread, but I feel now I have to look at macOS - isn't it TECHNICALLY running xorg as well and Quartz is what Apple's answer is to a compositor? Not like you can just remove xorg from macOS and still expect a desktop then.....


Yea I am just utterly confused now...

You can remove xorg from macos and expect the desktop all right.