14 ms·

> KDE Linux is Wayland-only; there is no X.org session and no plan to add one. Does this mean they're testing that all the Wayland bugs are fixed? I haven't up

by o11c 1y ago

> KDE Linux is Wayland-only; there is no X.org session and no plan to add one. Does this mean they're testing that all the Wayland bugs are fixed? I haven't updated to the new Debian stable quite yet but all the previous times I've switch to Wayland under promises of "it's working now" I've been burned; hopefully dogfood helps.

jacobsenscott 1y ago
Wayland works great for me. I use a rolling update distribution so everything is the latest version and I only use Firefox, a terminal, and emacs. Debian tends to be pretty far behind.
alabhyajindal 1y ago
When was the last time you tried Wayland? I switched to KDE Plasma a couple years ago not knowing anything about display server protocols and haven't had a single issue.
- o11c 1y ago
  The last time I tried it extensively was on Debian Bookwork (12.1 and later; I always wait for the first point release), released July 2023 but freezing sometime around February 2023. Yes, this was a while ago now. But just as now, people said then "all the bugs are fixed and missing features added"; all that really means is "we're in the long tail". I might've put up with it if not for the fact that there were 2ish major bugs that directly affected my main workflow (e.g. temporarily swapping to non-Latin text input).
- dboon 1y ago
  Same experience. I switched back to Linux a few months ago after a few years hiatus. Installed Arch and KDE Plasma. Literally didn’t even know I was using Wayland until I had to fiddle with something and realized X wasn’t even installed
