KDE Plasma 6.0 Is Enabling Wayland by Default

Original Article ↗ Hacker News Discussion ↗

KDE Plasma 6.0 will switch to Wayland as the default display server, signaling that major Linux desktops now see it as mature enough to replace the long‑standing X11 system. Commenters report that Wayland on KDE already works well for many everyday and gaming setups, highlighting benefits like no screen tearing, better security, HDR support and improving tiling features, but also note lingering problems around NVIDIA drivers, screen sharing, fractional scaling and niche tools such as password managers or KM software. Alongside technical issues, people debate KDE’s visual design and polish relative to GNOME and macOS, with some praising its power and customizability and others criticizing inconsistent spacing and aesthetics.

Wayland adoption & overall stability

  • Several users run KDE Plasma on Wayland daily (often for a year+), reporting it as “works fine” for typical laptop/desktop use and gaming.
  • Others see show‑stopping bugs: panels appearing in the wrong place, misaligned input coordinates, black screens after suspend, and cursor stutter in KDE Wayland but not in KDE X11 or GNOME Wayland.
  • Some issues appear distro‑ or configuration‑specific (e.g., NixOS unstable, Void), but others report the same problems across multiple machines.
  • A number of people say they’ll stay on X11 or delay switching, citing a long tail of small but annoying regressions.

NVIDIA and hardware-specific problems

  • NVIDIA is repeatedly called out as problematic on Wayland: tearing/flickering in Xwayland, broken multi‑monitor setups, rotation issues, flaky wake‑from‑sleep, and broken “Night Color”/Night Light.
  • Some say recent proprietary drivers (e.g., 545) significantly improve Wayland; others report new regressions (e.g., screens never waking after blanking).
  • Several users say AMD and Intel GPUs are largely trouble‑free on Wayland; a few have Intel-only lockups as well.
  • Debate over responsibility: some argue the community shouldn’t bend around NVIDIA; others note that X11 + NVIDIA still “just works” and see Wayland as premature.

Application, scaling & input quirks

  • Firefox, Chrome, Electron apps, and some IMEs often need environment variables or flags for Wayland mode; behavior varies by distro.
  • Fractional scaling: KDE’s Xwayland DPI scaling is viewed as better than GNOME/wlroots’ blurry upscaling, but Electron apps and older builds often misbehave.
  • Missing Wayland APIs (cursor position, window state) break or complicate tools like KeePassXC AutoType, goldendict popups, autokey‑style automation, and multi‑machine keyboard/mouse sharing (Barrier/Synergy; new fork “input-leap” is in progress).

Screen capture, RDP & conferencing

  • Screen capture is reported as working well for many via PipeWire/portals and OBS, but legacy apps that grab the X11 root window (e.g., some versions of Discord, Zoom, Meet) still fail.
  • KDE is adding an Xwayland video bridge to improve compatibility.
  • GNOME is preferred by some for out‑of‑box RDP; KDE’s KRDP exists but is less integrated.

Features, performance & security

  • Wayland benefits cited: no screen tearing, better sandboxing (socket-based access), HDR/VRR and gaming (often via Gamescope), and improved Plasma startup by deferring non‑essential services.
  • Some question UX trade‑offs of deferring launcher search backends to first use rather than at login.

KDE design vs alternatives

  • Heated debate on aesthetics: some call KDE visually inconsistent, dense, and “amateur” next to macOS/GNOME; others strongly prefer its information density, configurability, and classic desktop conventions.
  • There is recognition that KDE is highly themeable, but critics argue deeper layout/margin/hierarchy issues can’t be fixed by themes alone.
  • Several note Plasma 6 aims to simplify defaults and improve visual consistency, but opinions diverge on whether design quality is already “fine” or fundamentally lacking.