Yep you read that right, we’ve decided to throw the lever and go Wayland by default! The three remaining showstoppers are in the process of being fixed and we expect them to be done soon̵…
How is Wayland “ready” when critical things like idk, non QT apps quiting when the compositor crashes (and thus losing progress!) are called a “non showstopper”
its not listed as one is the weird thing, because it totally should be
imagine drawing and suddenly your compositor crashes leading to your program to crash and you to lose hours of progress, but other QT programs are fine
should’ve used krita because that’s QT except you cant replicate your workflow in that program because it misses features (and also you dont like it)
This is a real scenario I would have to worry about. That’s a showstopper for me
@Zamundaaa@mnglw xorg Apps don’t crash when the compositor crashes, you can just switch out compositors/window managers. But xorg Apps crash when the xserver is crashing
How is Wayland “ready” when critical things like idk, non QT apps quiting when the compositor crashes (and thus losing progress!) are called a “non showstopper”
Yeah… This one actually is a showstopper. And I thought it was fixed, didn’t realize it was fixed for QT apps only
its not listed as one is the weird thing, because it totally should be
imagine drawing and suddenly your compositor crashes leading to your program to crash and you to lose hours of progress, but other QT programs are fine
should’ve used krita because that’s QT except you cant replicate your workflow in that program because it misses features (and also you dont like it)
This is a real scenario I would have to worry about. That’s a showstopper for me
It actually was https://web.archive.org/web/20231023140410/https://community.kde.org/Plasma/Wayland_Showstoppers
I wonder why it isn’t anymore, because it’s been downgraded to Non-showstoppers
@klangcola @mnglw there are MRs to GTK, wlroots and SDL but the applications/framework will merge and publish the fix at their own release schedule
So it’s not a showstopper for KDE Wayland default because the fix is outside KDEs control?
It doesn’t really matter to end users though. So making the may-suddenly-loose-hours-of-work option the default seems unwise
so Wayland is not ready to be a default yet
How is Xorg ready when critical things like all apps crashing when the
compositordisplay server crashes are completely ignored?@Zamundaaa @mnglw xorg Apps don’t crash when the compositor crashes, you can just switch out compositors/window managers. But xorg Apps crash when the xserver is crashing
Ugh, I’ve been working on Wayland too much… I meant to write display server. Thanks