zdragnar 1y ago
I think "most" are fixed. I use quotes because I've seen people say they have issues that I have never run into myself. I'm currently stuck on Windows for some old school .NET work, but otherwise have been running Wayland on either arch or fedora for 8 or so years, no real problems specific to Wayland. With that said, I've also always had X to fall back to for the odd program that absolutely only worked in an X session. At this point, though, I don't even recall what they were (probably something that didn't like running under Swaywm because wlroots), so even that might not be an issue.
Almondsetat 1y ago
Are all X11 bugs fixed?
- o11c 1y ago
  I haven't hit any for probably a decade now. Bugs in the window manager or shell (both shipped by KDE) are somewhat more common, but even if they are crashes, due to X11 being better-designed for isolated faults they are easily recovered-from without loss of session.
  - jsheard 1y ago
    X11 not supporting modern display technologies is arguably a bug, and it's not likely to get resolved at this point (e.g. it can't do mixed DPIs, or VRR with multiple displays, or HDR in general).
    - o11c 1y ago
      I don't care about any of those things, since computers are about productivity for me. But I'm pretty sure at least half of them actually do work under X11, it's just that some UI libraries refuse to use it on the grounds of "X11 is outdated, I won't support features even though it does". (also, having played around with DPI stuff on Wayland, it's pretty broken there in practice)
      - whatevaa 1y ago
        Well and others do care, and no, bunch of stuff straight up doesn't work on Xorg, or is jank fest.
        superkuh 1y ago
        Yep. I feel the same about all the various wayland compositors. Even 15 years on none of them have managed to implement accessibility support for existing linux applications. No screen readers support on any but GNOME's compositor and that doesn't work with existing applications; GNOME invented 2 new incompatible protocols that only their compositor works with (which doesn't work with existing applications). No HDR or high DPI is an annoyance. Not supporting accessibility is real deal breaker. Especially for commercial settings where things like Americans with Disability Act compliance matters. And even more for me with my retinas slowly tearing apart and losing my eyesight: the entire waylands ecosystem is extremely inconsistent and buggy.
mappu 1y ago
I'm in a similar boat - i tried the Wayland session in Debian 10 and 11 and lasted less than a day; in Debian 12 i toughed it out for about a week before hitting a showstopper; but this time in Debian 13 i've used it since release without a single nit to pick.
eek2121 1y ago
The issue is that you are using Debian stable. Software quickly becomes out of date, sometimes by years, with the exception of security fixes and occasional backports. Wayland, KDE, and several other pieces of software evolve rapidly. What may be broken in one release will very likely be fixed a few releases after the last debian stable release. I'll run Debian on a server if I need predictability and stability with known issues. I won't run Debian on a desktop or workstation for the same reason.
- vlovich123 1y ago
  I’m in Arch and I generally struggle to get video acceleration in a browser with an Nvidia GPU.
  - levkk 1y ago
    Yup, same, using X, everything mostly works. Wayland - not so much.
  - fooker 1y ago
    Wayland + KDE in Arch has worked seamlessly with NVDIA GPUs for a couple of years now.
    - vlovich123 1y ago
      That’s what you’ve heard or been your experience? I’m sitting with SW acceleration in the browser today because some update broke it. I have had it working in the past but I’ve had like 2-3 updates in the past 2 years break it. And for what it’s worth there was a really bad tearing bug because of the argument over implicit and explicit synchronization that neither side wanted to fix. I think it’s since been addressed but that was only like in the past 6 months or something. So it’s definitely not been “years” since it’s been working seamlessly. Things break at a greater rate than X because X basically is frozen and isn’t getting updates.
      - fooker 1y ago
therealfiona 1y ago
Call me when I can run Wayland and share my full screen on M$ Teams. Last time I checked it was just individual windows. Cross that hurdle and I can go back to trusting the Linux Desktop for business things.
- abhinavk 1y ago
  I use it via Chromium. Are there additional features in the Electron version?
  - rs186 1y ago
    There is no electron version of MS Teams on Linux (any more). Thanks Microsoft!
- ahartmetz 1y ago
  Works fine in current KDE master branch, and it's been working for quite a while so it should be in the current release. Note that I run Teams in MS Edge for Linux, which is my dedicated Teams runtime environment and sandbox.
- heavyset_go 1y ago
  The only time I've ever had screensharing working correctly is under Wayland
bee_rider 1y ago
Has any distro ever promised that there are zero bugs in the software they use? I don’t particularly like Wayland but a lot of people have been using it for years at this point…
- devmor 1y ago
  User adoption is not really a great metric when it ships as a default on common distros. Most people would rather deal with issues and wait for support than fix things in an unsupported way. If it wasn't a default, it'd go back to barely being used.
  - frollogaston 1y ago
    If it's really broken, they can't get away with setting it default.
    - hulitu 1y ago
      Microsoft/Google would like to have a word with you.
      - MiddleEndian 1y ago
        Yep lol my experience on Windows 11 is that when opening a laptop, there's a realistic chance the taskbar will hang and have to restart itself (which takes a surprisingly long time)
        const_cast 1y ago
        This is my reality too and the taskbar takes some stuff down with it. Also the taskbar is just broken in general. It'll pull tons of apps behind the '...' button even though there's plenty of room on the taskbar and it'll also put fake apps that aren't actually open on the taskbar. Also no vertical task bar. Come on Microsoft.
        1y ago
athrowaway3z 1y ago
Wayland / KDE has been my main driver for a year on Void linux. IIRC it requires some tweaks at the start, it has worked without problems since then.
pmontra 1y ago
I installed Debian 13 on my laptop from 2014. It's got an NVIDIA K1100M. The latest proprietary driver supporting it is 390 which is not supported by Debian 13. It was by Debian 11. I skipped 12. I run Nouveau and Wayland and everything that didn't work with Wayland on Debian 11 works now, with one unfortunate exception: backlight control is broken, which means that I'm stuck with 100% brightness. That's probably a problem with the kernel or the driver because it happens with X11 too. X11 has a workaround for that because I can use gamma correction to simulate brightness control and make it work with night light. There was no way to do it in Wayland: they stomp on each other and undo whatever the other software did. So I'm back to X11 and frankly I don't notice any difference. If you have more luck with your graphic card you'll be probably OK with Wayland. Anyway the X11 session is there, logout from Wayland and login using X11.
- lproven 1y ago
  > It's got an NVIDIA K1100M. The latest proprietary driver supporting it is 390 which is not supported by Debian 13. It was by Debian 11. Tell me more, please. Does it only have an nVidia or is it dual GPU and switching? Because I have the latter and the lack of GPU drivers is keeping me on Ubuntu 22.04. Is it possible you're just using the Intel GPU and your nVidia is inactive?
  - pmontra 1y ago
    I'm still dual booting. Debian 11 to work and Debian 13 to finish setting up everything. With Debian 11, kernel 5.10.0-35-amd64 I was sure that I was using the NVIDIA driver 390 but I run dpkg -l before replying to you and I found out that actually I'm running the 470.256.02 driver. I definitely run the NVIDIA card because NVIDIA X Server Settings is telling me that X Screen 0 is on "Quadro K1100M (GPU 0)". I see it also in /var/log/messages and $ lspci -k | grep -A 3 VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1) DeviceName: 0 Subsystem: Hewlett-Packard Company ZBook 15 Kernel driver in use: nvidia cpuinfo reports that my CPU is an i7-4700MQ CPU @ 2.40GHz which according to the Intel web site has an internal Intel® HD Graphics 4600. I think that I never used it. NVIDIA X Server Settings does not report it but it's a NVIDIA program so I would not be surprised if it does not see it. Anyway, the kernel module for Intel should be i915 and it's not there. Maybe I have to load it but I'm phasing out this version of the OS. I'm pretty sure I never installed anything to switch between the two GPUs. There used to be something called bumblebee. Is that what you are using now? Apparently I can install the 470 driver in Debian 13 https://forums.debian.net/viewtopic.php?t=163756 https://forums.debian.net/viewtopic.php?t=163756 but it's from the unstable distribution and if Nouveau works I'm fine with that. I'm afraid that the NVIDIA driver and Wayland won't mix well even on 13 so I'll be on X11 anyway.
