Notice about KDE Plasma Edition

EbonJaeger

In the upcoming sync, our KDE Plasma edition will only offer the Wayland session by default. To keep everything aligned with the removal of X11 support in GNOME, we've decided to follow a similar plan for Plasma.

Solus Plasma Edition has used Plasma Wayland by default since the release of Plasma 6.0. The X11 session will still be available, but it probably won't exist forever. As with GNOME, the main focus is on improving Wayland, which has already come a very long way in recent years. So, we instead decide to subpackage the Xorg session to a new plasma-x11 package, and warn that it is DEPRECATED in its description.

Like we said in the GNOME announcement, we believe that the Wayland experience has matured significantly, and that this decision will not have a massive impact on users.

User Impact

Users will notice the login screen (SDDM) will only offer the Plasma Wayland session, assuming no other desktop or WM is installed.
Users that still need the X11 session can install plasma-x11 to add it back.

References

https://fedoraproject.org/wiki/Changes/KDE_Plasma_6

MikeK61

Can you please check my post in the last sync thread.
Maybe it is related.

Harvey

MikeK61
Are you on the unstable repo? If not, no it cannot possibly be related.

If you are on the unstable repo and have updated. Did you reboot?

TraceyC

MikeK61

ℹ Moderator Note
Don't use unrelated threads to ask about your issue. If you want a more dedicated response, start a new Support thread.

As the post says, this is in the upcoming sync. There is no way something that hasn't been rolled out to users can affect your system.

ETA: Unless you're on unstable. But still, new thread please.

MikeK61

Harvey

No i'm not on unstable and of course i always reboot twice after an update.

@TraceyC i thought it was related sorry my bad.

SilverBird775

It's about the native X11 Plasma session, right?

I wonder if the QT_QPA_PLATFORM=xcb environment variable will still work without the deprecated plasma-x11 package. It should work as before, I assume. Forcing specific application to use Xwayland is still a very handy tool for KDE applications that for one or another reason don't work properly with native Wayland.

Harvey

SilverBird775

kwin is Plasma's Wayland compositor.
kwin-x11 is only used when using x11 sessions (xorg-server)

When in a Wayland session and an app does not have native Wayland support or you wish to force a Wayland compatible app to use "x11" it does not actually use x11 but instead xwayland which is a partial protocol reimplementation of x11 for compatibility purposes on Wayland.

So no kwin-x11 is not needed for this purpose. I do not have kwin-x11 installed and everything works:

zmaint

Is wine and/or proton native yet under Wayland? About 75% of my computer usage is gaming related. Also last time I tried Wayland there was a ton of issues drawing game launchers, context menus, etc.. and flatpak based chrome web browsers wouldn't launch.

Original-Syn

zmaint I game and run Steam through xwayland with no issues. I also have a few other Wine apps that I need for various business tasks that run just fine as well.

SilverBird775

zmaint
Here is my Solus gaming tips for native Wayland.

Wine games

first, enable Wayland in wine registry:
wine reg.exe add HKCU\\Software\\Wine\\Drivers /v Graphics /d x11,wayland

With this tweak made I would highly recommend to match the Plasma display scale factor with winecfg - Graphics - Screen resolution. They should match, its super important or everything will run off scale. In my case:

Plasma Display Scale 200% == Wine 192 dpi

When not perfectly matched graphics scales or mouse input scales may be wrong in game, especially non-DPI aware ones.

SDL2 Linux games

SDL_VIDEODRIVER=wayland
most cross-platform games are feeling okay, but some like Dota 2 are talking to X11 directly so they fail.

Some crazy ones (Like Ren'Py engine novellas), that supply it's own stripped down SDL2 copy may need to redirect SDL to Solus native lib:
SDL_DYNAMIC_API=/usr/lib64/libSDL2-2.0.so.0

running SDL2 linux game with pipewire audio server:
SDL_AUDIO_DRIVER=pipewire

Harvey

No. Steam itself isn't even native Wayland and you can see I am playing Bauldur's Gate 3 and its using xwayland perfectly fine.

zmaint

Original-Syn Thank you. Last time I tried it (about 4 months ago) it was not a good experience. Will give it another go.

zmaint

Guys will Anydesk work on Wayland? I support about 10 friends/family who use Solus Plasma and while I don't use it frequently (mostly because Solus is rock solid🙂 ) I do need it from time to time (mostly to help with spreadsheets and games etc..).

Original-Syn

zmaint Anydesk still has issues on Wayland. RustDesk works well, last I saw, and it is available as Appimage or Flatpak.

zmaint

Original-Syn Thank you will give that a test run.

User_007

It's big joke that kde plasma don't remembers windows position on wayland :/

Original-Syn

User_007 Geting close. It can remember location, but not always size. They are actively working on proper support. You can use things like Remember Windows Position. https://github.com/rxappdev/RememberWindowPositions

zmaint

Original-Syn Rustdesk is a flickering buggy mess, but at least it is workable. Anydesk just gives the error "no wayland support" when you try to connect.

Original-Syn

zmaint It has been a while since I tried RD but do not remember much flickering. Hopefully they get that cleaned up. I know Anydesk is also working towards full Wayland support as well, but is not there.