top | item 44302650

Long live Xorg, I mean Xlibre

84 points| dxs | 9 months ago |dedoimedo.com

203 comments

order
[+] MarkusWandel|9 months ago|reply
I get it about Wayland. Most of X is legacy cruft and even isolating that into XWayland or whatever it's called for backwards compatibility is better than having it front and center.

But yes, there are use cases it doesn't cover. Example. My elderly mom uses Linux laptops that I've rigged to (1) always have an SSH connection open to my server machine, with reverse tunnels, and (2) run x0vncserver.

Modern security people would cringe, but this is the real world. I can open her desktop any time, from 700km away, and fix serious disasters like: She accidentally double-clicked an email and it opened up in a tab that obscures her message list (Thunderbird). This has worked very well to keep her online and happily emailing.

Where is the equivalent for Wayland? I get the impression that "it shouldn't exist because security" and therefore won't. Luckily, the show's not over yet. I run Fedora. The main spin won't do it any more, but the MATE spin is perfect. It comes up in MATE and it uses X! Still happy. Other laptop installations I have running probably use Wayland and as long as nothing breaks, I don't care.

[+] yjftsjthsd-h|8 months ago|reply
> But yes, there are use cases it doesn't cover. Example. My elderly mom uses Linux laptops that I've rigged to (1) always have an SSH connection open to my server machine, with reverse tunnels, and (2) run x0vncserver.

> Modern security people would cringe, but this is the real world. I can open her desktop any time, from 700km away, and fix serious disasters like: She accidentally double-clicked an email and it opened up in a tab that obscures her message list (Thunderbird). This has worked very well to keep her online and happily emailing.

I'm not sure why anyone would mind the security of that setup? Provided that your server isn't compromised, that arrangement should provide both confidentiality and integrity, and if SSH is compromised then we all have bigger problems.

[+] sudobash1|9 months ago|reply
This is true with more "modern" setups. I tried rustdesk with Wayland. It somewhat works, but you have to be present at the "remote" PC to click a button allowing the sharing.

I periodically retry Wayland, and it does seem to be improving, albeit slowly. There are a few significant things that just aren't there, but mostly it feels like death by a thousand paper-cuts. I can't dock toolbars; I can't use xdotools; screenshares are flaky; I can't click and drag to upload to browsers.

I could live with Wayland, but the experience is still superior (for my use-cases) with X11.

[+] c-hendricks|9 months ago|reply
KDE and Gnome each have their own Wayland compatible RDP servers. It's annoying it's not as convenient as older X vnc servers, but it's not impossible.

For wlroots systems there's wayvnc.

[+] anon-3988|8 months ago|reply
If you already don't care about security, whats stopping you from running 10 year old software and never updating it? Its not like Wayland is going to ruin your older software and hardware.

I don't get why its such a big deal that software that:

1. no one wants to develop 2. is completely free 3. no longer being developed

is such a problem, its free. if its so important to you, why not contribute yourself? Should these people be forced to contribute to projects that they want to be free of against their will?

[+] treve|9 months ago|reply
Does Waypipe solve this problem?
[+] msgodel|9 months ago|reply
I love the idea of coming up with something simpler than Xorg or even X11.

Unfortunately Wayland devs seem to have become user hostile in a way similar to the systemd devs (your use case being incompatible or unsuported is your problem, shut up and let us rearrange the OS etc) on top of the software just not being very good. Basic things like running video terminal emulators just doesn't work as well as it does on X (comparing Xterm on X to whatever on Sway always seemed to have much higher latency on my hardware, even moving the window around seems to lag a frame or two behind where it should be.)

At this point wayland itself has gotten pretty old, doesn't support what most desktop Linux users need day to day (at least enough to replace X) and is so unpleasant to deal with I don't think I'll be trying it again. It's a shame, the bar isn't that high. Then again maybe X11 is the oldest still in use graphics API for a reason.

[+] lelanthran|9 months ago|reply
I use Linux Mint, Mate.

I occasionally write native GUI apps (not electron-based), and for the current automation application I am working on Wayland is an absolute non-starter[1].

Like the other poster, every few years I would give Wayland a try, but as of today, 17-June-2025, Wayland is still lacking features that I want.

I have no objection to using it, I just need it to be a replacement for X.

[1] My application uses X11 FakeEvent. Did not find a similar thing for Wayland.

[+] 63|9 months ago|reply
I'll throw my hat in the anti-Wayland ring. I have a 5-year-old graphics card from the most popular graphics card company in the world. And yet, in 2025, I cannot run Sway/Wayland on my Nvidia 3070 for more than 20 minutes without a crash. i3/Xorg works fine.

Wayland just straight doesn't work and the push to move everyone to it looks ridiculous from my perspective.

