And people not yet updated should wait at-least for a week. (leaving it here in case it would help someone, but ppl probably will read this already too late 
)
wayland isnt ready in ALL edgecases, it works for most cases and standard equipment, yes that is true.
but i have 1 specific configuration of a setup where wayland is giving me this flickering issue too, so i know this problem and it hasnt been fixed since ~3 years (DE is irrelevant, happens on kde/gnome)
Let’s not shout. Wayland isn’t ready — neither Wayland nor KDE Wayland. Not everyone has the same settings, and not everyone has the same packages. All of these run flawlessly on different Linux distros with X11.
The most commonly cited Wayland issues are deal-breaker for some people:
Screen sharing via portals + PipeWire remains unreliable for many users (Discord, OBS, etc.), with noisy failure modes requiring environment-variable debugging. No multi-user headless RDP; multi-monitor RDP is unsupported. Clipboard from remote sessions requires an intermediate local app before pasting into native Wayland apps.
On Nvidia even after explicit sync landed, users still report freezes, memory leaks, and desktop glitches depending on driver/Plasma version combos.
A fresh report (Oct 12, 2026) on the well-known “Wayland breaks everything” gist: modifier keys are not forwarded when scrolling unfocused windows, breaking ctrl+scroll / shift+scroll workflows.
SUDO_ASKPASS has been broken since 2022
STOP saying “Wayland is ready”. It’s wishful thinking. The correct question is “Which one is MORE ready”. Everybody is different and has different settings which work flawlessly on X11, but encounter errors on Wayland. I wish “Wayland was ready” but it’s not. Unfortunately.
If Wayland doesn’t support a user’s hardware/configuration/workflow, there are desktop environments that still support X11 sessions (at least for now). Change to one of them. Simple enough.
the problem that i have with wayland are latency.. it feels laggy with my rig even if it is native wayland much worst if it is running on xwayland.
the way they say wayland solve this, but in reality it isnt.
All,
Can we make an effort not to turn this into some kind of Wayland vs X11 war? Or a Wayland is “ready” war?
The reality is:
- Wayland will never reach a point where it is perfect for everyone and neither did X11
- There are some things that work better on X11
- There are some things that work better on Wayland
- There are some things that don’t work at all on X11
- There are some things that don’t work at all on Wayland
If you want to continue to use X11 for any reason you have a few options:
- Switch to a DE that still supports X(and, ideally, isn’t planning on removing it soon)
- Switch to a window manager that is X-based like i3wm or openbox
- Switch to an LTS distro which will have the older version of KDE for some time, i.e. Debian, Kubuntu LTS, etc
That being said, if you are having a specific issue on Wayland KDE, you should report it on the bug tracker if it isn’t already. Otherwise, it is probably never going to be fixed.
Thanks, this cleared up something I was about to ask. New to EndeavourOS and reading a lot before changing anything.
Thanks for the info — helpful while I get used to the rolling-release workflow.