Wayland version 1.23 now accessible

After over a year of development presented stable release of the protocol, interprocess communication mechanism and libraries Wayland 1.23. The 1.23 branch is backwards compatible at the API and ABI level with the 1.x releases and contains mostly bug fixes and minor protocol updates. Project developments spread under MIT license. Reference Composite Server Westonwhich provides code and working examples for using Wayland in desktop environments and embedded solutions, is being developed as part of a separate development cycle.

Major changes to protocol:

  • In libwayland implemented An API that allows the client to determine the maximum size of the internal connection buffer on the server side. The base maximum buffer size is set via the wl_display interface, and the new API allows clients to change it on a per-client connection basis. On the practical side, the change allows the use of larger buffers in Wayland-specific clients, such as Xwayland, which are characterized by a higher intensity of input events.
  • Requests, events, and enums now have the ability to use the “deprecated-since” XML attribute to mark elements as deprecated. In Wayland terminology, requests are messages sent by a client to a server; events are messages transmitted from the server to the client; Enumerations are sets of numeric values ​​associated with a specific name that the protocol manipulates.
  • To the utility wayland-scannerdesigned for generating header files and code in the C language based on XML files describing the protocol, the “enum-header” mode has been added, which includes specifying only “enumerations” in header files.
  • wayland-scanner provides generation of verification functions (validator) for “enumerations” on the server side.
  • Added an API to assign a name to the queue to simplify later debugging.
  • Added functions wl_client_get_user_data() and wl_client_set_user_data() to make it easier to attach arbitrary data to the client.
  • Added a wl_shm.release request that allows the client to inform the server to stop using a shared object, allowing the server to release the memory associated with it.
  • Added support for the OpenBSD platform.

Wayland-related events that have occurred since the publication of the last issue:

  • XWayland 24.1.0 has been published with support for Explicit Sync technology and improved support for GLAMOR and EXA 2D acceleration architectures.
  • Update of the labwc (Lab Wayland Compositor) composite server with capabilities reminiscent of the Openbox window manager.
  • The wprs project develops a session manager for Wayland, similar to the screen utility, but for graphical applications.
  • Publishing a composite Niri server using Wayland and offering a tiling layout method that groups windows into an endlessly scrolling ribbon on the screen.
  • Update of the Wayland-Protocols set of protocols and extensions: 1.34, 1.33, 1.32, 1.35.
  • Development of an SDL3 library that uses Wayland by default.
  • Release of LXQt 2.0.0 desktop environment with Wayland support in PCManFM-Qt file manager, notification system, desktop, Runner, panel, logout interface, LXQt configuration interface and most applications.
  • Release of the Sway 1.9 user environment using Wayland.
  • New composite manager miracle-wm, based on Wayland and components for building Mir composite managers.
  • Louvre is a new library for developing composite servers based on Wayland.
  • Working on implementing Wayland support in Xfce.
  • Initial support for Wayland in the Budgie desktop environment.
  • Initial support for Wayland in the Cinnamon desktop environment.
  • Almost completed Porting the MATE desktop to Wayland.
  • The Lubuntu distribution is switching to Qt 6 and Wayland.
  • KDE 6 offers a default session that uses the Wayland protocol. Implemented support for Wayland extensions for color management.
  • Window decoration mode for Wayland is enabled in the Electron platform.
  • Update of the Wayfire composite server, which uses Wayland and allows you to create user interfaces with 3D effects in the style of 3D plugins for Compiz.
  • Wayland support in IntelliJ and OpenJDK IDEs.
  • Wayland support in the GNU Emacs text editor.
  • GNOME's Wayland-based session includes support for the Input Leap software KVM switch, which allows you to use a single keyboard and mouse to control multiple computers.
  • The KDE desktop edition of Fedora has stopped supporting X11-based session in the base distribution.
  • Improved support for Wayland-based environments in proprietary NVIDIA drivers.
  • A driver has been implemented that allows you to use Wine in environments based on the Wayland protocol without using XWayland and X11 components.
  • The Weston 13.0 composite server has been released.
  • To test KDE, GNOME, Enlightenment, Wayfire, Mir, Xfce and Sway over Wayland released special Live distribution Rebecca Black Linux.
  • Linux builds of Firefox are enabled by default to use the Wayland composite server instead of XWayland. It is possible to create assemblies that support work only in Wayland.

Let us remind you that Wayland is is a protocol for interaction between a composite server and applications working with it. Clients render their own windows in a separate buffer, passing updates to the composite server, which combines the contents of individual application buffers to produce a final output that takes into account possible nuances such as window overlap and transparency. In other words, the composite server does not provide an API for rendering individual elements, but only operates on already formed windows, which allows you to get rid of double buffering when using high-level libraries such as GTK and Qt, which take on the work of compositing the contents of windows.

Wayland solves many of X11's security problems by isolating input and output on a per-window basis, preventing a client from accessing the contents of other clients' windows, and preventing input events associated with other windows from being intercepted. Currently, support for direct work with Wayland has already been implemented for the GTK, Qt, SDL (starting with release 2.0.2), Clutter and EFL (Enlightenment Foundation Library) libraries. Starting with Qt 5.4, the QtWayland module is included with the implementation of components for running Qt applications in the environment of the Weston composite server, developed by the Wayland project.

Interaction with Wayland/Weston hardware, such as initialization, drm modesetting, and memory management (GEM for i915 and TTM for radeon and nouveau) of graphics cards, can be done directly through a module running at the kernel level, allowing do without superuser privileges. The Weston composite server can run not only using the Linux kernel DRM, but also on top of X11, another Wayland composite server, framebuffer, and RDP. In addition, projects are being developed to provide work on top of the graphics stack of the Android platform.

As part of the Weston project, one of the implementations of the composite server is being developed. Any other product that supports the Wayland protocol can also act as a composite server. For example, work is currently underway to provide Wayland support in KWin. In its current form, Weston has already gone beyond a set of examples for testing the Wayland protocol and can acquire functionality through plugins and add-ons. Custom shells and advanced window management functions are proposed to be implemented in the form of external backends to Weston. To ensure the execution of regular X11 applications in a Wayland-based environment, the DDX component is used XWayland (Device-Dependent X), similar in organization of work to Xwin and Xquartz for the Win32 and macOS platforms.

Thanks for reading: