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)?
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.
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.
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.
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?
Yea and a strangely (to me) large proportion of people seem vehemently opposed to apps even asking to collect usage data, which is incredibly helpful for developers, putting aside the more controversial things like privacy/marketing uses of the data.
Personally I don't believe for one second that Wayland has actually surpassed the install base of X11-like display servers.
Depends on how you measure it. A lot of IoT and wearables run Wayland, for instance (Tizen, Steam Deck, a bunch of specialised IoT stuff). Also don't forget the millions of Chromebook running Wayland on top of Linux. With my watch, my Deck, and my laptop running Wayland versus my desktop running X11, I live in a Wayland household.
I'm not sure what the general user is running, I would say X11 as well, mostly because a lot of Linux users have Nvidia hardware and Nvidia's crapper drivers still struggle with Wayland. I think it'll be a few years before you could say that the majority of people who know what Linux is, are on Wayland
Yeh, I'll wait until the bugs are ironed out and my distro (mint) determines it's stable. No need to start asking for troubles when everything is working smoothly.
What about PRIME, though? I'd like to give it a shot, but I only just ironed out my setup with triple-gpu(all different vendors) and a ton of sweat, I'm afraid it's going to be back to square one with wayland.
Same. I don't see why people need to argue about it or make a conscious decision about it anyway.
(My distro determined it was ready to use a while ago, so I've been switched over for a long time now. Indeed it's working fine, and I think I hardly even notice the difference.)
Same I want to move over so bad. It's so smooth and the animations feel much nicer but there is always a deal breaker issue that sends me back to x11 within a few hours.
Given that it requires self-reporting from the command line, I feel like the people that are more likely to be on the cutting edge may be more likely to report as well
I doubt it's representative of the population. Because it's from self reporting, at best it's representative of those who advocate their favourite platform, which is just a particular portion of the population. Though it would be cool to see Wayland surpass X
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?
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.
Would love to know how you're dealing with Gnome and HiDPI. I found it really wacky, massive title bars and such. Went to KDE Plasma 6 and it all looks right, but agree it seems a little wonky sometimes. I'm hoping the bugs get ironed out.
I wonder how representative that is of actual software used. I would imagine hardware probes are run from installers and live systems quite frequently. I would certainly not expect several percentage points of "neither" in practical settings.
Yeah, but when was the last time you decided to upload hardware device data for a root server to some hardware survey? That is something almost exclusively done by the kind of people who want to show off their system in some way.
I would guess not very representative at all. I don't believe wayland usage is higher, like at all. Maybe in a limited setting like NEW installs of the most popular distros, just because they default to it. But the existing install base? No way.
This is a graph of recent reports (one year time frame). The total reports from all time are over 70% X11.
But since the statistics are based on one time uploads, there's no way to know how many of those systems are still in use, or still run X11.
@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 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.
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.
Wayland has a mouse capture bug in proton / wine. It particularly seems to be an issue in FPS games. That may contributing to slower adoption for Linux gamers.
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.
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.
Same here. With the exception of the explicit sync, which will hopefully be resolved this week, I have been running Plasma 6 wayland since February. And honestly when I tried the X11 version it had more issues.
That's great for you. But it also has tons of problems with a lot of other users. Including issues with proprietary drivers, XWayland compat for many apps/games, screen tearing, multi-monitor setups (esp. with different aspect ratios and/or dpi scaling factors), VRR, HDR, rotation, color management, many accessibility features etc.
Bought a brand new machine. Top of the line. Installed windows on it. Thought "You know what, fuck this, time to give Linux another go". Discovered that nvida and Wayland don't get on...
Linux is becoming more and more popular on the desktop because it is now well suited for gaming. In addition to Proton, you also have to consider all the handhelds like SteamDeck. Valve certainly doesn't want an Nvidia product with crumbling proprietary drivers. With AMD, Nvidia could see that there is a market for it and has now established itself. It was only logical that Nvidia would not stand still. They will do everything to dominate the market as well.
nvidia works better for me on Linux than both nvidia/amd on windows. I know not everyone's experience is the same, but it's at least not universally bad in case you were trying to say that.
Which nvidia drivers work with Wayland? I have one pc that only has 470 supported card, l guess all hopes are lost there..
But my 980 gtx machine seems to work mostly on wayland, except somehow minecraft only works on Xorg
To temper your expectations you'll likely have some problems. But you'll have the ability in future to make use of new display technologies, like VRR and HDR
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.
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
I just set up xmonad because I was in the mood for change. Took about a week of tinkering a bit each day and I really like it. Afterwards, I was still in the mood for configs and looked at Wayland. There isn't much progress on Wayland xmonad, so guess that has to wait.
That's a common problem I've been hearing for almost 10 now - the software support isn't quite there yet.
I've never used xmonad but it looks like a generic tiling window manager based on a quick Google. There are tons of those for Wayland, with Sway and Hyprland seemingly leading the charge.
I don't think xmonad has the development power or the interest to rewrite their X11 window manager into a Wayland compositor. That doesn't mean there aren't any replacements that have been designed from the ground up to work with Wayland, though.
The main draw of xmonad is that you can modify pretty much everything, as the config itself is a Haskell file (the entire thing is written in Haskell). There are tonnes of modules to use, you can define your own window layouts and add whatever functions you can dream off - I haven't seen any other window manager offer this kind of freedom (with the added joy of learning Haskell!).
As for the second point, about half a year ago, they started doing exactly this. Rewriting xmonad for Wayland. Guess I'll sit this one out.
The default "gaming mode" that the Deck boots into is running wayland, specifically valve's own gamescope compositor which has a lot of workarounds and breaks from wayland's spec to allow for better gaming performance.
When you quit out to "desktop mode" it loads into KDE Plasma with X11, although with recent changes to Plasma, it may well be that the desktop mode will change to being wayland based too.
And people who intentionally use the thing that isn't quite ready are more likely to do that self reporting than someone who installed Mint years ago and dgaf. Just saying, these numbers are meaningless.
Yeah, I agree that most are on X11 still. That said, by this time next year and probably by the end of the year once explicit sync has landed in most packages of relevance, most distros that do annual releases will switch the default to wayland on all hardware.
A lot of hardware has nvidia gpus and wayland is finally pretty stable on both of the 2 major DEs. A lot of work in the last couple years by DEs, toolkits and the wayland protocol has moved the needle quite a bit.
I disagree. Ubuntu has used Wayland as default since 22.04, and it's the most used distro out there.
Debian Stable is on Wayland by default. So is Fedora, OpenSUSE, and Arch if you install one of the big DE's (which have a combined usage share of over 80%).
Actually most distros with Gnome or KDE will boot into a wayland session by default.
Mint is the only big one still on X11.
Are you sure? I'd actually say the opposite. The types of people who install Ubuntu, Debian, have Chromebooks, etc (which are on Wayland) won't have replied to this survey because they install and forget, but the people who like to rice their systems, use TWMs, etc and have strong opinions on Wayland/SystemD/Flatpaks etc are more likely to reply to this
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
It is possible, although unlikely, that it is the display server for WebOS, the OS Palm built and LG bought. I seem to recall them having their own display server.
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.
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.