Wayland 1.19 available

Stable release of the protocol, interprocess communication engine and libraries Wayland 1.19 . Branch 1.19 is backward compatible at the API and ABI level with the 1.x releases and contains mostly bug fixes and minor protocol updates. Improved build system, which now requires Meson tooling at least version 0.52.1. The Weston Composite Server, which provides code and working examples for using Wayland in desktop and embedded environments, is evolving in a separate development cycle .

Applications, desktop environments, and distributions related to Wayland:

  • Fedora 34 plans to migrate the KDE desktop build to use Wayland by default. The X11 session is planned to be an option. The kwin-wayland-nvidia package is used to run KDE when using proprietary NVIDIA drivers.
  • KDE is working to bring a Wayland-based session to readiness for day-to-day use and to achieve parity in functionality over X11. Fixed issues with screencasting and middle-click insertion. Fixed issues with XWayland stability. Provided the ability to adjust the speed of mouse movement and scrolling. In KWin, a large refactoring of the code responsible for compositing was carried out, which made it possible to achieve a decrease in latency for all operations related to the mixing of different objects on the screen. KWin also has a subsurface clipping technique that solves the flickering problem in many applications. The ability to work on systems with several GPUs and connect monitors with different screen refresh rates has been implemented.
  • Development of KWinFT, a fork of KWin focused on Wayland, has begun. The project also develops the wrapland library with the implementation of the libwayland binding for Qt / C ++, continuing the development of KWayland, but without the Qt binding.
  • GNOME for Wayland has removed full screen rendering when using dma-buf or EGLImage in favor of partial window updates, which reduce the amount of data transferred between GPU and CPU. In combination with an independent update of the interface elements, this optimization has significantly reduced power consumption when operating on battery power. Added the ability to assign different refresh rates for each monitor.
  • In GTK 4, the GDK APIs have been redesigned to use the Wayland protocol and related concepts. X11 and Wayland related features have been moved to separate backends.
/Media reports.