Wayland (display Server Protocol)

Wayland is a communication protocol that specifies the communication between a display server and its clients, as well as a C library implementation of that protocol. A display server using the Wayland protocol is called a '' Wayland compositor'', because it additionally performs the task of a compositing window manager.

Wayland is developed by a group of volunteers initially led by Kristian Høgsberg as a free and open-source community-driven project with the aim of replacing the X Window System with a secure and simpler windowing system for Linux and other Unix-like operating systems. The project's source code is published under the terms of the MIT License, a permissive free software licence.

As part of its efforts, the Wayland project also develops a implementation of a Wayland compositor called ''Weston''.

Overview

The Wayland Display Server project was started by Red Hat developer Kristian Høgsberg in 2008.

Beginning around 2010, Linux desktop graphics have moved from having "a pile of rendering interfaces... all talking to the X server, which is at the center of the universe" towards putting the Linux kernel and its components (i.e. Direct Rendering Infrastructure (DRI), Direct Rendering Manager (DRM)) "in the middle", with "window systems like X and Wayland ... off in the corner". This will be "a much-simplified graphics system offering more flexibility and better performance".

Høgsberg could have added an extension to X as many recent projects have done, but preferred to " ushX out of the hotpath between clients and the hardware" for reasons explained in the project's FAQ:

Wayland consists of a protocol and a reference implementation named Weston. The project is also developing versions of GTK and Qt that render to Wayland instead of to X. Most applications are expected to gain support for Wayland through one of these libraries without modification to the application.

Initial versions of Wayland have not provided network transparency, though Høgsberg noted in 2010 that network transparency is possible.
It was attempted as a Google Summer of Code project in 2011, but was not successful.
Adam Jackson has envisioned providing remote access to a Wayland application by either "pixel-scraping" (like VNC) or getting it to send a "rendering command stream" across the network (as in RDP, SPICE or X11). As of early 2013, Høgsberg was experimenting with network transparency using a proxy Wayland server which sends compressed images to the real compositor. In August 2017, GNOME saw the first such pixel-scraping VNC server implementation under Wayland. In modern Wayland compositors, network transparency is handled in a
xdg-desktop-portal implementation
that implements the RemoteDesktop portal.

Many Wayland compositors also include a
xdg-desktop-portal implementation
for common tasks such as a native file picker for native applications and sandboxes such as Flatpak
xdg-desktop-portal-gtk
is commonly used as a fallback filepicker), screen recording, network transparency, screenshots, color picking, and other tasks that could be seen as needing user intervention and being security risks otherwise. Note that xdg-desktop-portal is not Flatpak or Wayland-specific, and can be used with alternative packaging systems and windowing systems.

Software architecture

Protocol architecture

The Wayland protocol follows a client–server model in which clients are the graphical applications requesting the display of pixel buffers on the screen, and the server (compositor) is the service provider controlling the display of these buffers.

The Wayland reference implementation has been designed as a two-layer protocol:
* A low-level layer or ''wire protocol'' that handles the inter-process communication between the two involved processesclient and compositorand the marshalling of the data that they interchange. This layer is message-based and usually implemented using the kernel IPC services, specifically Unix domain sockets in the case of Linux and other Unix-like operating systems.
* A high-level layer built upon it, that handles the information that client and compositor need to exchange to implement the basic features of a window system. This layer is implemented as "an asynchronous object-oriented protocol".

While the low-level layer was written manually in C, the high-level layer is automatically generated from a description of the elements of the protocol stored in XML format. Every time the protocol description of this XML file changes, the C source code that implements such protocol can be regenerated to include the new changes, allowing a very flexible, extensible and error-proof protocol.

The reference implementation of Wayland protocol is split in two libraries: a library to be used by Wayland clients called libwayland-client and a library to be used by Wayland compositors called libwayland-server.

Protocol overview

The Wayland protocol is described as an "asynchronous object-oriented protocol". ''Object-oriented'' means that the services offered by the compositor are presented as a series of ''objects'' living on the same compositor. Each object implements an ''interface'' which has a name, a number of methods (called ''requests'') as well as several associated ''events''. Every request and event has zero or more arguments, each one with a name and a data type. The protocol is ''asynchronous'' in the sense that requests do not have to wait for synchronized replies or ACKs, avoiding round-trip delay time and achieving improved performance.

The Wayland clients can make a request (a method invocation) on some object if the object's interface supports that request. The client must also supply the required data for the arguments of such request. This is the way the clients request services from the compositor. The compositor in turn sends information back to the client by causing the object to emit events (probably with arguments too). These events can be emitted by the compositor as a response to a certain request, or asynchronously, subject to the occurrence of internal events (such as one from an input device) or state changes. The error conditions are also signaled as events by the compositor.

