Have not noticed any XWayland-specific crashes myself in two years I've been using it, but glad it gets the attention it deserves. XWayland is what makes Wayland functional, at least in KDE.
Switching Firefox to XWayland increases rendering performance drastically on my fairly trivial PC with an Intel iGPU. Without XWayland maps are barely usable due to graphics lag.
There are also other examples. Flatpak makes switching an app to XWayland trivial, so I do it with every app I use. Fixes tons of rendering issues.
I wanted to do Accessability stuff, so clicking and targeting windows automation, such as in autohotkey. Ydotool isnt even close. Its not really workable yet.
githman@reddit
Have not noticed any XWayland-specific crashes myself in two years I've been using it, but glad it gets the attention it deserves. XWayland is what makes Wayland functional, at least in KDE.
Life-Acanthaceae6659@reddit
I find Wayland to be perfectly functional, although I don't use X11 apps. Everything is compiled for Wayland only.
githman@reddit
Switching Firefox to XWayland increases rendering performance drastically on my fairly trivial PC with an Intel iGPU. Without XWayland maps are barely usable due to graphics lag.
There are also other examples. Flatpak makes switching an app to XWayland trivial, so I do it with every app I use. Fixes tons of rendering issues.
HerpaderPoE@reddit
I wanted to do Accessability stuff, so clicking and targeting windows automation, such as in autohotkey. Ydotool isnt even close. Its not really workable yet.
ilep@reddit
List of fixes:
https://lists.x.org/archives/xorg/2026-April/062234.html
Saved you a click.