KDE Plasma 6 goes Wayland by default, initial HDR gaming support

Quoting: enigmaxg2Since the vast majority of GPUs out there are Nvidia, and it's known how bad they play with Wayland, I see this as a risky move.

I have heard from actual Nvidia users that, with the last few drivers, it's actually been pretty good or at least fine enough.

As someone who've been using KDE Wayland for the past year or so, I can say that for the most part it's ready for most users. It's just waiting for some application devs to switch over to the new method, and with KDE on Deck representing a massive userbase, I think this would be something that tips over those devs into putting in the work. Here's hoping that Valve will finally focus on Steam on Wayland - still waiting for Remote Play Together to work well, which it should be able to, given how I've been using KDE Connect to control my PC for a while now.

It looks like 2024 will be the Year of Get Wayland Done.


Last edited by fenglengshun on 15 November 2023 at 9:06 am UTC

Quoting: enigmaxg2Since the vast majority of GPUs out there are Nvidia, and it's known how bad they play with Wayland, I see this as a risky move.

Well the latest NVIDIA driver 545.x do work with Wayland now and quite well. However often if not always the MODULES for it to work under Wayland are not setup by default so it leaves loads of people with crashing or black screen on login.

I have a 4090 and everything in wayland is smooth as butter except for one major thing, and that is fullscreen apps, those need Explicit Sync which is not yet fully supported outside of experimental patch support that you only get access to if you really look for them. (and know howto install them)

GNOME atm seems to be offering better performance for NVIDIA customers where as Plasma Wayland still has some performance issues and non existent experimental support for explicit sync.

Games run fine in windows btw. Also Gamescope 3.13 broke nvidia support somehow so use 3.12 (if you even want to use that, it doesn't fix the Massive tearing issues)


Last edited by TheRiddick on 15 November 2023 at 5:30 am UTC

It will be an absolute shitshow for a long while I mean how many years have they been trying to implement Wayland lol.

Quoting: enigmaxg2Since the vast majority of GPUs out there are Nvidia, and it's known how bad they play with Wayland, I see this as a risky move.

Unless they manage to tackle down ALL the issues in the 105 days (at the time of writing this) remaining until release, with little to no help from Nvidia.

They have been going for a couple years with this and got only a small success, unless a miracle happens, I see this becoming a shitshow.

It's not as risky as it might seem. On Windows the majority are indeed Nvidia GPU's, but on the Linux side the majority is actually Intel or AMD GPU's (even if we exclude Steam Deck). However Nvidia is a gigantic company and I'm sure the Wayland situation will improve soon.

Quoting: jo3fisIt will be an absolute shitshow for a long while I mean how many years have they been trying to implement Wayland lol.

In reality, I would say that most of the push for Wayland has only really come in the past three years, between the wider defaulting to Wayland and leading to more groups actually contributing for Wayland and Wayland-adjacent development - such as Valve with Gamescope and KDE, as well as overall much more activity in the Portal and Pipewire, as well as things like xwaylandvideobridge, color management, and input-module.

Wayland itself is fine, it's the Wayland-adjacent protocol and applications that needs to catch up now.

Quoting: slaapliedjeJust seems weird to me. Anyhow, doesn't really matter as long as the sessions are available for each for compatibility (as I've stated elsewhere, I still have some randomly weird issues with Wayland, like Firefox and on-screen keyboards not activating).

I'm still at the stage of switching to Wayland, finding something that isn't working right or irritating me how it works, then flipping back to Xorg. Maybe one day they'll get there... :P

I have exactly the same experience. Gaming on Wayland (at least with AMD) is no problem for me. In fact I already use a Plasma Wayland Session on Nobara. But last time I also tried doing work on a Wayland session there were always things which didn't work, like not being able on Firefox to put a tab to a new window, drag and dropping of files sometimes didn't work. Screen sharing didn't work in many applications, mouse control with virtual machines had bugs. For now I still use Xorg.
But changing it as default is no problem for me as long as the old option is still available.
But back then I was trying out Gnome, maybe on Plasma I wouldn't have had those problems in the Wayland session.


Last edited by kaktuspalme on 15 November 2023 at 8:08 pm UTC

Quoting: enigmaxg2Since the vast majority of GPUs out there are Nvidia, and it's known how bad they play with Wayland, I see this as a risky move.

I've noticed that Debian does it right, if it detects you're running an nvidia GPU, the wayland session isn't even listed as an option (or at least it was with the last fresh install I did).

I keep trying Wayland, but there are one or two big issues that keep happening, so I keep resorting back to X11.

My hope is those things will get ironed out as X11 loses attention.

Quoting: 14I keep trying Wayland, but there are one or two big issues that keep happening, so I keep resorting back to X11.

My hope is those things will get ironed out as X11 loses attention.

Yeah, one more bug I keep running into is the copying of my password from the nitrokey app when I click on it from the drop down menu doesn't work in Wayland... I have to get it the long way around. I'm guessing because it's compiled with an older version of QT, which doesn't have any compatibility with Wayland.