For a client to be able to make a request to an object, it first needs to tell the server the ID number it will use to identify that object. There are two types of objects in the compositor: global objects and non-global objects. Global objects are advertised by the compositor to the clients when they are created (and also when they are destroyed), while non-global objects are usually created by other objects that already exist as part of their functionality.

The interfaces and their requests and events are the core elements that define the Wayland protocol. Each version of the protocol includes a set of interfaces, along with their requests and events, which are expected to be in any Wayland compositor. Optionally, a Wayland compositor may define and implement its own interfaces that support new requests and events, thereby extending functionality beyond the core protocol. To facilitate changes to the protocol, each interface contains a "version number" attribute in addition to its name; this attribute allows for distinguishing variants of the same interface. Each Wayland compositor exposes not only what interfaces are available, but also the supported versions of those interfaces.

Wayland core interfaces

The interfaces of the current version of Wayland protocol are defined in the file of the Wayland source code. This is an XML file that lists the existing interfaces in the current version, along with their requests, events and other attributes. This set of interfaces is the minimum required to be implemented by any Wayland compositor.

Some of the most basic interfaces of the Wayland protocol are:
* ''wl_display'' the core global object, a special object to encapsulate the Wayland protocol itself
* ''wl_registry'' the global registry object, in which the compositor registers all the global objects that it wants to be available to all clients
* ''wl_compositor'' an object that represents the compositor, and is in charge of combining the different surfaces into one output
* ''wl_surface'' an object representing a rectangular area on the screen, defined by a location, size and pixel content
* ''wl_buffer'' an object that, when attached to a ''wl_surface'' object, provides its displayable content
* ''wl_output'' an object representing the displayable area of a screen
* ''wl_pointer'', ''wl_keyboard'', ''wl_touch'' objects representing different input devices like pointers or keyboards
* ''wl_seat'' an object representing a seat (a set of input/output devices) in multiseat configurations

A typical Wayland client session starts by opening a connection to the compositor using the ''wl_display'' object. This is a special local object that represents the connection and does not live within the server. By using its interface the client can request the ''wl_registry'' global object from the compositor, where all the global object names live, and bind those that the client is interested in. Usually the client binds at least a ''wl_compositor'' object from where it will request one or more ''wl_surface'' objects to show the application output on the display.

Wayland extension interfaces

A Wayland compositor can define and export its own additional interfaces. This feature is used to extend the protocol beyond the basic functionality provided by the core interfaces, and has become the standard way to implement Wayland protocol extensions. Certain compositors can choose to add custom interfaces to provide specialized or unique features. The Wayland reference compositor, Weston, used them to implement new experimental interfaces as a testbed for new concepts and ideas, some of which later became part of the core protocol (such as ''wl_subsurface'' interface added in Wayland 1.4).

Extension protocols to the core protocol

XDG-Shell protocol

XDG-Shell protocol (see freedesktop.org for XDG) is an extended way to manage surfaces under Wayland compositors (not only Weston). The traditional way to manipulate (maximize, minimize, fullscreen, etc.) surfaces is to use the wl_shell_*() functions, which are part of the core Wayland protocol and live in . An implementation of the xdg-shell protocol, on the contrary, is supposed to be provided by the Wayland compositor. So you will find the header in the Weston source tree.

xdg_shell is a protocol aimed to substitute wl_shell in the long term, but will not be part of the Wayland core protocol. It starts as a non-stable API, aimed to be used as a development place at first, and once features are defined as required by several desktop shells, it can be finally made stable. It provides mainly two new interfaces: xdg_surface and xdg_popup. The xdg_surface interface implements a desktop-style window that can be moved, resized, maximized, etc.; it provides a request for creating child/parent relationship. The xdg_popup interface implements a desktop-style popup/menu; an xdg_popup is always transient for another surface, and also has implicit grab.

IVI-Shell protocol

IVI-Shell is an extension to the Wayland core protocol, targeting in-vehicle infotainment (IVI) devices.

Rendering model

The Wayland protocol does not include a rendering API. Instead, Wayland follows a ''direct rendering'' model, in which the client must render the window contents to a buffer shareable with the compositor. For that purpose, the client can choose to do all the rendering by itself, use a rendering library like Cairo or OpenGL, or rely on the rendering engine of high-level widget libraries with Wayland support, such as Qt or GTK. The client can also optionally use other specialized libraries to perform specific tasks, such as Freetype for font rendering.

