I’m sorry to respond after so long, but now I had time to read everything calmly.
Thank you very much, I have read that explanatory diagram twice, and although I have not understood most of the things, at least I have been able to see the difference.
So, from ignorance, it seems that Wayland has fewer steps to process than X. As a noob user who knows 0 programming, at first glance it seems that Wayland is “better” and faster than X.
But, since the apps/packages have not been programmed in Wayland, and all of them have been programmed in X, and only some have been “supported” by Wayland, then most of them do not work correctly in Wayland.
I mean, Wayland runs smoother and lighter than X for me (although I guess it depends on the hardware). But programs with gui do not work correctly for me, such as steam, jdownlaoder 2, clamtk, mouse settings in KDE, etc.
For example, it has some small bugs such as, for example, Steam in Wayland, when opening a chat, does not allow me to copy ANYTHING, neither through shortcuts nor by right clicking. It’s a small “bug” but it’s a problem for me.
So, if Wayland is a (composer is it called?) better than X, and this will improve the experience of users of KDE and other desktops, in the future, I think it’s great.
But I think, it seems that all Linux programs were made with X, so now we will have to transfer or make them all compatible from X to Wayland. And that will be a lot of work, and also possibly not all programmers do that with their programs.
There is also XWayland which I’m not sure what it is, but I think it makes X programs compatible with Wayland without the need to program, I THINK, I don’t know.
So, isn’t this something negative for Linux because the progress of Linux is being delayed a bit and causing quality problems for possible new future/current users who are now joining Linux?
Like for example me, who is having these problems with Wayland, and I didn’t know about all this.
In the case of the Steam problem on Wayland, I don’t know if it should be fixed by Steam, Wayland, or XWayland, or someone else, but it seems like this will take years.
Aside from all this, I’m sure that X and Wayland have other advantages and disadvantages, but I wish there was some way for this to be solved in a few years.
One thing that I thought when I was using Linux, and I was using Windows + Linux with dual boot, is that having X and Wayland was something negative, since Windows only had 1 desktop, and that was something that I didn’t like in Linux.
I mean, I don’t see it as a bad thing now, but I think we should unify a single desktop that has as few steps as possible to render, that works better, and that has a future. And that we don’t have to create another new composer in 10 or 20 years.
But I speak from total ignorance, so I don’t know.
Yeah it’s hopefully gonna be fixed with explicit sync that is coming in June(?).
Thanks friend. But, you mean this?:
If you mean “explicit sync protocol”, isn’t this supposed to be released tomorrow, May 15?
And, what does this have to do with GUI programs working? I mean, it will fix the flickerin, but will it fix the other little bugs that are not visual?
Yeah but it need a lot of parts and support witch I think will be complete and out in June or sooner?
It will(supposedly) fix alot if not all of Gui issues like Steam flashing/blinking.
Damn it!
I’ll have to wait another month! I was so happy because I thought the driver was being released today or something…
Anyway, thank you very much for all the information friend. I will try to look at our forum every day and then I will know when it has been launched.
Thanks again friend!
No problem! We are all here to help or ask for help on this great forum!
It’s on its way… Note beta final in june And KDE is releasing Plasma 6.1 in Jun.
“KDE Plasma 6.1 desktop environment release, due out in mid-June 2024.”
Omg, thank you very much for letting me know! I am really very happy with this, since I get better performance in games with Wayland.
Maybe this won’t solve the “compatibility” on some programs that work on X11 and not on Wayland, but this will definitely solve the flickering and desynchronization in games, which is the biggest problem I had.
I’m looking forward to June. Thanks again friend! 
X11 is better for gaming, 100%. It isn’t because it’s either is inherently better for gaming or anything (although it is cuz vsync is always on on wayland), it’s just that most games can only run on X so if you run them on wayland you’d be running them through xwayland anyways and usually lose a bit of performance in the process (We’re generally talking marginal though, like 1-3fps difference or something)
I don’t think u should reallyy be too worried about which is better for gaming, the right question to ask is which is better for you.
Games on wayland is great! Compared to x11 it’s little(1-3 fps as you say) to No difference!
I haven’t run into any problems gaming in wayland.
And Wayland is the future(unless we get something new).
Its mostly true but on Plasma Kwin is able to allow tearing (so vsync off) since 5.27. Its was mostly a KDE push but since then Hyperland and Weston also added the protocol (https://wayland.app/protocols/tearing-control-v1).
Seem like a nice tradeoff since xwayland provide things that X can’t provide like HDR or VRR for example.
the thingy to disable vsync isn’t exactly stable yet, it can break other things. And there is no HDR neither in wayland nor in x11, i think again that kde had experimental very early HDR on wayland or something like that, last i checked which was a few months ago. And i think VRR is supported on X though i’m not a 100% on that.
Work without problem on my end (AMD GPU). Don’t know for team green/blue tho.
HDR is on Plasma since 6.0 but most apps don’t have support for it.
For HDR compatible games, its already possible if you are not afraid to ticker: https://www.reddit.com/r/linux_gaming/comments/1csmsrp/setting_up_hdr_support_on_linux_plasma_6/
I’ve tested on my end and was able to play Star Wars Jedi: Fallen Order with HDR.
My bad, look like its possible https://wiki.archlinux.org/title/Variable_refresh_rate
it’s probably fine on blue, but green likely has problems. At least until explicit sync, maybe that’ll somehow fix it.
Could just be you haven’t happened upon the situation where it breaks something yet.
Thy announced a date for Plasma 6.1
“The final KDE Plasma 6.1 release will be available starting June 18th, 2024”
Plus some time for it to get into Arch.
And the new 555 Nvidia driver is coming around that time as well.
That’s great, thanks for letting me know!
By the way, Arch is always the first “distro/repository/branch” (I don’t know how to say it correctly), to receive updates, right? I mean, it’s the fastest, ahead of Debian and Fedora/RedHat, right?
I mean, KDE desktop/GUI is from the KDE Neon distribution, based on Debian-Ubuntu, so they will be the first to release it because it’s their distribution. But the next ones should be all Arch based distros, right?
Same or something similar I guess with nvidia drivers.
Sorry, just to be sure, you both are talking about: red = amd, green = nvidia, blue = intel or Arc? xP
Yeah it’s amd, nvidia and intel.
I use nvidia GPUs and intel iGPUs, and from my experience intel is incredibly stable, but nvidia isn’t. When I tried wayland with nvidia, the login screen would lead me to a black screen. I’ve also had multiple issues with intel/nvidia hybrid setups, and have heard lately of many nvidia driver bugs.
amd is much more stable, but I think intel is the most stable because i occasionally hear about new amd driver issues.
Oh I see, thank you. Does this also happen with CPUs, or are Intel and AMD equally stable?