- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Source: https://linux-hardware.org/?view=os_display_server
Reporting is done by users who voluntarily upload their system specs via
# hw-probe -all -upload
Reporting is done by users who voluntarily upload their system specs via
# hw-probe -all -upload
So not skewed at all…
Why would it be skewed? What would be the cause for a subset of linux users, that upload hardware probes with extraneous information about their display server, to skew the extraneous data?
Because a huge portion of the people willing to do this are already on Wayland, but I believe there exists an even larger percentage on X that are not submitting any data.
And another commenter said:
We’re just left to do armchair psychology about the type of people who would submit data to this site. So the numbers are effectively useless.
Because a huge portion of the people willing to do this are already on Wayland, but I believe there exists an even larger percentage on X that are not submitting any data.
What is the basis for that assumption?
And another commenter said:
We’re just left to do armchair psychology about the type of people who would submit data to this site. So the numbers are effectively useless.
So because one cannot know which type of people submit data to the site it should be disregarded? That’s basically saying any poll or questionnaire with anonymous yet unique answers are invalid. That’s a pretty bad argument.
So because one cannot know which type of people submit data to the site it should be disregarded? That’s basically saying any poll or questionnaire with anonymous yet unique answers are invalid. That’s a pretty bad argument.
This is basically a survey or poll. You want people to provide you with data about what they’re running. To get an accurate view of the entire population you need a representative and randomized sample. If you’re relying entirely on self-reported data you’re not going to be getting a reliably randomized subset of people. You’ll get people who are motivated to report their usage to a third party. That can lead to persistent biases in the data.
It may be that Wayland use is being under represented because the people reporting want to show that “X11 is still king!” Or it could be that this website is shared frequently with certain user groups (e.g. in some arch (btw) forum or something) and so you’re getting a skew towards that population and away from the whole.
We don’t know who these users are and we can’t “offset” for those factors. And the data isn’t reliably randomized so it’s subject to those biases whether we know about them or not.
Though as another person pointed out the trend itself may be of some interest if the population being polled is consistent. Though I doubt anybody suspected that Wayland use is NOT increasing?
Anonymous polls are indeed useless for several reasons.
Man I spent 4 paragraphs saying what you just said in one sentence. 😅
by default, your content is all rights reserved, the most restrictive license possible. AI trains on “all rights reserved” content all the time. You really think adding a CC-BY-NC is gonna do anything?
I just did that, why not, but it misreported my DE anyway, so I’d take the OP post with quite a grain of salt.
err, why? actually it can be skewed against wayland(wayland users tend to be more security aware), and why the suprise, KDE, GNOME are wayland from the get go, steam deck too, hyprland and sway etc
It can skew either way equally. We’re just left to do armchair psychology about the type of people who would submit data to this site. So the numbers are effectively useless.
fair
But the change in the numbers is not useless since the psychology of the Wayland users vs. x11 didn’t change
That seems probable but was there any doubt that Wayland use is increasing? Wayland has been changing to the default distro by distro. The only reason this is “news” is because somebody has claimed that “Wayland usage has overtaken X11”.
You’re discounting the trend here. Assuming the methodology is consistent, over a short time we’re seeing a noticeable change, bias or not.
I’m not actually. Does anybody doubt that wayland use is increasing? Distros have increasingly been making it the default. I’d be surprised if use weren’t increasing. In fact it might be under-represented in this data depending on whether all distros are being accurately represented or not.
Wait Steam Deck now runs Desktop mode in Wayland?
plasma do, unless valve changed that
On launch Steam Deck had it’s desktop/Plasma session set to X11, hence my question
yep, plasma was still x11 from default when steam deck launched, plasma 6 switched to wayland as default, now i don’t know if steam deck was updated to plasma 6
Do you have a better way of measuring it?
In what direction would voluntary self-reporting of all system specs skew the display server statistic (and why)?Do you have a better way of measuring it?
No better way of measuring doesn’t mean this is a good way of measuring.
What way do you imagine would be more precise?
A method that attempts to collect data from a randomized or representative population rather than relying on self-report.
The fact that you need consent to get this data would make a randomized approach impossible.
Could always go for opt-out instead opt-in metrics. Fedora had some recent controversy with it.
deleted by creator
Yes. It just may be possible that accurate poll data on such things isn’t possible.
Steam hardware survey but that will skew towards gamers. That said, it would be a good indicator on how compatible Wayland is.
Yeah, this is pretty textbook selection bias.
What way do you imagine would be more precise?
Unavoidable analytics, apparently. Yay?
Well do you want useful stats or not /s
But seriously, a lot of opt-in (that never get opted in to) data is insanely useful for developers, but it has such a bad stigma that we never get anywhere close to the amount of usefulness a larger dataset could provide.
Tbf a lot of that stigma has to do with trust violation.
I like the way kde does it. On first install it gives a slider with how much analytics you want to send. I just do all of it because I trust KDE, but it’s nice that it asks you. They probably have some pretty good data.
This is the important point IMHO. This kind of feedback is exactly something I’d love to do, but I don’t think I had any idea about it before this post. Just a little popup on a new install/upgrade would be a much broader net.
I imagine people who care about this sort of thing are more likely to report it. And people who care about this sort of thing are also more likely to be early adopters and go through the effort of switching to Wayland.
The way to get a more random sample is not something I want (built-in, automatic telemetry by default). So I’m fine with having skewed data for something like this.
Its a pretty good survey and has a good sample size. Statistics is hard. I won’t take the criticism too seriously.
Anyone who needs accessibility is screwed as Wayland takes over. Let’s hope we can still choose for another say 40 years. Then, I’ll be done, and Wayland can rule. Pity those who will still need accessibility options though.
How so?
In X11, any application can control any window. That makes screen readers and other accessibility tools very easy to write.
In Wayland, applications can only control their own stuff (no injecting
sudo rm -rf / --no-preserve-root
through keystrokes right after you hit enter on asudo
command in your terminal!). Screen recording access is only granted on request. A lot of applications written for the “anything goes, permissions are an illusion” style X11 has, will be difficult to port to Wayland.Windows had a similar problem when Vista introduced integrity levels (even non-admin users can have several levels of privileges, and windows can’t interact with higher privilege levels by default) leading to a lot of these tools running as admin, even under modern Windows.
Wayland and X11 have a more involved accessibility tree, but not every accessibility application uses that, and not every application exposes the necessary info. Synthetic clicks (i.e. interactive screen reader support) support is limited by design, as are global keyboard shortcuts.
Accessibility tools on Linux are already pretty mediocre compared to macOS or iOS or Android or Windows, but on Wayland it’s even worse.
Ah ok. Thank you for the detailed answer.
I really don’t get the whole Wayland vs X11 thing. X11 works fine, why crate an alternative? What’s so great about Wayland that can’t be implemented in X11?
Wayland is architexturally better than X11. X11 was developed in a time where any serious application more powerfully than a terminal emulator would be running on another computer, and everything else has been hacked on top of that. There’s hardly any security restrictions for things like keyloggers and key stroke injection. It’s old and maintenance sucks for the people currently maintaining it.
After a couple of decades, people looked at what the rest was doing and thought perhaps the old mainframe model isn’t necessary anymore. Windows and macros don’t model their GUI after mainframes with dumb terminals that happen to be physically located within the same machine, so X stands alone in its design architecture.
I think everyone maintaining graphics code for Linux distros thinks X11 doesn’t cut it anymore. Importantly, the people writing GPU drivers don’t seem to want to be held back by the extensions built on top of X11 (while others dutifully maintain their old drivers). This is work only the companies making GPUs can afford, without it, the drivers will stop working. There’s probably also a reason Android took the Linux kernel but stripped it of X11 acceleration and developed its own GUI stack. Canonical tried to get rid of X years ago by developing Mir and a bunch of small projects tried to create an X12 of sorts, but neither took off. Almost everyone is now working on Wayland when it comes to alternatives.
There are people who don’t care. Some GUIs will always be X11 and they can use X11 as long as the drivers and tooling still support it. Most X11 programs have worked without modification for years through XWayland, and I expect future applications to still work fine through some kind of reverse that’ll turn Wayland programs into X11 programs.
Thank you for the great explanation. I haven’t been keeping tabs on this subject so I’m a bit ignorant about the limitations of X11 advantages of Wayland.
For me X11 just worked and I was happy with that. I want aware of the security issues either.
The problem is, X11 doesn’t really work fine for modern usage.
It kinda falls apart with multiple monitors, especially when they require different scaling or refresh rates (or both), HDR support would be incredibly difficult to add, it’s buggy, it’s virtually impossible to maintain or add features. Often fixing a bug breaks things, because the bugs in it are so old that programs have actually been designed around them, or even to utilise them.
Now imagine trying to adapt X for use with VR/AR displays and all the differences in window management that’ll be required for that.
It’s a security nightmare. Any app can see what any other app is doing. That means that if you have a nefarious app, it can scrape any information on your screen, without even needing root privileges. Then there’s a load of other vulnerabilities.
The developers have moved to Wayland because X is structurally unfixable.
GNOME is working on a new Accessibility Toolkit for all desktops, funded by the $1M from STF. It’s intended to make accessibility better on Wayland.
Watch thisweek.gnome.org for updates on accessibility; there’s usually one. Here’s a very recent article about how it’s going from LWN: https://lwn.net/Articles/971541/
“At this point, some of you might be thinking ‘show me the code’”, he said. The audience murmured its agreement. Rather than linking to all of the repositories, he provided links to the prototypes for Orca and GTK AccessKit integration. Campbell said these would be the best way to start exploring the stack.
If all goes well, Newton would not merely provide a better version of existing functionality, it would open up new possibilities. Campbell was running out of time, but he quickly described scenarios of allowing accessible remote-desktop sessions even when the remote machine had no assistive technologies running. He also said it might be possible to provide accessible screenshots and screencasts using Newton, because the accessibility trees could just be bundled with the image or pushed along with the screencast.
The conclusion, he said, was that the project could provide “the overhaul that I think that accessibility in free desktop environments has needed for a little while now”. Even more, “we can advance the state-of-the-art not just compared to what we already have in free desktops like GNOME”, but even compared to proprietary platforms.
He gave thanks to the Sovereign Tech Fund for funding his work through GNOME, and to the GNOME Foundation for coordinating the work.
There was not much time for questions, but I managed to sneak one in to ask about the timeline for this work to be available to users. Campbell said that he was unsure, but it was unlikely it would be ready in time for GNOME 47 later this year. It might be ready in time for GNOME 48, but “I can’t make any promises”. He pointed out that his current contract ends in June, and plans to make as much progress as possible before it ends. Beyond that, “we’ll see what happens”.
deleted by creator
My understanding is that AccessKit is an entirely separate thing to the portal.
Unfortunately, for several things, your choices are X, which is broken by design and few developers QA their software for anymore, or Wayland, which works pretty well in many areas, but where several important (or even basic) features are quagmired by bike shedding. But things are improving really quickly, and part of that is everyone shifting focus to Wayland.
I recently tried to navigate my GNOME desktop via screen reader and did not enjoy the experience. If I ever need it, I hope it works properly by that point…
At least for me, X is a worse experience on every computer I own (including the NVIDIA one), which is why I use Wayland. Neither is problem-free. I’m fortunate enough not to depend on accessibility features; perhaps my opinion would be different then.
This is exactly the problem I meant. Thank you for such a detailed overview of the issue. Most apps won’t provide for it, and as you described why technically, it will mean the end of accessibility as a system whole.
I doubt it’ll be the end of accessibility. There’s a very active issue on Github about an accessibility portal to fix Wayland’s shortcomings for accessibility. I expect the problem to be that very few people work on accessibility tooling, so even if the standard is finished tomorrow, it can take years for tooling to catch up.
I expect the Gnome/KDE tools to work on Gnome and KDE first, and then generic tools to work later. Or maybe the tooling Google has built into ChromeOS will be ported over, as Chromebooks are running on Wayland as well, who knows!
Luckily, X11 is going nowhere for the coming years. There are still people running system-v on bleeding edge Arch installs. Linux has a very long half time when it comes to software support. If you install Ubuntu 24.04 with X11 today, you’ll be able to keep using the current accessibility toolset until 2034 at least.
Are you serious? Every sane desktop is working on accessibility. I recently heard from System76 that they’re putting in the effort for COSMIC, we have GNOME focusing a portion of that €1 million they got from Germany, on accessibility (last I heard, they’re working on cross-desktop solutions). Now, I don’t remember hearing much from Plasma on accessibility, but I think it’s fair to assume they’re also working on it.
User skullgiver provides an excellent answer as to why. It’s a shame, but it’s a reality that most apps won’t expose themselves properly, and hence accessibility is over in Wayland. Despite their excellent efforts.
who is using linux through their web browser
Users of ESXI, 3CX, Univention and Nextcloud
would that show up as their display server though? surely VMWare et al run some other display server on the backend and then stream to clients via VNC?
No, that’s why the web frontend graph is at 0%.
And those systems don’t have a display server, they open up a web server to interact with.if the graph is really at 0%, and not 0.0001%, why’s it there at all?
also, i’m really confused as to why an HTML webui would qualify as a display server.
deleted by creator
I switched to Wayland the moment my distro went moved to KDE Plasma 6 because according to my logic: if things are going to be broken and I’m going to adjust to them anyways, I might as well do it all at once: shock therapy style.
Plasma 6 broke a lot of my desktop customization, but that is to be expected. And Wayland? It has been surprisingly okay. I am experiencing some keyboard-related problems that I can’t even begin to track down (sometimes the keyboard flat out refuses to work for certain programs, sometimes it’s the numpad). However, I am not sure if it’s really related to Wayland, so I’m withholding judgement.
How are you enjoying EndeavourOS?
… I actually use Arch. Sorry.
But really, I would have gone with EndeavourOS (instead of Arch) if it were not for my friend who really strongly advocated for Arch (even installing it for me—or rather, converting my Manjaro install into an Arch one).
If I’ve had any regrets in my Linux journey, it’s choosing Manjaro instead of EndeavourOS as my introduction to Arch-based distros.
… I actually use Arch. BTW.
FTFY
Arch people REALLY hate Manjaro
-happy Manjaro user
And in my case, I kinda don’t like Endeavour OS. I installed it on my laptop to try it out a couple months ago. It looked to me like a convenient no nonsense installer for Arch with some nice defaults, then you stumble on their custom update/mirror manager nonsense. Then you want to use a printer and realize they left CUPS disabled, as if to give you an “excuse” to use systemctl. Then if you want to use Samba, you need to go out of your way to find a default config file. I’ve had to jump through more hoops and dealt with more quirky nonsense than with Manjaro stable on that distro.
It’s like it doesn’t know who this is meant for. People who want their hand held through a GUI for something basic as updating their system, or people who love writing their own config file for everything.
Might as well install Arch, really.
-Other happy Manjaro user
Exactly! That is my neverending conundrum with people going for Endeavour.
Like, why not Arch at this point?
Thanks for your voice!
I would rather have arco over endeavour.
Same
But Manjaro is king
deleted by creator
I just switched to Endeavour from Manjaro when I upgraded my hardware, and every update changes the default kernel on the selection screen. I go in and edit the file to change the default from lts to the latest kernel, and the next update switches it right back. It’s maddening, i could do Arch, and I’ve done it on other machines I just don’t have the time for that level of customization. I already waste enough time tinkering.
I just installed EOS a couple of minutes ago and realized what you are saying.
So, during install, you did not click on the box that says “firewall” ( selected by default ) and you did not click on the box that says “Printing support” ( not selected by default ). To you, that means that EOS does not know who it is targeting?
These seem like sensible defaults. Regular users should use a firewall. Many systems will not connect to a printer.
Clicking clearly presented checkboxes ( or leaving them as default ) at the point the installer asks you to seems pretty friendly. It is certainly a lot more friendly than having to know what pacman -S is and whatever the hell CUPS is ( I know what it is but “printing” seems a bit more newb friendly ).
Not setting stuff up at install time and then complaining that it is not installed the way you want seems….”odd”. Also, the SAMBA packages for EOS come from the Arch repos. The experience adding packages post install is literally identical between the two distros.
This is not a very compelling indictment of EOS.
I’m sure EndeavourOS is perfectly fine for the people who work on it and their core user base. That’s not my issue. It’s still happily running on my laptop. I just keep on seeing people say “Don’t use Manjaro, use EndevourOS! It’s much better.” But your average computer user would lose their shit at having to deal with those ^ issues. “You just had to enable it at installation if you wanted printing. You didn’t see the checkbox?! Oh mah gaaa” …Seriously? It’s not a checkbox to turn it back on if you miss it and should be opt-out to begin with. Are you going to tell me CUPs is a significant memory/storage drain and a gaping vulnerability in a residential network? If one’s not familiar with Linux, CUPS, pacman and Systemd it’s a huge headache for most people to get this working.
I just think that EndeavourOS shouldn’t be presented as a Manjaro alternative for your average person, when it’s an opinionated Arch-based distro with spotty defaults aimed at somewhat experienced Linux users that want nitty-gritty control over their system. (Users which, again, might as well be using vanilla Arch if that’s fun or important to them) And it has some weird update/mirror manager that prevented me from just using pacman to update my system at one point and I had to figure out whatever it was they wanted me to use. Never had this kind of crap happen to me in Manjaro. Nor was printing disabled by default. Nor were network shares hard to get working.
How does Garuda fit on the Arch spectrum?
Kinda hated, but not as much as Manjaro.
Manjaro guy’s perspective - nicer than Endeavour, at least there is some functionality that is actually useful and justifies it being a separate distro.
Normally, Arch folks hate Chaotic-AUR as part of Garuda, the bloat™, and the fact it’s heavily designed with hypergaming styling, which is not only not pleasing for many, but adds extra hurdles on the way to ricing.
Yeah, I’m sorry. I’m biased against it, thanks to my experience with it.
Swing and a miss! Well, I can take solace in the fact that 99.9% of the packages you are using are in EndeavourOS too. So, I was mostly right. :)
I also wish we could replace Manjaro with a green themed EndeavourOS. So many people could be saved the pain. Manjaro is the next biggest Linux honeypot after OpenOffice ( which exists only to ruin the experience for people that should have used LibreOffice instead ).
Converting Manjaro to Arch in place is a labour of love. I have done it myself and it is was more steps than I expected it to be. Worth it though. Good friend.
Well, I can take solace in the fact that 99.9% of the packages you are using are in EndeavourOS too. So, I was mostly right. :)
Yeah, also I think EndeavourOS and Arch moved to Plasma 6 at around the same time too? I tried holding off the update to Plasma 6 for a few days but finally took the update on March 12.
I also wish we could replace Manjaro with a green themed EndeavourOS. Manjaro is the next biggest Linux honeypot after OpenOffice.
I think with enough faffing around customizing things in KDE Plasma, I think a green-themed EndeavourOS is doable. Would I recommend it? Not really, lol! From what I’ve seen, I like EndeavourOS’ default theming.
It’s just a shame EndeavourOS isn’t as known as Manjaro (at least during the time I first jumped into running Linux as a daily driver). But then again, with Manjaro shitting the bed becoming more known, I hope EndeavorOS can take the place of Manjaro as the Arch-based distro for newbies.
Converting Manjaro to Arch in place is a labour of love. I have done it myself and it is was more steps than I expected it to be. Worth it though. Good friend.
Oh yeah, I was there with him when he was doing it. I can’t do any help other than cheering him on, and to have another eye on the screen making sure he doesn’t make any stupid mistakes in the process. At few points, I reminded him of the fact that I’ve backed up my files, and if things really get FUBAR, we can just do a clean install and restore the files from backup.
EOS uses the Arch repos. So, EOS and Arch got KDE 6 together since whatever is in the Arch repos hits them both at the same time.
If Manjaro doesn’t work for you, doesn’t mean it doesn’t work for everybody
Leave our sacred amazing green Manjaro alone!
EndeavourOS is crap btw
And LibreOffice has terrible UI, even if it’s feature-rich. Onlyoffice is the way to go
Alright, enough unpopular opinions for today.
Once installed, EndeavourOS is literally just Arch except for perhaps a couple of optional utilities and some theming. Even the kernel is the same. So you think Arch is crap btw?
More recent EOS installs do use Dracut. So, I guess there is one difference now ( unless you use dracut on Arch ).
I do not mind the look of Manjaro. That is not my issue with it.
I am fine with OnlyOffice as well. It is OpenOffice that nobody should use ( it is literally just an ancient version of LibreOffice at this point ).
So, other than saying Arch is crap, none of your opinions from that post are unpopular with me.
Yeah, dracut and some small differences here and there just make it more complicated to no gain, and I just don’t comprehend why would someone who installs Endeavour wouldn’t just install Arch and not depend on some random distribution that does little beyond easy set up (which has recently been shown as problematic when Endeavour team dropped ARM support).
Arch is alright btw. It has its audience, and it serves them well. Besides, it’s an independent, but highly popular distro, which I value. It’s snappy, configurable, well-documented, and no-fuss.
Besides, it would be weird to use Manjaro and hate its upstream. Though Mint people can experience such vibes…
I have been pretty happy with Dracut and have moved a few other systems to it. I used the instructions in the Arch wiki for how to do that of course. Dracut ( even in EOS ) comes from the Arch repos. Takes a couple minutes.
EOS only moved to Dracut recently so only my newest system would be using it ( rolling updates do not change that kind of thing ). I have all my systems using it now though, including “real” Arch.
I am less enthusiastic about systemd-boot though it does seem faster. It is just part of my bias against systemd.
Regardless, I could certainly move any of my systems to whatever I want. Installing EOS and then migrating away from Dracut would be faster than installing Arch to begin with. Of course, just starting with EOS Galileo ( before the move to Dracut ) works just as well. A simple pacman -Syu brings you to the same place as a newer install.
Honestly, uninstalling eos-hooks from EOS to get Arch is faster than installing yay in Arch to get the AUR ( yay and paru are both in EOS by default ).
I tried switching to Wayland on Mint, it did not go well. Unfortunately I do not care to follow an hour long guide to figure out how to get it to run games properly.
Mint Wayland support is experimental and was released in Mint 21.3 ~3 months ago
The Wayland session isn’t as stable as the default (X11) one. It lacks features and it comes with its own limitations.
It was added as a preview for people interested in Wayland and as an easy way for them to test if they want to give us feedback.
A board was set up to keep track of Wayland development. It’s available at https://trello.com/b/HHs01Pab/cinnamon-wayland.
A dedicated Github repository was created for issues related to Wayland, whether they need fixing in Cinnamon, in an XApp project, a Mint tool or anything software project we maintain: https://github.com/linuxmint/wayland.
In terms of timing Wayland support doesn’t need to be fully ready (i.e. to be a better Cinnamon option for most people) before 2026 (Mint 23.x). That leaves us 2 years to identify and to fix all the issues. It’s something we’ll continue to work on and improve release after release.
These days the unique use case X was designed for is very, very niche. For everyone else, Wayland is the way to go.
Voluntarily uploaded data? This feels like that old linux user count site.
I will run that probe on my machines to contribute, though.
For completeness, we should review the involuntarily uploaded data as well.
Don’t forget the voluntarily not uploaded data! That can’t be left out.
Is this because of me?
Finally, it’s the year of the other desktop!
Glad to see it finally happening. Wayland has been an amazing experience for several years
Crazyy!
Btw I am XWayland free since today!
I have a list of recommended apps here
Some apps need environment variables:
Qt:
- qpwgraph
GTK
- GPU Screen recorder, I guess
Electron
- Nextcloud Flatpak
- MullvadVPN RPM
- Signal Flatpak
- (Element, I switched to the Webapp in Librewolf)
- Freetube Flatpak
You can use
xlsclients -l
to detect apps using XWayland.Some may even want to run apps through XWayland on purpose, like KeepassXC for Clipboard access or autotype. Lets see how long it takes to implement all the needed protocols.
/circlejerk
flatpak bad lmao
Flatpak saved my ass when I super broke my Arch upgrade but didn’t have time to fix it before work. I ran using only Flatpak apps for like 6 weeks because they were the only thing that worked
Decent use case. You do use snapshots now, right?
Trying to set up snapshots is what broke my system. Not sure what the issue was exactly, but BTRFS was reporting a different amount of used space than there actually was, and my snapshots started recursively backing up until everything died
Next time I install Linux I’m going to use Ext4 and snapshots out the gate
That’s weird. I’ve had zero issues with BTRFS and I have both compression and snapshots.
Have you looked at bcachefs, by the way?
Honestly, I’m kind of tired of complicated stuff. I just want a fs that works and is easy to do recovery operations on when it doesn’t work. My SSD is big enough
Yeah. I’m hoping bcachefs ends up being good.
Funny. True, on superstable but also super unstable systems, having separated apps makes most sense.
Not actually on “immutable” rpm-ostree systems, as these have the best and most solid package management.
So actually when people say “these immutable systems, you just use Flatpaks”, actually on the regular systems you should mainly use Flatpaks.
Let me know when wine finally gets ported to Wayland!
I’ll just wait for the official version to finish porting to Wayland. Nothing against the three guys working on this version. I’m sure they’re good people.
True, if I use bottles Flatpak as a GTK wayland app, the actual apps still use XWayland.
Not using any Wine apps though.
Yeah, games are the big reason I jumped ship and I’m pretty excited about the ongoing work porting Wine to Wayland. I’m also too broke to upgrade from my Nvidia card so the efforts improving Nvidia on Wayland are greatly appreciated.
Gotta save up for an education somehow.😄
Yes, “just buy new hardware” is not a solution.
But dont let some news fool ya. NVIDIA already won the AI race, so their “new open source driver” will only benefit their newly sold products
Yeah, thankfully I’ve got a turing card (2000 +)which is said to be the cutoff for the open source drivers.
Waiting for explicit sync support from nvidia but even then, I doubt I’ll switch until I can enable tearing. I’m sensitive to input latency and playing on wayland feels like my aim is floating
I’m sure Nvidia will become stable on wayland by the time xfce also migrates lol
NVIDIA is likely to be stable on Wayland next month. If you wait for other people to ship you code, it will arrive with the fall releases ( eg. Ubuntu 24.10 ).
Xfce is targeting 4.20 for full Wayland support. If you use Xfce 4.20 on kernel 6.9, you may break the Internet.
Nice.
He said the numbers.
Don’t let your memes be dreams
Bc if you had meme dreams they would be nightmares?
NVIDIA is likely to be stable on Wayland next month.
Do you have a source for that?
Not digging them all up but this is the next article up for me: https://www.phoronix.com/news/XWayland-24.1-Released
Thanks for the link :)
Pretty much all the Xfce4 apps support Wayland. We just need Xfce4 panel and the desktop.
@KISSmyOSFeddit
Hw-probe is a nice project. To buy my laptop I created an usb bootable linux that auto connectet my mobile hotspot and uploaded the report.
I went to som shops and usbbooted their devices.
Most shops had no problem with that.
So I found a working convertable laptop. 👍What’s sad ont this linux-hardware.org website is the poor desin of this homepage.
It is really not usable, except for your own device. But also there its difficult to analyse for certain hardware details.I’m quite surprised they actually allowed to stick unknown USB into computer they will be selling to their customers 😮
As someone who switched to wayland way back when sway was dominant…? About time.