I ask as I see these choices in sddm or lightdm:
Plasma (Failsafe)
Plasma (Full Wayland)
Plasma (Wayland)
Plasma (X11)

So, which should one prefer and why?

I am really interested from the stand point of a user.

So, if you have had a better experience with one, or have encountered issues with some, please let us know.

The is to be able to help end-users looking for advice.

I've Full Wayland in KDE on -current. All I change is the theme to "Dark", turn off the compositor, and set the animation speed to "instant". My only complaint is it is missing the wl-copy command for those using password-store password manager. X11 option works fine with xclip from SBo. Everything else seems to work, and when it doesn't, is fixed in the next batch of updates.

EDIT: forgot to add:

I prefer Wayland for the newer code base, and I enjoy testing software. With that said, I have not ran to any major problems in Wayland.

1 members found this post helpful.

Thanks for your answer. Pease note that I have in mind users of Slackware 15.0 rather than -current if that makes a difference.

1 members found this post helpful.

Even, as you know, I'm a huge advocate of Wayland/Plasma5 I for one I would chose as default for regular users the X11 variant of Plasma5, being the most robust.

Regarding the Wayland type of sessions, most stable of them is Plasma (Wayland) while the Full variant may have various issues depending on hardware and user usage.

In fact, the difference between those two Wayland sessions is that the Full Wayland forces the usage of native Wayland support while the other one leaves to application the ability to use either this or the X11 via XWayland.

How NOT all KDE applications are fully ported to Wayland yet, the non full Wayland session may behave much more stable.

And this is important. Very important. Consider that a Wayland server (KWin) crash will mean the crash of entire desktop.

BTW, I for one I use daily the standard (mixed) Wayland session.

7 members found this post helpful.

Except for the russian accent, same as LuckyCyborg

EDIT
This is what LuckyCyborg is talking about:
https://community.kde.org/KWin/Wayland

1 members found this post helpful.

I have been using -current Plasma Full Wayland for several months, but I put it to fairly limited use - everyday stuff like internet browsing and email. The one problem I’ve run into is that Seamonkey segfaults, apparently not supported on Wayland.

I just installed 15.0 and am using Plasma X11 (I’ve been getting by fine with 14.2 and -current) and have run into no problems with it, but that’s not a very long time to find problems, so can’t point out any there.

BTW the installation of 15.0 was quick and smooth. Once again thanks to Pat and everyone on the Slackware team for a great OS!

TKS

1 members found this post helpful.

Agreed. I'm running X11 Plasma at run level three on my Slackware64-current unit and my Slackware64-15.0 unit. Very robust, stable and surprisingly light on system resources.

2 members found this post helpful.

Same here. Good ol' run level three, as they say...

1 members found this post helpful.

Same here, running level 4.

1 members found this post helpful.

Except for l'accent Francais, same again!

I'd agree that X11 is probably the most robust of the choices available in Slackware 15.0

2 members found this post helpful.

I would and do go with X11 for KDE. Reason. I had some serious issues with Wayland. The show stopper was clipboard handling with LibreOffice Calc. Those issue may or may not have been fixed but I am not willing at this point to give Wayland another shot, since X11 works.

I have always used x11 as a session
But since I switched to Xwayland, I don't have any problem, except for the region selection option in Spectacle (which worked for a while, but not anymore)

I'll predate the first post and say that right after the 15.0 install I did startx just like I used to do in previous Slackware versions, and KDE loaded. And I have no clue which scenario of those four mentioned happened. Where can I read more about it?

Currently, starting KDE in Slackware64-15.0 starts Plasma (X11). To use another variant you need to use sddm (runlevel 4).
EDIT: As marav stated in next post (thanks!) you can also use startkwayland instead of startx (on runlevel 3)
EDIT2: startkwayland seems to start Plasma (Wayland). To start Plasma (Full Wayland) you would need to set GDK_BACKEND=wayland and QT_QPA_PLATFORM=wayland before the command as done in /usr/share/wayland-sessions/z_plasmafullwayland.desktop:So if I am right you could write a /usr/bin/startkwayland-full command with this content:Caveats:

1. I did not try
2. Bear in mind the known issues using full wayland.

Some readings:
https://wiki.archlinux.org/title/KDE#Starting_Plasma
https://community.kde.org/Plasma/Way...ion_management
https://wiki.archlinux.org/title/Wayland

tl;dr: KDE with Wayland is WIP, hence the initial post of this thread.

2 members found this post helpful.

In fact, if you want to start a Xwayland session, you need to use startkwayland instead of startx (on runlevel 3)

5 members found this post helpful.