The resulting buffer with the rendered window contents are stored in a ''wl_buffer'' object. The internal type of this object is implementation dependent. The only requirement is that the content data must be shareable between the client and the compositor. If the client uses a software (CPU) renderer and the result is stored in the system memory, then client and compositor can use shared memory to implement the buffer communication without extra copies. The Wayland protocol already natively provides this kind of shared memory buffer through the ''wl_shm'' and ''wl_shm_pool'' interfaces. The drawback of this method is that the compositor may need to do additional work (usually to copy the shared data to the GPU) to display it, which leads to slower graphics performance.

The most typical case is for the client to render directly into a video memory buffer using a hardware (GPU) accelerated API such as OpenGL, OpenGL ES or Vulkan. Client and compositor can share this GPU-space buffer using a special handler to reference it. This method allows the compositor to avoid the extra data copy through itself of the main memory buffer client-to-compositor-to-GPU method, resulting in faster graphics performance, and is therefore the preferred one. The compositor can further optimize the composition of the final scene to be shown on the display by using the same hardware acceleration API as an API client.

When rendering is completed in a shared buffer, the Wayland client should instruct the compositor to present the rendered contents of the buffer on the display. For this purpose, the client binds the buffer object that stores the rendered contents to the surface object, and sends a "commit" request to the surface, transferring the effective control of the buffer to the compositor. Then the client waits for the compositor to release the buffer (signaled by an event) if it wants to reuse the buffer to render another frame, or it can use another buffer to render the new frame, and, when the rendering is finished, bind this new buffer to the surface and commit its contents. The procedure used for rendering, including the number of buffers involved and their management, is entirely under the client control.

Comparison with other window systems

Differences between Wayland and X

There are several differences between Wayland and X with regard to performance, code maintainability, and security:

; Architecture : The composition manager is a separate, additional feature in X, while Wayland merges display server and compositor as a single function. Also, it incorporates some of the tasks of the window manager, which in X is a separate client-side process.

; Compositing : Compositing is optional in X, but mandatory in Wayland. Compositing in X is "active"; that is, the compositor must fetch all pixel data, which introduces latency. In Wayland, compositing is "passive", which means the compositor receives pixel data directly from clients.

; Rendering : The X server itself is able to perform rendering, although it can also be instructed to display a rendered window sent by a client. In contrast, Wayland does not expose any API for rendering, but delegates to clients such tasks (including the rendering of fonts, widgets, etc.). Window decorations are to be rendered on the client side (e.g., by a graphics toolkit), or on the server side (by the compositor) with the opt-i
xdg-decoration
protocol, if the compositor chooses to implement such functionality.

; Security : Wayland isolates the input and output of every window, achieving confidentiality, integrity and availability for both. The original X design lacked these important security features, although some extensions have been developed trying to mitigate it.

: Also, with the vast majority of the code running in the client, less code needs to run with ''root'' privileges, improving security, although multiple popular Linux distributions now allow the X server to be run without root privileges.

; Networking : The X Window System is an architecture that was designed at its core to run over a network. Wayland does not offer network transparency by itself; however, a compositor can implement any remote desktop protocol to achieve remote display. In addition, there is research into Wayland image streaming and compression that would provide remote frame buffer access similar to that of VNC.

Compatibility with X

XWayland is an X Server running as a Wayland client, and thus is capable of displaying native X11 client applications in a Wayland compositor environment. This is similar to the way XQuartz runs X applications in macOS's native windowing system. The goal of XWayland is to facilitate the transition from X Window System to Wayland environments, providing a way to run unported applications in the meantime. XWayland was mainlined into X.Org Server version 1.16.

Widget toolkits such as Qt5 and GTK3 can switch their graphical back-end at run time, allowing users to choose at load time whether they want to run the application over X or over Wayland. Qt 5 provides the command-line option to that effect, whereas GTK 3 lets users select the desired GDK back-end by setting the Unix environment variable.

Wayland compositors

Display servers that implement the Wayland display server protocol are also called ''Wayland compositors'' because they additionally perform the task of a compositing window manager.

A library called wlroots is a modular Wayland implementation that functions as a base for several compositors