guappa 1y ago
There are still numerous little issues.
p4bl0 1y ago
I use the current stable with KDE Plasma over X11, there's nothing forcing you to use Wayland in Trixie.
triknomeister 1y ago
I'm using Wayland exclusively for 4 years now on Archlinux (may be more, I forget). At this point, it is better than X11. It still has bugs, but then so does X11. Fractional scaling is fixed in Plasma 6 though. So, if you need that, it has been good for 1 year now.
- skeezyboy 1y ago
  i dont want to call linux old fashioned but to still be working the kinks out of windowing system in 2025 boggles me... its almost as if there's a resistance to GUIs or something.
  - triknomeister 1y ago
    GUIs are tough in open source because they need way more than just code. You need UX designers, testers, feedback loops, and infrastructure — stuff most volunteer projects can’t sustain. That’s why devs can dogfood CLI tools but GUIs are a whole different beast. Even *Windows* and *macOS* struggle with this — just look at how messy *fractional scaling* is [link](https://devblogs.microsoft.com/oldnewthing/20221025-00/?p=107318 https://devblogs.microsoft.com/oldnewthing/20221025-00/?p=10...). And yet, *Linux/KDE* has been pushing GUI innovation for decades. Apple and Microsoft have copied so many KDE features it’s hard to keep track.
  - const_cast 1y ago
    The window manager in windows is horribly buggy and extremely slow. Lots of animation flickering and snapping for seemingly no reason. Try maximizing Firefox while a video is playing and watch the animation - or, usually, lack thereof. Wayland is, by far, the best windowing system I've ever used. No dropped frames, ever. Its actually kind of uncanny, it feels like you're using an iPhone.
sho_hn 1y ago
While I appreciate all the folks singing our praises, as an upstream developer I think you deserve a better response than "you are holding it wrong" :) We think that the Wayland session currently is the better choice for the majority of our users. It's more stable and polished, performs better on average, and has more features and enables more hardware. That said there are still gaps in the experience, and non-latin input is one of them. In principle it's roughly on par witu X11, but it's still pretty crap, e.g. at the moment we give you a choice between having a virtual keyboard and having something like ibus active, when many users want both at the same time, and a lot of the non-latin setup stuff is still not part of the core product, which is very user-unfriendly. The KDE Linux alpha in particular will definitely and unequivocably not serve you well as it currently doesn't ship any ibus/fcitx. The good news is that this is something we are very actively working on in the background right now. We have an annual community-wide goal election process that made Input improvements one of our goals, and the topic has been all over our developer conference this year.
- snickerdoodle14 1y ago
  Can I do something like `wmctrl -xa terminator || exec terminator` yet?
- superkuh 1y ago
  Another huge gap is accessibility. No wayland compositor has managed to implement screen reader support that works with existing applications yet. And no, GNOME's wayland compositor did not achieve this. In typical GNOME fashion they threw away all support for existing screen readers and accessibility and invented two entirely new GNOME only protocols that no software except theirs supports.
samiv 1y ago
I just pointing this out in the other comment. So no, bugs are still there, plenty of system level graphics glitches in all but most trivial circumstances. Jank and glitches. Jank and glitches.
superkuh 1y ago
I hope it also means they've managed to do what no wayland compositor has managed in the past 15 years: have working accessibility (screen reader support, etc) that works with existing applications. Otherwise this is just another toy/demo distro. And no, gnome's wayland compositor did not achieve it either. They threw away all accessibility support and then invented two new gnome-only protocols for it that no software except gnomes own compositor supports.

