We're continuing investigation to the performance issues, you can follow and react here: https://lemmy.world/c/friendicaworld

mastodon - Link to source

#Plasma is going all #Wayland

After nearly three decades of KDE desktop environments running on #X11, the future KDE Plasma 6.8 release (due early 2027) will be Wayland-exclusive.

Read the FAQ below to find out what this means for you and the future of KDE:

blogs.kde.org/2025/11/26/going…

Going all-in on a Wayland future

Well folks, it’s the beginning of a new era: after nearly three decades of KDE desktop environments running on X11, the future KDE Plasma 6.
KDE Blogs
#wayland #plasma #x11
This entry was edited (1 week ago)
in reply to Cameron Bosch

mastodon - Link to source

clerian

@cameron_bosch @a_blahaj X11 does support colour management - e.g. different input/output and working profiles for different applications + multi screen setups. This is really difficult to do in wayland - compare discuss.pixls.us/t/wayland-col… for more details. This is not about HDR.

Wayland color management

Just saw the following on the wayland developers mailinglist HDR support in Wayland/Weston and that reminded me that I always wanted to make a topic here to discuss color management on wayland, especially since the proposal from the wayland devs itse…
discuss.pixls.us
@Cameron Bosch @just a blåhaj

reshared this

in reply to KDE

mastodon - Link to source

Mikko Tuumanen

How do I handle the following situations in the future when xinput, xrandr, devilspie, xwit, etc. are gone?

- Multi seat setup: 2 × (gpu, keyboard, mouse)

- Multi pointer stuff, having more than one pointer and keyboard foucs simultaneously

- Automate any screen or input related changes? Change refresh rate before starting a game? Restore resolution after running a game in case it happned to crash?

- Start an application without window decorations directly into given coordinates and given size? And of course more than one instances of the same applicaiton with different coordinates.

Unknown parent

mastodon - Link to source

areacode

@enigmatico The decision has already been made that Wayland is what will be used so at some point we need to accept that leaving it in is keeping the rest from getting off the sinking ship. Like mentioned in the blog post. Also mentioned those that really need to have it need to switch to a LTS distro.

And we are still at least a year away from that happening.

@ENIGMATICO
This entry was edited (1 week ago)
Unknown parent

akkoma - Link to source

Éris Serène

And you're free to make the decision not to use it! It's not KDE's responsibility to spend time and effort on maintaining compatibility with a display server that is falling out of use and is largely unmaintained. It's not like there's no other option - if you want to stick with X11, use xfce, or even a plain old window manager. It's not compulsory nor sustainable for them to maintain compatibility with X11 - catering to a small minority of users who refuse to use Wayland or have issues with it will only harm the project in the long run, stymying the addition of new features and general stability of the codebase. By the time that X11 support is dropped from Plasma, developers will have had 19 years to adapt their software to Wayland (and even then, XWayland will remain). Free software is all about choice - if you don't want to move to Wayland, then you're free to use another desktop environment.
Unknown parent

akkoma - Link to source

Éris Serène

I'm not arguing that it's not going to cause issues, I'm saying that issues in the short term will prevent infinitely more in the long run
They've been switching away from X11 pretty much ever since Wayland was introduced into the codebase and stabilised
You eventually just have to pull the plug when the cost of maintaining something outweighs the benefit to it existing
This is how software always has and always will work
It's unfortunate, but that's the case
Unknown parent

akkoma - Link to source

Éris Serène

I understand where you're coming from, but if not now, when?
Nvidia's newer drivers have mostly stabilised Wayland support, and that was the last thing preventing the change
Anything else is really just holding the ecosystem back
I personally don't use Wayland (I run Qubes which depends on X11, and OpenBSD), but I understand that this change has to be made
If it doesn't happen now, chances are it never will, and we'll be stuck with the status quo of double the work for developers
in reply to areacode

sharkey - Link to source

Nube

Open source and Linux shouldn't be something like, “This is the decision, accept it or you'll be left behind.”

It's not just about taking away the user's freedom of choice; it's simply that many people are left behind. In my case, my hardware does NOT work well with Wayland, so I have to buy a new PC just because someone has decided that I should? Many people will be left behind by decisions like this, and that's not the spirit of open source. To me it sounds more like something an evil corporation would say

in reply to Nube

mastodon - Link to source

Cameron Bosch

@nube I understand where you're coming from, but there are two important things to note about this.

First, XWayland is NOT going anywhere. Almost all X11 apps will still work, they'll just run via XWayland instead of refusing to run.

Second, I do agree that Wayland protocol discussions have become "circular". That's is annoying and it should 100% be reworked to allow for more use cases.

@Nube
⇧