Some notable Wayland compositors are:
* Westonan implementation from the Wayland development team. Weston implements client side decorations.
* Enlightenment claimed full Wayland support since version 0.20 but work is currently underway to land a complete Wayland compositor
* KWin has nearly complete Wayland support as of 2021
* Mutter maintained a separate branch for the integration of Wayland for GNOME 3.9 (in September 2013); in the 3.13.1 release in 2014, the Wayland branch was merged into the main repository.
* Clayland – a simple example Wayland compositor using Clutter
* Sway – a tiling Wayland compositor, based on wlroots; it is a drop-in replacement for the i3 X11 window manager.
* Hyprlandan independent tiling Wayland compositor written in C++. Noteworthy features of Hyprland include dynamic tiling, tabbed windows, a clean and readable C++ code-base, and a custom renderer that provides window animations, rounded corners, and Dual-Kawase Blur on transparent windows.
* Woodlandwlroots-based window-stacking compositor for Wayland written in C, inspired by TinyWL and focused on simplicity and stability.
* labwca wlroots-based window-stacking compositor for Wayland, inspired by Openbox. It follows a similar approach and coding style to Sway.

Weston

Weston is a Wayland compositor previously developed as the reference implementation of the protocol by the Wayland project. It is written in C and released under the MIT License.

Weston officially supports only Linux due to dependencies on kernel-specific features such as kernel mode-setting (KMS), the Graphics Execution Manager (GEM), and udev. On Linux, it handles input via evdev and buffer management via Generic Buffer Management (GBM). A prototype port for FreeBSD was announced in 2013.

The compositor supports High-bandwidth Digital Content Protection (HDCP) and uses GEM to share buffers between applications and the compositor. It features a plug-in architecture with "shells" that provide elements like docks and panels. Applications are responsible for rendering their own window decorations.

Weston supports rendering via OpenGL ES or the pixman library for software rendering. The full OpenGL stack is avoided to prevent pulling in GLX and other X Window System dependencies.

A remote desktop interface for Weston was proposed in 2013 by a developer from RealVNC.

Maynard

''Maynard'' is a graphical shell and has been written as a plug-in for Weston, just as the GNOME Shell has been written as a plug-in to Mutter.

The Raspberry Pi in collaboration with Collabora released Maynard.

libinput

The Weston code for handling input devices (keyboards, pointers, touch screens, etc.) was split into its own separate library, called ''libinput'', for which support was first merged in Weston 1.5.

Libinput handles input devices for multiple Wayland compositors and also provides a generic X.Org Server input driver. It aims to provide one implementation for multiple Wayland compositors with a common way to handle input events while minimizing the amount of custom input code compositors need to include. libinput provides device detection (via udev), device handling, input device event processing and abstraction.

Version 1.0 of libinput followed version 0.21, and included support for tablets, button sets and touchpad gestures. This version will maintain stable API/ABI.

As GNOME/GTK and KDE Frameworks 5 have mainlined the required changes, Fedora 22 will replace X.Org's evdev and Synaptics drivers with libinput.

With version 1.16, the X.Org Server obtained support for the libinput library in form of a wrapper called .

Wayland Security Module

Wayland Security Module is a proposition that resembles the Linux Security Module interface found in the Linux kernel.

Some applications (especially the ones related to accessibility) require privileged capabilities that should work across different Wayland compositors. Currently, applications under Wayland are generally unable to perform any sensitive tasks such as taking screenshots or injecting input events without going throug
xdg-desktop-portal
or obtaining privileged access to the system.

Wayland Security Module is a way to delegate security decisions within the compositor to a centralized security decision engine.

Adoption

The Wayland protocol is designed to be simple so that additional protocols and interfaces need to be defined and implemented to achieve a holistic windowing system. these additional interfaces were being worked on. So, while the toolkits already fully support Wayland, the developers of the graphical shells are cooperating with the Wayland developers creating the necessary additional interfaces.

Desktop Linux distributions

most Linux distributions support Wayland out of the box. Some notable examples are:
* Debian ships Wayland as the default session for GNOME since version 10 (Buster), released 6 July 2019.
* Fedora starting with version 25 (released 22 November 2016) uses Wayland for the default GNOME 3.22 desktop session, with X.Org as a fallback if the graphics driver cannot support Wayland. Fedora uses Wayland as the default for KDE desktop session starting with version 34 (released 27 April 2021)
* Manjaro ships Wayland as default in the Gnome edition of Manjaro 20.2 (Nibia) (released 22 November 2020).
* Raspberry Pi OS, a port of Debian, has offered the option to use Wayland since version 11 (Bullseye) was released on 3 December 2021 and it became the default in version 12 (Bookworm) released on 10 October 2023.
* RebeccaBlackOS is a live USB Debian-based Linux distribution that allows a convenient way to try out a real Wayland desktop without having to make any modifications to the main operating system of the computer. It has been used since as early as 2012 to showcase Wayland.
* Red Hat Enterprise Linux ships Wayland as the default session in version 8, released 7 May 2019.
* Ubuntu shipped with Wayland by default in Ubuntu 17.10 (Artful Aardvark). However, Ubuntu 18.04 LTS reverted to X.Org by default due to several issues. Since Ubuntu 21.04, Wayland is the default again.
* Slackware Linux included Wayland on 20 February 2020 for the development version, -current, which became version 15.0.

