While we wait to see what comes of the new X.Org Server Git branch plans and a possible X.Org Server 26.1 release, several X.Org libraries saw new point releases this weekend. These seldom-updated libraries saw new releases to ship various build fixes and other minor improvements.
Alan Coopersmith of Oracle’s Solaris team and long-time X.Org release wrangler spent a lot of time this weekend shipping new upstream X.Org library updates
Why are they doing this when Wayland sucks on 60% of graphics cards? Right when we’re catching Microsoft in a vulnerable state and more people are fleeing to Linux than ever?
Nvidia just sucks on linux. They put all their development effort in CUDA, and their general stuff focuses windows.
Maybe because it doesn’t suck anymore on 60% of graphics cards?
I have been dealing with Wayland Issues on my Nvidia card, so yeah, they still suck.
Ah, if it’s not working right for you, it obviously means it’s not working right for 60% of people.
What’s that? The situation has improved dramatically over the last two years, and many happily use Nvidia cards with Wayland without issues, me included? No, can’t be the case, you still have issues.
Actually that is not too far off from being true.
mesa right now has this massive regression on wayland: https://gitlab.freedesktop.org/mesa/mesa/-/issues/14674
And not long ago all gtk4 apps were totally broken on intel with wayland, this was recently fixed on mesa but that change has only hit people using archlinux and other rolling release distros.
No, it absolutely is very far off, unless you find actual studies & user feedback. Lets not do weird mental gymnastics to find logic in pure hyperbole. You gotta give me way more than one 1-week-old bug, and one bug that was quickly caught and fixed. Bugs are going to happen in software that is worked on.
The reason X was stable for a long time is because many new & nowadays important features (like fractional scaling) weren’t being worked on, the ecosystem was mostly frozen. There’s more churn around Wayland because it’s newer & supports more (and often structurally much better) approaches to solving its problems. Don’t want to get caught in that? Maybe don’t use a distro that is specifically known for shipping new software very quickly.
The performance regression? It hasn’t been fixed.
You will run into old wayland bugs lol, like GTK4 apps being totally broken on intel.
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/38373
On wayland even getting apps to draw their own icons is a total disaster, and doesn’t help the constant sabotage from gnome of refusing to fix those issues, and don’t get me started on the csd mess which is another source of nightmares.
Wayland suffers a lot of internal fragmentation, we didn’t see these kind of issues in the move from pulseaudio to pipewire because there is really only one implemenation of pipewire, guess what would have happened a bunch of DEs decided to make their own implementations of pipewire instead?
They are probably running a system full of “workaround” environment variables that are not needed anymore or something like that, and seeing issues because of it.
I’ve also had a flawless experience with Nvidia & Wayland recently.
Actually the opposite. I reinstalled everything last week or the week before.
Either that, or it’s Debian with its ancient drivers and libraries. Maybe even both.
This has been so much of the problem. The only light at the end of the tunnel is that it is literally just a matter of time until these users catch up and stop complaining.
Or how far behind is Mint on the updates for kernel, Nvidia drivers, KDE, etc? I remember them being really far behind on some things. It confuses me how Mint is suggested so often.
Oh yeah, Mint is also pretty special. It’s pretty good for non-gaming “it just works” purposes, but recommending it blind for gaming is just straight up evil: No Gnome. No KDE. Just three niche DEs that are still mostly stuck on X11. Meaning, that if you want to properly make use any recent monitor features (as in, decade old features) your only option is to switch to another distro.
It’s a surefire way to get someone to switch back to Windows.
https://forums.developer.nvidia.com/t/nvidia-please-get-it-together-with-external-monitors-on-wayland/301684
Year old bugs don’t exist. My thinkpad works perfectly fine, there is no war in Ba Sing Se.
Ah yes, I forgot that all Nvidia users also use their internal Intel graphics card. How could I?
Wayland does not suck on 60% of graphics cards. No need to spread misinformation
sucks on Nvidia, which has about 60% of the market share.
pre-edit: HAH it’s even worse, 73%.
https://store.steampowered.com/hwsurvey/
Definitely not all of the Nvidia users, since I am one, and have no issues at all. I am even on an “unsupported” configuration, since I use Sway and they don’t officially support Nvidia.
lol
And I have amd btw (bought the gpu to try sway in specific).
Also nvidia in specific, the creator of i3 recently made this post detailing all the issues he has had switching to sway:
https://michael.stapelberg.ch/posts/2026-01-04-wayland-sway-in-2026/
edit: sway doesn’t even support fifo v1 ffs.
So don’t use Sway, plenty of DEs are more polished.
Most of the bugs you linked to are not related to Nvidia or the post. I don’t know who is suprised thay Sway, which is relatively new, has unresolved bugs that i3, which is older, does not have.
If you are an i3 user the only solution is sway.
sway is 10 years old and they haven’t gotten backwards compat with i3 right, let alone other wayland specific issues like not having fifo v1.
Ok fair, but I still think that “a few bugs that make it not act like i3” is quite different from “doesn’t have backwards compat with i3 right”.
None of those bugs affect me, so I can see why my perspective of Sway being perfectly usable may differ from other users whose workflow is broken.
Looking forward to Sway having
fifo, seems to work well in KDE and Gnome