by o11c 1y ago

jacobsenscott 1y ago

Wayland works great for me. I use a rolling update distribution so everything is the latest version and I only use Firefox, a terminal, and emacs. Debian tends to be pretty far behind.

alabhyajindal 1y ago

When was the last time you tried Wayland? I switched to KDE Plasma a couple years ago not knowing anything about display server protocols and haven't had a single issue.

o11c 1y ago
The last time I tried it extensively was on Debian Bookwork (12.1 and later; I always wait for the first point release), released July 2023 but freezing sometime around February 2023. Yes, this was a while ago now. But just as now, people said then "all the bugs are fixed and missing features added"; all that really means is "we're in the long tail". I might've put up with it if not for the fact that there were 2ish major bugs that directly affected my main workflow (e.g. temporarily swapping to non-Latin text input).
dboon 1y ago
Same experience. I switched back to Linux a few months ago after a few years hiatus. Installed Arch and KDE Plasma. Literally didn’t even know I was using Wayland until I had to fiddle with something and realized X wasn’t even installed

zdragnar 1y ago

I think "most" are fixed. I use quotes because I've seen people say they have issues that I have never run into myself. I'm currently stuck on Windows for some old school .NET work, but otherwise have been running Wayland on either arch or fedora for 8 or so years, no real problems specific to Wayland. With that said, I've also always had X to fall back to for the odd program that absolutely only worked in an X session. At this point, though, I don't even recall what they were (probably something that didn't like running under Swaywm because wlroots), so even that might not be an issue.

Almondsetat 1y ago

Are all X11 bugs fixed?

o11c 1y ago
I haven't hit any for probably a decade now. Bugs in the window manager or shell (both shipped by KDE) are somewhat more common, but even if they are crashes, due to X11 being better-designed for isolated faults they are easily recovered-from without loss of session.
- jsheard 1y ago
  X11 not supporting modern display technologies is arguably a bug, and it's not likely to get resolved at this point (e.g. it can't do mixed DPIs, or VRR with multiple displays, or HDR in general).
  - o11c 1y ago
    I don't care about any of those things, since computers are about productivity for me. But I'm pretty sure at least half of them actually do work under X11, it's just that some UI libraries refuse to use it on the grounds of "X11 is outdated, I won't support features even though it does". (also, having played around with DPI stuff on Wayland, it's pretty broken there in practice)
    - whatevaa 1y ago
      Well and others do care, and no, bunch of stuff straight up doesn't work on Xorg, or is jank fest.
      - superkuh 1y ago
        Yep. I feel the same about all the various wayland compositors. Even 15 years on none of them have managed to implement accessibility support for existing linux applications. No screen readers support on any but GNOME's compositor and that doesn't work with existing applications; GNOME invented 2 new incompatible protocols that only their compositor works with (which doesn't work with existing applications). No HDR or high DPI is an annoyance. Not supporting accessibility is real deal breaker. Especially for commercial settings where things like Americans with Disability Act compliance matters. And even more for me with my retinas slowly tearing apart and losing my eyesight: the entire waylands ecosystem is extremely inconsistent and buggy.

mappu 1y ago

I'm in a similar boat - i tried the Wayland session in Debian 10 and 11 and lasted less than a day; in Debian 12 i toughed it out for about a week before hitting a showstopper; but this time in Debian 13 i've used it since release without a single nit to pick.

eek2121 1y ago

The issue is that you are using Debian stable. Software quickly becomes out of date, sometimes by years, with the exception of security fixes and occasional backports. Wayland, KDE, and several other pieces of software evolve rapidly. What may be broken in one release will very likely be fixed a few releases after the last debian stable release. I'll run Debian on a server if I need predictability and stability with known issues. I won't run Debian on a desktop or workstation for the same reason.

vlovich123 1y ago
I’m in Arch and I generally struggle to get video acceleration in a browser with an Nvidia GPU.
- levkk 1y ago
  Yup, same, using X, everything mostly works. Wayland - not so much.
- fooker 1y ago
  Wayland + KDE in Arch has worked seamlessly with NVDIA GPUs for a couple of years now.
  - vlovich123 1y ago
    That’s what you’ve heard or been your experience? I’m sitting with SW acceleration in the browser today because some update broke it. I have had it working in the past but I’ve had like 2-3 updates in the past 2 years break it. And for what it’s worth there was a really bad tearing bug because of the argument over implicit and explicit synchronization that neither side wanted to fix. I think it’s since been addressed but that was only like in the past 6 months or something. So it’s definitely not been “years” since it’s been working seamlessly. Things break at a greater rate than X because X basically is frozen and isn’t getting updates.
    - fooker 1y ago

therealfiona 1y ago

Call me when I can run Wayland and share my full screen on M$ Teams. Last time I checked it was just individual windows. Cross that hurdle and I can go back to trusting the Linux Desktop for business things.

abhinavk 1y ago
I use it via Chromium. Are there additional features in the Electron version?
- rs186 1y ago
  There is no electron version of MS Teams on Linux (any more). Thanks Microsoft!
ahartmetz 1y ago
Works fine in current KDE master branch, and it's been working for quite a while so it should be in the current release. Note that I run Teams in MS Edge for Linux, which is my dedicated Teams runtime environment and sandbox.
heavyset_go 1y ago
The only time I've ever had screensharing working correctly is under Wayland

bee_rider 1y ago

Has any distro ever promised that there are zero bugs in the software they use? I don’t particularly like Wayland but a lot of people have been using it for years at this point…

devmor 1y ago
User adoption is not really a great metric when it ships as a default on common distros. Most people would rather deal with issues and wait for support than fix things in an unsupported way. If it wasn't a default, it'd go back to barely being used.
- frollogaston 1y ago
  If it's really broken, they can't get away with setting it default.
  - hulitu 1y ago
    Microsoft/Google would like to have a word with you.
    - MiddleEndian 1y ago
      Yep lol my experience on Windows 11 is that when opening a laptop, there's a realistic chance the taskbar will hang and have to restart itself (which takes a surprisingly long time)
      - const_cast 1y ago
        This is my reality too and the taskbar takes some stuff down with it. Also the taskbar is just broken in general. It'll pull tons of apps behind the '...' button even though there's plenty of room on the taskbar and it'll also put fake apps that aren't actually open on the taskbar. Also no vertical task bar. Come on Microsoft.
        1y ago

athrowaway3z 1y ago

Wayland / KDE has been my main driver for a year on Void linux. IIRC it requires some tweaks at the start, it has worked without problems since then.

pmontra 1y ago

I installed Debian 13 on my laptop from 2014. It's got an NVIDIA K1100M. The latest proprietary driver supporting it is 390 which is not supported by Debian 13. It was by Debian 11. I skipped 12. I run Nouveau and Wayland and everything that didn't work with Wayland on Debian 11 works now, with one unfortunate exception: backlight control is broken, which means that I'm stuck with 100% brightness. That's probably a problem with the kernel or the driver because it happens with X11 too. X11 has a workaround for that because I can use gamma correction to simulate brightness control and make it work with night light. There was no way to do it in Wayland: they stomp on each other and undo whatever the other software did. So I'm back to X11 and frankly I don't notice any difference. If you have more luck with your graphic card you'll be probably OK with Wayland. Anyway the X11 session is there, logout from Wayland and login using X11.

lproven 1y ago
> It's got an NVIDIA K1100M. The latest proprietary driver supporting it is 390 which is not supported by Debian 13. It was by Debian 11. Tell me more, please. Does it only have an nVidia or is it dual GPU and switching? Because I have the latter and the lack of GPU drivers is keeping me on Ubuntu 22.04. Is it possible you're just using the Intel GPU and your nVidia is inactive?
- pmontra 1y ago
  I'm still dual booting. Debian 11 to work and Debian 13 to finish setting up everything. With Debian 11, kernel 5.10.0-35-amd64 I was sure that I was using the NVIDIA driver 390 but I run dpkg -l before replying to you and I found out that actually I'm running the 470.256.02 driver. I definitely run the NVIDIA card because NVIDIA X Server Settings is telling me that X Screen 0 is on "Quadro K1100M (GPU 0)". I see it also in /var/log/messages and $ lspci -k | grep -A 3 VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1) DeviceName: 0 Subsystem: Hewlett-Packard Company ZBook 15 Kernel driver in use: nvidia cpuinfo reports that my CPU is an i7-4700MQ CPU @ 2.40GHz which according to the Intel web site has an internal Intel® HD Graphics 4600. I think that I never used it. NVIDIA X Server Settings does not report it but it's a NVIDIA program so I would not be surprised if it does not see it. Anyway, the kernel module for Intel should be i915 and it's not there. Maybe I have to load it but I'm phasing out this version of the OS. I'm pretty sure I never installed anything to switch between the two GPUs. There used to be something called bumblebee. Is that what you are using now? Apparently I can install the 470 driver in Debian 13 https://forums.debian.net/viewtopic.php?t=163756 https://forums.debian.net/viewtopic.php?t=163756 but it's from the unstable distribution and if Nouveau works I'm fine with that. I'm afraid that the NVIDIA driver and Wayland won't mix well even on 13 so I'll be on X11 anyway.

