Feature Highlight - Wayland Compositor Hand-Off
http://blog.davidedmundson.co.uk/blog/qt6_wayland_robustness/ This is a robustness improvements that let Wayland clients (applications/programs) gracefully survive and reconnect with the Wayland Compositor after a crash / restart or even complete replacement with a different Wayland compositor. X11 Server, from what I understood in my old explorations, architecturally it would not have been possible to get there from within the limits of X11's design. As someone who daily drives KDE Plasam Wayland, I'm really looking forward to this coming down stream. I've at various time suffered the pain of loosing my whole session over crash bugs. A frustrating, but thankfully brief example was a combination of PrusaSlicer and the QT file dialog triggering a compositor crash. It really takes me back 15 years, when the same level of instability was in X11's ecosystem. But I switched to KDE's Wayland compositor because there are meaningful parts that are already surpassing the prior art, and competing with what the commercial OSes are putting out. -- Scott Sullivan
Thanks for sharing this, Scott.
As someone who daily drives KDE Plasma Wayland, I'm really looking forward to this coming down stream.
I echo this statement. Wayland has only been getting better & better on my KDE install on Arch. Wish I could discuss further @ tonight's meeting, but I'm double booked. Warm regards, -- Mark Prosser // E: mark@zealnetworks.ca // W: https://zealnetworks.ca
Now living in the future with KDE Plasma 6, on Fedora 40. I can confirm that compositor hand-off is working as intended. It's now recovering gracefully from infrequent bad interaction with a 3rd-party application. On 2023-09-12 11:18, Scott Sullivan via talk wrote:
http://blog.davidedmundson.co.uk/blog/qt6_wayland_robustness/
This is a robustness improvements that let Wayland clients (applications/programs) gracefully survive and reconnect with the Wayland Compositor after a crash / restart or even complete replacement with a different Wayland compositor.
X11 Server, from what I understood in my old explorations, architecturally it would not have been possible to get there from within the limits of X11's design.
As someone who daily drives KDE Plasam Wayland, I'm really looking forward to this coming down stream. I've at various time suffered the pain of loosing my whole session over crash bugs. A frustrating, but thankfully brief example was a combination of PrusaSlicer and the QT file dialog triggering a compositor crash. It really takes me back 15 years, when the same level of instability was in X11's ecosystem. But I switched to KDE's Wayland compositor because there are meaningful parts that are already surpassing the prior art, and competing with what the commercial OSes are putting out.
-- Scott Sullivan
participants (2)
-
Mark Prosser -
Scott Sullivan