[+] jauntywundrkind|9 months ago|reply
AMD has great open source drivers that work wonderfully everywhere. Even their old hardware keeps getting amazing upgrades & enhancements, a decade+ latter!

Word on the street is Nvidia is doing a much much better job, for a year or so now. But, like, you are using a GPU that sway used to make you type "--i-wont-buy-an-nvidia-gpu-again" and now makes you type --unsupported-gpu to use.

It's not Wayland's fault if your video card can't do the pretty same sensible reasonable kernel calls asked of it without crashing. I realize that you might not really care about the distinction, I sympathize highly that it just sucks, and no one in open source likes this (Google image search "Linus Torvalds Nvidia"; 2025 only a bit better than 2012 if your bug report here really true I guess). But fault & culpability matters, and Wayland does way way way less special magic & is way more straightforward with how it handles the display subsystem than X, which half ignores the kernel & has its own absurd driver subsystems and mountains of jank overlapping extensions to do what kernels and GPUs just do these days. GPUs have it easy under Wayland!

[+] const_cast|9 months ago|reply
I know this conversation keeps coming up again and again, but this is firmly nvidia's issue. Nvidia has been antagonistic to the Linux desktop for forever.

Before Wayland, it was not sunshine and rainbows. For a long time, a lot of shit just did not work and there was no way to make it work. Nvidia did not care. It took Linux Trovalds shitting on Nvidia to make them care a little. It took YEARS for Nvidia on the Linux desktop to be decent.

And, to this day, a lot of Nvidia features just do not work, even on X. You get a MUCH better experience on Windows.

Wayland cannot see the Nvidia source code because nobody can. They're trying their best, but they're not going to regress to old ass versions of stuff to get it to work and they're not gonna throw spaghetti at the wall. Nvidia needs to step up because they decided they're the only ones who can develop the driver. There's nothing anyone can do.

[+] mqus|9 months ago|reply
At least in the past, this was an nvidia issue (not respecting the kernel). But I do understand the user issue here: X works, Wayland does not.
[+] neurostimulant|8 months ago|reply
Wayland and Nvidia seems to work better on bleeding edge distro that ships bleeding edge DE and latest stable kernel.
[+] trothamel|9 months ago|reply
I've tried to switch a few times, and keep going back to X. It seems like simple stuff - the big one is that I like to remote into my system and look at the screen, and with wayland, there's no way to look at the side monitor like I can with X11 and x11vnc.
[+] treve|9 months ago|reply
[project] is bad because it's missing [pet peeve feature] will never get old. Ultimately open source devs work on what they want to work on. Feature-wise Wayland may be worse in some ways than X11 and better in others, but it's winning because people work on it/with it.

But choice and competition is one of the best things about Linux, so if a small group is upset about losing X11 and self-organize to carry the torch, more power to them. Build a great alternative, and maybe present yourself as a choice rather than being so reactionary. You're not a rebel, you're just in a niche and that's OK.

[+] exiguus|9 months ago|reply
I understand that change can be challenging, but actively seeking reasons to avoid change is another matter entirely. The criticism of Wayland in this article seems unfounded. Transitioning to new tools can resolve many issues.

You have a choice: acknowledge that Wayland is faster, more user-friendly, and more secure, or remain tied to technologies from the 1990s.

Since Ubuntu has adopted Wayland exclusively for its new LTS release, I've noticed over the past few days that much of the criticism comes from Windows users who rely on RDP to configure Red Hat or CentOS with a GUI, or something similar. These users have become accustomed to the lack of security in Xorg to perform their tasks. Now, they must reconsider how they maintain their Linux machines.

In any case, I was unaware that Wayland was becoming the new systemd. Perhaps this is because I have been using it for more then four years, starting with bullseye (sid) / GNOME, and for about two years with FreeBSD / Sway. I use these systems daily at work without any major issues.

[+] eadmund|9 months ago|reply
> I understand that change can be challenging

It’s less about change and more about outright breakage. Wayland does not support me.

> You have a choice: acknowledge that Wayland is faster, more user-friendly, and more secure, or remain tied to technologies from the 1990s.

Wayland may be faster, it’s certainly more secure (in the same sense that a system embedded in a ton of concrete and dropped to the bottom of the ocean is more secure), but I’m not convinced that it’s more user friendly. It’s certainly not friendly to me, since it does not allow me to run my window manager of choice.

I’m not convinced that the technologies of the 1990s were necessarily all that bad, either. Yeah, there were some assumptions which turned out not to be the case in reality. And yeah, there is a ton of cruft. And yeah, no-one would design X11 the way it is today. But, you know what? X11, unlike Wayland, works for me.