guappa 1y ago

There are still numerous little issues.

p4bl0 1y ago

I use the current stable with KDE Plasma over X11, there's nothing forcing you to use Wayland in Trixie.

triknomeister 1y ago

I'm using Wayland exclusively for 4 years now on Archlinux (may be more, I forget). At this point, it is better than X11. It still has bugs, but then so does X11. Fractional scaling is fixed in Plasma 6 though. So, if you need that, it has been good for 1 year now.

skeezyboy 1y ago
i dont want to call linux old fashioned but to still be working the kinks out of windowing system in 2025 boggles me... its almost as if there's a resistance to GUIs or something.
- triknomeister 1y ago
  GUIs are tough in open source because they need way more than just code. You need UX designers, testers, feedback loops, and infrastructure — stuff most volunteer projects can’t sustain. That’s why devs can dogfood CLI tools but GUIs are a whole different beast. Even *Windows* and *macOS* struggle with this — just look at how messy *fractional scaling* is [link](https://devblogs.microsoft.com/oldnewthing/20221025-00/?p=107318 https://devblogs.microsoft.com/oldnewthing/20221025-00/?p=10...). And yet, *Linux/KDE* has been pushing GUI innovation for decades. Apple and Microsoft have copied so many KDE features it’s hard to keep track.
- const_cast 1y ago
  The window manager in windows is horribly buggy and extremely slow. Lots of animation flickering and snapping for seemingly no reason. Try maximizing Firefox while a video is playing and watch the animation - or, usually, lack thereof. Wayland is, by far, the best windowing system I've ever used. No dropped frames, ever. Its actually kind of uncanny, it feels like you're using an iPhone.

sho_hn 1y ago

While I appreciate all the folks singing our praises, as an upstream developer I think you deserve a better response than "you are holding it wrong" :) We think that the Wayland session currently is the better choice for the majority of our users. It's more stable and polished, performs better on average, and has more features and enables more hardware. That said there are still gaps in the experience, and non-latin input is one of them. In principle it's roughly on par witu X11, but it's still pretty crap, e.g. at the moment we give you a choice between having a virtual keyboard and having something like ibus active, when many users want both at the same time, and a lot of the non-latin setup stuff is still not part of the core product, which is very user-unfriendly. The KDE Linux alpha in particular will definitely and unequivocably not serve you well as it currently doesn't ship any ibus/fcitx. The good news is that this is something we are very actively working on in the background right now. We have an annual community-wide goal election process that made Input improvements one of our goals, and the topic has been all over our developer conference this year.

snickerdoodle14 1y ago
Can I do something like `wmctrl -xa terminator || exec terminator` yet?
superkuh 1y ago
Another huge gap is accessibility. No wayland compositor has managed to implement screen reader support that works with existing applications yet. And no, GNOME's wayland compositor did not achieve this. In typical GNOME fashion they threw away all support for existing screen readers and accessibility and invented two entirely new GNOME only protocols that no software except theirs supports.

samiv 1y ago

I just pointing this out in the other comment. So no, bugs are still there, plenty of system level graphics glitches in all but most trivial circumstances. Jank and glitches. Jank and glitches.

superkuh 1y ago

I hope it also means they've managed to do what no wayland compositor has managed in the past 15 years: have working accessibility (screen reader support, etc) that works with existing applications. Otherwise this is just another toy/demo distro. And no, gnome's wayland compositor did not achieve it either. They threw away all accessibility support and then invented two new gnome-only protocols for it that no software except gnomes own compositor supports.