Toolkit support

Toolkits supporting Wayland include the following:
* Clutter has complete Wayland support.
* EFL has complete Wayland support, except for selection.
* GTK 3.20 has complete Wayland support.
* Qt 5 has complete Wayland support, and can be used to write both Wayland compositors and Wayland clients.
* SDL support for Wayland debuted with the 2.0.2 release and was enabled by default since version 2.0.4.
* GLFW 3.2 has Wayland support.
* FreeGLUT has initial Wayland support.
* FLTK supports Wayland since version 1.4.0 (Nov. 2024).

Desktop environments

Desktop environments in the process of being ported from X to Wayland include GNOME, KDE Plasma 6 and Enlightenment.

In November 2015, Enlightenment e20 was announced with full Wayland support. GNOME 3.20 was the first version to have a full Wayland session. GNOME 3.22 included much improved Wayland support across GTK, Mutter, and GNOME Shell. GNOME 3.24 shipped support for the proprietary Nvidia drivers under Wayland.

Wayland support for KDE Plasma was delayed until the release of Plasma 5, though previously KWin 4.11 got an experimental Wayland support. The version 5.4 of Plasma was the first with a Wayland session. During 2020 Klipper was ported to Wayland and Plasma 5.20, released in October 2020, improved screen casting and recording. In Plasma 6, the default graphical session that uses Wayland was set as the default, making the X11 session secondary.

Other software

Other software supporting Wayland includes the following:
* Intelligent Input Bus is working on Wayland support, it could be ready for Fedora 22.
* RealVNC published a Wayland developer preview in July 2014.

wayvnc
is a VNC server for wlroots-based Wayland compositors.
* Maliit is an input method framework that runs under Wayland.
* kmscon supports Wayland with wlterm.
* Mesa has Wayland support integrated.
* Eclipse was made to run on Wayland during a GSoC-Project in 2014.
* The Vulkan WSI (Window System Interface) is a set of API calls that serve a similar purpose as EGL does for OpenGL & OpenGL ES or GLX for OpenGL on X11. Vulkan WSI includes support for Wayland from day one: VK_USE_PLATFORM_WAYLAND_KHR. Vulkan clients can run on unmodified Wayland servers, including Weston, GENIVI LayerManager, Mutter / GNOME Shell, Enlightenment, and more. The WSI allows applications to discover the different GPUs on the system, and display the results of GPU rendering to a window system.
* Waydroid (formerly called Anbox-Halium), a container for Android applications to run on Linux distributions using Wayland.

Mobile and embedded hardware

Mobile and embedded hardware supporting Wayland includes the following:

* postmarketOS
* GENIVI Alliance: The GENIVI Aliance, now COVESA, for in-vehicle infotainment (IVI) supports Wayland.
* Jolla: Smartphones from Jolla use Wayland. It is also used as standard when Linux Sailfish OS is used with hardware from other vendors or when it is installed into Android devices by users.
* Tizen: Tizen up to 2.x supports Wayland in in-vehicle infotainment (IVI) setups and from 3.0 onward defaults to Wayland.

History

Kristian Høgsberg, a Linux graphics and X.Org developer who previously worked on AIGLX and DRI2, started Wayland as a spare-time project in 2008 while working for Red Hat. His stated goal was a system in which "every frame is perfect, by which I mean that applications will be able to control the rendering enough that we'll never see tearing, lag, redrawing or flicker." Høgsberg was driving through the town of Wayland, Massachusetts when the underlying concepts "crystallized", hence the name (Weston and Maynard are also nearby towns in the same area, continuing the reference).

In October 2010, Wayland became a freedesktop.org project. As part of the migration the prior Google Group was replaced by the ''wayland-devel'' mailing list as the project's central point of discussion and development.

The Wayland client and server libraries were initially released under the MIT License, while the reference compositor Weston and some example clients used the GNU General Public License version 2. Later all the GPL code was relicensed under the MIT license "to make it easier to move code between the reference implementation and the actual libraries". In 2015 it was discovered that the license text used by Wayland was a slightly different and older version of the MIT license, and the license text was updated to the current version used by the X.Org project (known as MIT Expat License).

Wayland works with all Mesa-compatible drivers with DRI2 support as well as Android drivers via the Hybris project.

Releases

See also

* Mir (software)
* X Window System

References

External links

*

{{Desktop environments and window managers for X11 and Wayland

Collabora
Free software programmed in C
Software using the MIT license