I would love to use Wayland, honestly. That’s not a lie. But it doesn’t work. And from what I can see it doesn’t want to work.

[+] msgodel|9 months ago|reply
The problem is it is not in fact faster and more user friendly. Maybe it works ok with your set up but that doesn't change reality and all the attempted gas lighting from devs and fans does is tick off the portion of the community that has legitimate problems with it.
[+] yjftsjthsd-h|8 months ago|reply
> Since Ubuntu has adopted Wayland exclusively for its new LTS release, I've noticed over the past few days that much of the criticism comes from Windows users who rely on RDP to configure Red Hat or CentOS with a GUI, or something similar. These users have become accustomed to the lack of security in Xorg to perform their tasks. Now, they must reconsider how they maintain their Linux machines.

I don't follow? If folks are using RDP, they don't need Xorg's less-secure remote access options, they can just use RDP? And Wayland has VNC and RDP servers, including GNOME having built-in RDP, so if people are using that then it shouldn't matter whether GNOME happens to have replaced X with Wayland.

[+] jmkr|9 months ago|reply
A few weeks ago I was looking into `XReparentWindow` because certain things use it (DAW Plugins). I don't think Wayland can do something similar (but I guess XWayland works), GTK and Qt both seem to have their own version.

Looking more into plugin libraries, a lot of it is based specifically on X, I don't think that's going to be rewritten anytime soon.

I've felt for a while stuck between X and Wayland. Same with Pipewire and Jack/Pulse.

[+] queenkjuul|8 months ago|reply
Agreed. Wayland has things to offer me, just like pipewire; then I actually use it, and find things i rely on don't work properly.

Why in bloody hell is it so hard to persist routing across reboots with pipewire? Why is Wayland turning 17 without a serious replacement for SSH forwarding?

Not that Pulse was ever excellent on that particular point, but it mostly worked without resorting to third party apps or hand writing scripts.

[+] yongjik|9 months ago|reply
Well, it's my understanding that Xorg still cannot do per-monitor fractional scaling these days, have they fixed it? That was the major selling point of Wayland for me, as an occasional linux desktop user.

Retina MacBook Pro was released in 2012, about 13 years ago. Personally, I don't think Xorg is in a position to sneer at its competitor for being "beta in quality" after "15 years into making."

[+] palata|9 months ago|reply
I don't get the Xorg vs Wayland fight. Feels like it mostly coming from people who don't contribute to either of them.

If you like Xorg, use Xorg. If you like Wayland, use Wayland. If you're not happy about an issue, contribute to it.

[+] Yizahi|8 months ago|reply
Author seems to conflate features unique to X11 with "useful" features or "desirable by many" features. I would try to project minimally, but the long list he provides is not that, at least for some significant number of users, or maybe even for majority (I suspect it is).

While on the other hand he conveniently ignores that a majority of users do need stuff like working HiDpi scaling, multimonitor use with different scalings, general monitor stability in all scenarios (plug and play from laptop, sleep/hibernate, go to 3D gaming and back to desktop etc.) and other stuff used daily by most users. And which is very brittle or even missing in X-11.

For professional use, I can live with Linux without graphical server at all. But for entertainment or creative arts use, monitor "just working per spec" is way more important than those thin client X-11 features inherited from mainframes and mostly unused.

[+] StillBored|9 months ago|reply
Wayland is architecturally garbage. Not for technical reasons, but social ones. Although social isn't the right word to describe a technology that encourages toolkit/DM/etc fragmentation which in turn breaks core functionality in the wider application ecosystem. Some of this isn't the fault of wayland directly, but it makes it worse. AKA by design there isn't a standard way to iterate windows and detect buttons/lists/various control types/etc which massively complicates if not outright breaks screen readers, while at the same time continues to fragment simple things like theming (and copy/paste is even worse than it was 10 years ago) if an application isn't using the blessed GUI toolkit. And in say fedora, the gnome folks seem to be designing to a device type that doesn't exist, its terrible out of the box with multiple monitors/etc while at the same time being terrible on touchscreen devices. I don't run it that much, but was showing my daughter who is perfectly competent in windows and macos (she carries both around all day!), how to navigate gnome, and jut shocked how absolutely none of it is intuitive to someone who has 'expert' level knowledge of all the common OS/phone UI's. Sure it looks slick, because its not cluttered with 'garbage' like you know, maximize buttons, scroll bars, and other things one might click on with a mouse. All the while doing cool things like reflowing the terminal text whenever the scrollbar appears/disappears. Its this complete lack of supervision/understanding. Sure on a phone touchscreen scroll bars might get in the way, but on a large screen laptop with two 30"+ 4K monitors?

And frankly, as someone who works closely with some of these distro's, I think there is a silent majority who have the same opinion but aren't willing to pay the political tax in their ecosystem for standing up and pointing out the emperor is naked for fear of sounding like a Luddite and being sidelined.

