My kid (13) surprised me the other day and said he wanted to try Linux. He has seen me forever using it and got scared about W10 getting hacked or something so thought of trying it out.
I handed over to him my Fedora 43 (KDE plasma) install USB drive and once installed the problems began.
The monitor couldn’t be set to native resolution, and Steam didn’t want to run. Turns out that there is no wayland compatibility with the Radeon Polaris RX480. What a bummer, that card is perfectly fine for what he does on his PC.
We tried with the cinnamon version and that is working fine. He even has roblox running.
Tl;Dr: Wayland isn’t compatible with older hardware that most casual windows users are mostly going to be using.
If he wants to try plasma just install the x11 version on fedora:
sudo dnf install plasma-workspace-x11
Yup. Its not the default anymore (and for good reason), but it is still supported for now. This is a pretty straightforward solution to the problem.
I need some context for the picture?
Idk, especially when using the most recent version of Wayland compositors, it’s been great. Solved my display and touchpad issues.
I did have some Nvidia issues but that shouldn’t be surprising regardless of display protocol.
But like… use whatever software you want. Worst case you can always just nest a minimal Wayland compositor like cage or gamescope in your X session.
Problem with Wayland, is the liability of being to not able the use of some software, and not being able to foresee it.
X11 is also working well, and a lot of the “issues” people have with it is more about hearsay than real issues.
This is the reason why we have distro diversity: we can choose ! And laugh at innocent memes either way we feel about it
I will happily switch over once libinput isn’t absolute ass with my touchpad! Or if I could adjust its settings in any meaningful way!! Or if you could let me use my old touchpad driver!!!
Until then you can attempt to pry x11 from my cold undead still-animated hands
Plasma devs are currently focusing on input devices. Ideal time to offer them to help test your device and get amazing support out of it.
Or you could sit on your ass and do nothing, which is essentially gambling that they’ll happen to support it (or your next device) when you’re forced to switch at some point in the future.
Club is a war crime. I rest my case.
Wayland is the one thing that fixed a whole shit-ton of my problems overnight and now I find out nobody wants to use it under any circumstances.
¯\(ツ)/¯ Alrighty thenAlmost everyone uses it. We just never make posts about “our configuration works effortlessly, give us attention”
Only people with a bone to chew and shit to stir feel the need to post such things. Back in the day it was people who felt superior for debugging their steaming pile of init shell spaghetti, now it’s people who just can’t live without diving into X11 configuration files.
Plenty use it without knowing as it is what the Steam Deck uses in gaming mode.
The people who use it happily don’t make memes about it. I do have some weird errors every now and then, it’s definitely not as stable for me as X11. However X11 wasn’t very smooth with my multi monitor setup, and Wayland improved the smoothness of my PC enormously, so the random issues every now and then are worth it
I’m fine with X. Which problems did you have?
It’s been some time, but the biggest pain point for me on X11 was 4k@144hz. Short of some xrandr tweaks I couldn’t manage to set, Wayland immediately worked perfectly.
I suspect I ran in to x11’s limit in that case.
x11 when you try to use 2 monitors that don’t have the exact same atomic composition:
I think it took me 2 years to get six monitors on two GPUs working consistently under X11. Yes, I’m that fucking stubborn.
Wayland worked right from the start.
Weird. I have to switch all my machines to x11 in order to get multiple monitors working. Wayland just renders back screens on everything but main. Also makes remote desktop access buggy as fuck if it works at all.
Yeah, my multimonitor experience is better under x11, especially gaming (also Lutris has more features for x11 too in that regard). I only use it on that machine tho.
Zoom still doesn’t work right on Wayland.
As someone who uses many of its features for job interviews on a Wayland machine, what doesn’t work?
Possibly, yet against their best efforts, their shit works better now, see the end of this comment. But first:
I’ve ranted about this before, but Zoom is bone-chillingly badly written software. It’s also the only piece of software that I’ve never seen the code of, but will make comments about code quality and development practice with 100% certainty.
Zoom has broken for me in so many many completely insane and creative ways that the only explanation is that they have nobody keeping things in check and just an army of interns hacking away at things half-assedly until they “work”.
If there are 3 nice and standard ways to do things that can be easily googled, Zoom does a given thing in 2 more ass-backwards ways that make no sense and are fragile as fuck. E.g. they did screen sharing using GNOME’s screenshot API, at a time when every tutorial told you to use the dedicated cross-DE screencast API. When called out, they switched to a different GNOME API.
I think at this point they finally fixed it by actually using the API people told them to use years earlier, but who knows what other inane mistakes are still there to prevent things from working.
Hear hear. They can’t keeo up though, with standards changing every 20 years or so…
no screen sharing software works on it.
Liar. Proof by contradiction: Everything I use works (KDE Plasma).
- Discord
- Slack
- Teams
- even Zoom, despite being a dogshit pile of hacks
You can include Google meet, rust desk and jitsi as well
Yeh, zoom works on one of my two main machines on wayland…
See my rant about Zoom here: https://vger.to/lemmy.ml/comment/22183939
tl;dr: if there’s any issue with Zoom, you can always bet that it’s Zoom’s fault. Its bug density is just so much higher than anything else you run on a regular system.
Meet also works with screen sharing on Wayland, so I’ve no idea what the GP is about tbh
Removed by mod
Three-day suspension. Come back when you’ve learned to regulate your emotions.
Thank you!
You said “no screen sharing software”.
- That’s wrong
- It’s pretty much impossible that you don’t know that some screen sharing software works on Wayland
Consequently, that was a lie. Or you suck at expressing yourself and meant something different than what you wrote. But as written, definitely a lie.
Well… you just said no software works. They’ve given you counter examples, now you either have to cite examples of software not working with screen sharing or you’re the fool
- teams
- slack
- zoom
- Firefox browser capture for web screen share
never have I had any of these work for me, I’m not the only one either.
still doesn’t make me a liar and we can both be right.
Then you should have said “for me” or “on my machine”, but instead you said “no screen sharing software works on it” in a context where “it” can only be interpreted as Wayland in general.
And that’s wrong and you know it.
What you said is literally incorrect. There are screen sharing applications that work on Wayland. I just used one ten minutes ago.
so you’re sticking with “it works on my machine” then. cool.
also incorrect does not mean liar.
incorrect means not correct.
You said “no screen sharing software works on it”. If “it” is anything other than your POS laptop, then you’re a fucking liar
Removed by mod
I screen share on Slack with Wayland at work every day
My child will never see more than 8-bit color
I’m sorry to hear about your child’s condition. Hope they can find a cure for it soon, wish you all the best.
This is your freedom, enjoy it.
You’re absolutely free to maintain X11 when no one else does
Doesn’t Wayland slow to a crawl under CPU load? I get mouse updates like once a second if I dare to make this mini PC play a video.
No, it doesn’t.
Meanwhile I’m here on Wayland because it does things that x11 doesn’t.
Like wreck the playability of your games? ;)
If by “WRECK” you mean “improve” yes.
You must use a different Wayland than I do.
I play competitive multiplayer games with VRR on a 4k240 monitor in a tiling wm with direct scanout. Color management support (HDR, 10bit, anything beyond 8bit sRGB) is also coming along.
I’ve never had a better working setup than this. Everything on X was painful. Even just getting vsync to work properly used to be tricky in some cases.
I agree that wayland does miss features compared to X but a lot of them are conscious design decisions and don’t affect me personally. For example running graphical applications remotely through e.g. SSH or the complete lack of security allowing any application to easily read my keyboard input.
Xorg never worked quite right for me with multiple displays of different resolutions, orientations and refresh rates. Even after extensive setup, I would get screen tearing effects all the time. In wayland, everything just works OOTB for me.
I set TearFree in the mesa driver settings (not sure if it’s amd only?) so there’s no tearing even without vsync, I have a small 50hz display and a 1080p 120hz without issues
According to the X11 devs, it’s all a pile of hacks to shoehorn in features like this. Some things would have never been properly possible with it. So why it might work for you, it’ll never work for everyone.
if variable high refresh rate on my game monitor while discord and YouTube run at 60hz on the other wrecks playability, then definitely
I’m not one of those people who loves tearing though, so its good enough for me
It actually does wreck the playability of games for me by disabling the ctrl and shift key. A known issue no one has bothered to look into. I cant complain tho, theyre working their butts off for free
As someone else said: Linux Mint is late to the Wayland party, use a more robust DE when you want to talk about what “Wayland” can and can’t do.
It’s fucking weird people have such strong opinions about issues like X11 and systemd. They’re meant to be working in the background away from the user, and that’s exactly how I treat them. Actually systemd still provides some functions a user might have to interact with manually, for X11 I’m just baffled.
When I take an uber, I don’t care whether the car has an automatic or manual transmission.
Gnome forced me onto Wayland a few weeks ago and I’ve been dealing with issues ever since. Some issues even affecting the most basic level tasks like typing text, imagine dealing with that in 2025. Following your analogy, if the Uber with the fancy new transmission came to a halt every kilometre, you’d care too.
Same here. All amd. 13 year old cpu. Wayland has a ton of issues and 0 noticeable improvements for me.
I was an early adopter years back, so I reported bugs while I could still switch back when I needed to (which ended up being once to screen share with Zoom)
If you had done this, you wouldn’t be forced into a buggy environment now.
Nvidia?
Not even, amd on both my laptop and desktop, but still lots of issues. None of them major, but it adds up.
I think the average user wouldn’t care, Linux just attracts nerds. And I think it’s totally fine and even good that people care how their computer works—it shows that users care about their software working for them, rather than just wanting to go along with whatever is given to them. I think a lot of the positions people take about these things are very silly, but I’d still prefer someone to have a silly opinion about X11/Wayland or pid 1 than to not have an opinion at all. It’s nice that users are being actively involved in deciding what they want their system to be; it’s a nice change from the average user who’s like “well microsoft is screenshotting my screen every 5 seconds and feeding it into copilot now, guess I’m going along with that”.
I used to use some features that only worked on x11. Slowly I found alternatives or workarounds on wayland. So I understand the sentiment. Imagine you book an uber but it’s electric so they say you can’t book a ride that’s too long
I love your metaphor because it is exactly the kind of pedantry that is usually at play with X11 vs Wayland.
“I can’t take an electric uber because it has an effective range less than 400 miles!”
Who the fuck takes a uber to a destination over 4 hours away?
A normal person rents a car, takes a bus, catches a train or buys a plane ticket. Ain’t no one faring a uber for a long trip to another city. But that’s exactly the kind of complaints from people obsessively clinging to X11. They have a hyper specific use case or workflow that almost no one else uses.
Or maybe they’re developers that are tired of the wheel being reimplemented?
Eg.
https://www.jwz.org/blog/2025/06/wayland-screenshots/Every single person has different problems and priorities, and until hyper specific use cases/workflows work on Wayland, many will stay on Xorg.
I understand and agree. Anyone who has a super specific use case that means they still use X11, go ahead, no one is stopping them. But to complain or trash Wayland on that basis is asinine. Every single change in paradigm breaks someone’s workflow, that’s impossible to avoid. But the responsible thing to do is to adapt either with new tools and resources, or with a slight change in workflow. They act like people are taking away their toy, when in reality it is just adding to the pile of available toys. But they are upset because their toy is old and won’t get repaired anymore, while the new toy is slightly different but a bit easier to clean and repair, so they get upset at the other kids for playing with it. Ignoring that the new toy doesn’t make the old toy disappear.
The problem is many distros are going to stop shipping Xorg, because it is “not needed” anymore.
You should be able to compile it yourself though, even if upstream doesn’t provide it prepackaged
That’s where the adapt part comes in.
I had a friend who collected CRTs and VHS players right at the turn from DVD to bluray. He didn’t argue to kill LCDs, HD video or CDs. He didn’t wrote to Sony to complain that he couldn’t find VHS on Walmart anymore or that his hyper specific CC format didn’t work on DVD the exact same way it did on VHS. He accepted that tech culture shifted and that to keep his hobby up he had to take up a lot of the upfront work of maintaining old tech alive. He learned to repair old CRTs and VHSs and keeps them running for libraries. Even collaborating to digitize particularly niche historical content.
People who just complain and stay in some deprecated tech (instead of reporting bugs and working with the new way) will have a rude awakening when it’s just no longer supported.
I’m not saying everyone should be a early adopter, but this timeline was more than forgiving. People who did nothing but keep using the X11 GNOME session might run into Wayland session bugs now that they could have reported years ago.
Some may have bugs that fully break the session, and reporting bugs comes with a new problem: if you do, odds are someone will dismiss it, and/or tell you to fix it yourself.
Hmm, especially GNOME devs are definitely very opinionated, but “running a Wayland session on halfway-contemporary hardware” is definitely something all DE devs want to support.
So if you give them workable information, you won’t be dismissed.
When I take an uber, I don’t care whether the car has an automatic or manual transmission. But I care what MY CAR has! Especially since there isn’t a shop for my car and I have to do all my own maintenance. Like, init/systemd is a huge architectural change, it’s weird to you that people who depend on their computer to perform whatever function gives their life meaning and viability want to have a functional grasp of their system? That’s a big change to absorb for essentially no practical benefit to the problem domain.
If you only live in the GUI layer, you aren’t the driver. The implementation details are abstracted away from you. Your software are the real uber drivers, you’re just being driven around.
I found that systemd actually simplified all the things I was doing on sysvinit. BUT, I did hold out until Debian testing stopped supporting sysvinit, and I think waiting gave me a better experience.
With X11 -> Wayland, the main thing holding me back finding a tiling compositor that will work under Plasma and is packaged for Debian and the learning at least the basics. My XMonad configuration isn’t that special, but I’m really quite used to not having to re-arrange my own windows, and being able to move/resize/refocus all with the home row and modifier keys. So, I’m probably going to wait until Debian testing ships a Plasma that doesn’t support X11, and have to do some learning then.
In my eyes, it’s the same deal as conservatives coping with the changing world. There is a version where they just shut up and let the rest of the tech landscape improve while they happily stick to the X they know (X.org or even XLibre).
while they happily stick to the X they know
Aren’t there still maintained window managers that support X11?
Getting left behind is the natural and inevitable consequence of obsolescence.
Huh, why do I hear someone shouting about Windows 11 requiring TPM?
Yes, the people who refuse to either upgrade to Win11-compatible hardware or move to an OS compatible with their existing hardware will eventually get left behind. Both in terms of security and compatibility. It’s happened many times, from the fall of AGP in favour of PCIE, to every time Intel inroduced a new CPU socket. X11 is the next.
Bring in politics is a choice
You aren’t wrong though
Unless I’m terribly misunderstanding the word’s meaning (or anglophones once again redefined a word to reflect their current sensibilities), “conservative” doesn’t automatically imply politics, just that someone is resistant to new ideas. A person who only listens to music produced before the 20th century and goes into a rage when video game music composers are mentioned is a conservative, but not in terms of political views.
The issue is that in the political landscape, that word has shifted away from its social meaning. “Conservatives” in the US and parts of Europe are actually reactionaries, i.e. people pushing back against the status quo wanting to “return” to some idealized past that never existed like that.
So using the word “conservative” in its original sense might not be understood by people.
There are still existing issues with wayland that do not exist on X11. I’m talking, using last-gen consumer grade hardware that will break basic applications like, who knows, a web browser. Meanwhile the “upside” are extremely marginal to a lot of people. Different screen scaling isn’t implemented using proper DPI on most implementations, variable refresh rate is not something most people care about (I sure don’t care that my second monitor is capped at 120Hz instead of 144Hz because of my first monitor), etc.
So, yeah, for some people, it’s not a matter of preference, it’s a matter of having a stable, working system vs. a broken system where basic features are not a given.
If you took an uber and the car was a horse-driven carriage and your seat was a hole in a rotted plank, you’d complain.
I’d have to change desktop environments, because my current one only has “experimental” support in the latest version, and my distro is years behind, anyway. Your choices are pretty much KDE, Gnome or building your own desktop with a standalone window manager, and I don’t like any of those options.
Fair, although I never understood why people choose Mint and so on.
Plasma is so configurable that you can just make it look and act like you want, right?
So I guess it’s getting the GNOME experience (everything is simple, no setup) but with a classic desktop paradigm?
Pretty much, yes. It also used to be lighter in resource use than GNOME, though IDK if that’s still true. XFCE and LXQt are definitely lighter than both Gnome and Plasma, they are a lot more stable in the sense that they don’t change that much from release to release, and they play nice with third party window managers (e.g. tiling WMs).
What’s always funny to me when someome brings up missing features of Wayland is how, apparently, the missing features of X11 are getting pushed under the table or somehow also blamed on Wayland in some twisted way. Like, holy shit, compare the display settings of KDE on a modern display between Wayland and X11. My laptop didn’t even show a third of all options anymore.
Sure, it will be nice once Wayland can do a few things (better), the current development push surely helps. But it’s not like X11 can do everything either.
Yeah. “Feature parity or get out”, like dude we’re long past feature parity.
Wayland supports so much more stuff than X11 does, and what does X11 have that Wayland doesn’t? X forwarding? Just use a modern remote desktop solution, all X forwarding was doing in “modern” times (read: the 21st century) was streaming pixels anyway, just less efficiently than modern remote desktop.
I still use X forwarding.
It works just fine using xWayland, and X forwarding has always been so janky there is no chance to notice any difference caused from using xWayland instead of native.It will surely take many years and well established wayland native remote tunneling before anyone thinks of ditching xWayland.
Waypipe has worked very well for me.
It’s nice but a little janky. For me for example I have to hit ctrl+C twice after closing a session where I started a kde program.
Multi window apps are still broken, and the wayland protocol guys have been dragging it for more than two years
Honestly which app do you use that makes use of multi window rendering?
The main one is KiCAD (electronics design).
They have a good article on the challenges they’re facing on Wayland, worth a read https://www.kicad.org/blog/2025/06/KiCad-and-Wayland-Support/
I don’t, but some people like multi window GIMP, and apparetnly several applications in the automotive (kiCAD for example) and scientific field
People who like multi window gimp must be a very special kind of nerd. I used it before single window mode was added, but when it was I never looked back. Positioning each subwindow in a way that didn’t suck was such an absolute pain
ah that was so annoying, and nowadays using tiled windows, that’s something I don’t see myself doing anymore
But that pain was once. And then you shoved that config into your dotfile svn and never did it again. Mine has followed me since like 2010.
(This is not me taking part in the wl/X11 argument. I am just one of those multi-window gimp nerds)
It’s not a pain if you use a tiling WM, and doesn’t KDE remember and restore window positions yet?
alias hc=herbstclient # GIMP # ensure there is a gimp tag hc add gimp hc load gimp ' (split horizontal:0.850000:0 (split horizontal:0.200000:1 (clients vertical:0) (clients grid:0)) (clients vertical:0)) ' # load predefined layout # center all other gimp windows on gimp tag hc rule class=Gimp tag=gimp index=01 pseudotile=on hc rule class=Gimp windowrole~'gimp-(image-window|toolbox|dock)' \ pseudotile=off hc rule class=Gimp windowrole=gimp-toolbox focus=off index=00 hc rule class=Gimp windowrole=gimp-dock focus=off index=1it’s not a pain
Here’s the dozen lines of config I had to write and tweak and debug to make it tolerable
Uh huh. You do you.
Hold on, so I can’t run Transmission that has the torrent list in one window and torrent details in another window? Only one single window per app? What insanity is this.
Every app I know opens a window for the preferences, how is this solved in Wayland? Even just the typical Explorer-style file manager requires multiple windows to function. And of course, I always have a dozen Firefox windows open.
Oh multi-window works, it is mostly just that applications cannot geometrically position them themselves. There are other small issues, but thay is the main one I hear. It is a non-issue for things like settings and Transmission, since you just open another window and do not really care exactly where it os relative to the other ones. It often ends up being on top. For multi-window Gimp it is worse, as it is toolbars and modules, and the app wants to place them precisely relative to one another. This is currently not working in Wayland, but they create new extensions all the time so it is only a matter of time IMO.
Thanks for the explanation. As it happens, one of my irks about the Windows version of Transmission is that it doesn’t remember the position of the torrent-properties window. I want the list on the left, the details on the right — particularly since Transmission reuses the details window, essentially treating it as a pane. This worked splendidly on MacOS.
Yeah. “Feature parity or get out”, like dude we’re long past feature parity.
Ok, replace the xfce/KDE wm with something like i3 and then keybind all of the commands that aren’t wm specific through a global hotkey daemon like sxhkd.
I could never get it to work.
If you’re waiting on Wayland to reimplement the thing that made X11 a monolithic unmaintainable mess, you’ll be stuck on your rotting platform from the 80s for a while.
Having modular DEs is what:
made X11 a monolithic unmaintainable mess
?
https://lxqt-project.org/blog/2025/09/22/2-way-of-wayland/
https://lxqt-project.org/release/2025/11/05/release-lxqt-2-3-0/
I switched to Wayland. I think I have almost everything working except keepassxc’s global hotkey and autotype. Also certain apps like ardour, I have to manually break components off from the main window and move to different monitor to get the “multi monitor” functions going. This I know they have been trying for 2 years now, anyday now.
I can’t copy/paste from a terminal program to a GUI program under wayland without jumping through hoops and configuring every individual program to use some variant of a DE-specific utility that bypass wayland’s model to peek/poke into the clipboard.
That’s not a minor feature to me. And in my (and probably some other people) case, trading basic copy/paste for not-yet-implemented differential DPI scaling does not sound too great.
Some people are adamant to not switch, but I swear some people are so adamant to force everyone else to switch without even considering that their use case might not match other people use case, it’s infuriating. It’s not like me staying on X will degrade everyone else’s experience of the new shiniest thing.
Distribution moving to wayland might be good in the very long term, but for now, when you have a 3080Ti (a relatively recent card) and it breaks basic desktop composition when switching to wayland, telling people “just throw it out and buy another card instead of keeping your currently working system” is not going to help anyone.
What are you talking about? You can copy-paste from Terminal programs to GUI programs and vice-versa like everywhere else (with the terminal of course needing CTRL + SHIFT + C / V, which as we know is historical to Unix terminals). I’m doing that for years, so does my family. It works just fine.
And bringing up Nvidia now really is bending down backwards to paint Wayland as bad while it’s painfully obvious it’s the driver’s fault. We all know the classic Nvidia driver sucks in more ways than one and loves to break, even Nvidia knows that and works on a replacement. That’s not Wayland’s fault.
What are you talking about? You can copy-paste from Terminal programs to GUI programs and vice-versa like everywhere else (with the terminal of course needing CTRL + SHIFT + C / V, which as we know is historical to Unix terminals). I’m doing that for years, so does my family. It works just fine.
I’m not talking about copy/pasting from the terminal emulator, thank you very much. Just run VIM and have it copy/paste from the global clipboard without setting up esoteric, sometimes DE-dependent stuff, and you’ll understand.
And bringing up Nvidia now really is bending down backwards to paint Wayland as bad while it’s painfully obvious it’s the driver’s fault.
Sure. I did not say it was wayland fault. Or anyone else, really. I explained why some people could not “just move on to wayland already you nincompoop” with very tangible issues that still prevent them from doing so. Who is at fault is of no consequence here. If I switch to wayland, I lose features, I have a broken desktop, and throwing away thousands of equipment because “it’s the future” does not sound that great. It’s just a matter of fact. Whether it’s wayland’s fault, plasma’s implementation’s fault, nvidia’s fault, or anyone else’s is irrelevant to the user experience here.
People can’t go “stop using X and use wayland”, and ignore raised issues by saying “no, that issue you’re having is not a big issue”, “that issue you’re having is not wayland’s fault”, “that issue you’re having does not concern most people”, etc. And reading replies in this thread, it seems people have a hard time imagining circumstances beyond their own.
I’ve used this neovim keybind for years:
vim.keymap.set({'n', 'x'}, 'gy', '"+y') -- copy vim.keymap.set({'n', 'x'}, 'gp', '"+p') -- pasteI was able to copy/paste between nvim and other applications on sway, Hyprland, Niri and KDE on Wayland.
The global clipboard register + should also work in modern regular vim afaik.
Thats not entirely true.
wl-copyexists and I use it, but it’s not fully there yet. Things like slackadays/clipboard are still fucking around with weird Wayland issues.I’d like better clipboard support, but
alias c=wl-copyis good enough most of the time for me. And it works in neovim as well.Yeah, I know of such “solution”. But what is the point of forcing the change when it doesn’t bring me tangible benefits, brings significant downsides, and only some of these downsides have half-useful workarounds?
I have no problem with whether wayland existing or it becoming the new standard, but forcing people to move in these circumstances seems a bit silly, especially when some issues stem from people having hardware from one manufacturer that represents around 75% of general consumer systems (according to Steam survey, which might or might not be representative but sure brings a lot of people).
Thankfully, at least with the distributions I use, switching back and forth is trivial. But given the circumstances, I don’t really understand the extremely heavy push.
I don’t think anyone’s forcing anyone to do anything. But not a lot of people are stepping to to maintain X
While it’s certainly winded down over time, XOrg is still maintained. Last fix was released in september 2025. Is it enough? It never is. But that’s not really an argument to move from “working” to “not working as well” for now.
I thought most of the maintenance went towards Xwayland, though I don’t follow it that closely
It mostly did, yes. But when a big issue pops up, X still gets the occasional patch.
And, since this is a bit of a hot topic it seems, that sounds fair to me. X is the past, wayland is the future. I’m just annoyed at people glossing over the reasons not everyone can move on.