[+] marcodiego|9 months ago|reply
Having this specific guy becoming the lead/creator/maintainer of Xlibre, strengthens my argument about the kind of people who are against the Xorg->Wayland replacement.
[+] Thoreandan|9 months ago|reply
I'm waiting for BoringX or OpenX or, well, any other fork. Search for 'xorg drama'.
[+] MrArthegor|9 months ago|reply
I agree completely with this post. It’s the eternal issue in the GNU\Linux side, reinvent the wheel instead of enhance the existing, and submit half backed solutions and claim it’s the full replacement to the previous solutions
[+] shmerl|9 months ago|reply
> What I don't like is ANY, I repeat ANY software solution that champions mediocrity.

Then it should be proven that proposed alternative to Wayland is not mediocre or worse in issues Wayland is solving. Overall the post looks very shortsighted in looking at these issues from very narrow perspective, seemingly not realizing problems that need solving are much wider and not limited to one use case.

Wayland surely is not perfect and needs development (which lately seems to be moving at better pace), but I'm not convinced at all proposed alternative is better.

[+] devmor|9 months ago|reply
> very narrow perspective, seemingly not realizing problems are much wider and not limited to one use case

Ironically, this is the complaint many of us have about the development of Wayland.

[+] moomin|9 months ago|reply
I mean, I’m a Windows user so I have no dog in this fight, but it seems like the principal implants are that it’s slower, less responsive and less stable than the alternative. This seems like a primary use case. I’m not sure what the wider use cases you’re thinking of that justify the switch.
[+] devmor|9 months ago|reply
I agree with the sentiment of this post in general (annoyance with Wayland being shoved down my throat, despite missing core features of Xorg) but I am rather concerned about Xlibre's future as a project. The README being stuffed with reactionary political dogwhistles is downright weird and doesn't inspire confidence in longevity.
[+] jajuuka|9 months ago|reply
I disagree with the sentiment and welcome the future. But I do agree the way the author skips over the reason this exists and the problematic nature of their readme is a red flag. Either they agree with the dogwhistles or are being intentionally obtuse to proclaim that it's "only about the code".

Definitely don't see this project having legs or at the very least not advancing very far.

[+] timewizard|9 months ago|reply
> The README being stuffed with political dogwhistles is downright weird

For reasons I've never understood politics started invading open source about 10 years ago. What's weird is that these political ideas all seem to be highly aligned and this is the first major project that breaks that alignment.

Personally I'd prefer to see the politics, on both sides, disappear forever. It only pollutes the engineering and it fails to be convincing or meaningful in any other context.

> doesn't inspire confidence in longevity.

There are forces trying to kill X11 for their own internal reasons. I think as long as there is a project that is trying to maintain it, it will be successful, political warts and all.

[+] Lariscus|9 months ago|reply
[flagged]
[+] soraminazuki|9 months ago|reply
> The main dev, apart from being a reactionary nutjob

This is honestly an understatement. Posting antivax conspiracy theories on LKML? Reactionary. Writing anti-DEI rants in his REAMDE and COC files? Reactionary. But this long-winded rant [1] defending WW2 Germany? "Reactionary" doesn't even begin to describe it.

Whatever one's opinion on Wayland, his conduct [2] should be a huge red flag to anyone using his software.

[1]: https://web.archive.org/web/20190404153507/https://lists.dyn...

[2]: https://lkml.org/lkml/2024/10/24/1249

[+] Lammy|9 months ago|reply
> Xorg proper is now reverting a lot of their changes

They're returning to a previous state which they believe possessed positive characteristics absent from contemporary? Somebody should come up with a word for that.

[+] queenkjuul|8 months ago|reply
Yeah when I first heard of XLibre i went and saw some of the comments on the maintainer's freedesktop PRs and immediately lost interest in the project.

That was before i even knew they were a Nazi-defending nutcase insistent on dragging politics into LKML.

Frankly hope the project dies. Wayland can't replace X for me yet but I've no confidence XLibre is an improvement on X11 in any capacity.

[+] bmacho|9 months ago|reply
Can you explain how xorg developers removing a lot of their own code and calling it "bad" because they get mad at someone makes you think that xorg is professional and makes the fork look bad? I am only able to see it the opposite way, that is, xorg developers have no idea wtf are they doing.

I mean them deleting their own code only proves their own incompetence not Enrico's.

[+] MarkusWandel|9 months ago|reply
I should add, we also have a use case for X at work. Run gigantic EDA tool by submitting it to a compute server via LSF. It all works, just like magic; the right cookie is passed, X is remoted, it opens up, no fuss. What's the Wayland way?