Wayland (protocol)

[[File:Wayland display server protocol.svg|thumb|right|upright=1.6|{{ordered list

| The evdev module of the Linux kernel gets an event and sends it to the Wayland compositor.

| The Wayland compositor looks through its scenegraph to determine which window should receive the event. The scenegraph corresponds to what is on screen and the Wayland compositor understands the transformations that it may have applied to the elements in the scenegraph. Thus, the Wayland compositor can pick the right window and transform the screen coordinates to window local coordinates, by applying the inverse transformations. The types of transformation that can be applied to a window is only restricted to what the compositor can do, as long as it can compute the inverse transformation for the input events.

| As in the X case, when the client receives the event, it updates the UI in response. But in the Wayland case, the rendering happens by the client via EGL, and the client just sends a request to the compositor to indicate the region that was updated.

| The Wayland compositor collects damage requests from its clients and then re-composites the screen. The compositor can then directly issue an ioctl to schedule a pageflip with KMS.}}]]

The Wayland Display Server project was started by Red Hat developer Kristian Høgsberg in 2008.{{cite web|url=https://www.phoronix.com/scan.php?page=article&item=wayland_q209&num=1|title=The State Of The Wayland Display Server|author=Michael Larabel|date=20 May 2009|work=Phoronix|access-date=17 October 2021|archive-date=17 October 2021|archive-url=https://web.archive.org/web/20211017212244/https://www.phoronix.com/scan.php?page=article&item=wayland_q209&num=1|url-status=live}}

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".{{r|Corbet 2010}}

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

{{blockquote|What's different now is that a lot of infrastructure has moved from the X server into the kernel (memory management, command scheduling, mode setting) or libraries (cairo, pixman, freetype, fontconfig, pango, etc.), and there is very little left that has to happen in a central server process. ... [An X server has] a tremendous amount of functionality that you must support to claim to speak the X protocol, yet nobody will ever use this. ... This includes code tables, glyph rasterization and caching, XLFDs (seriously, XLFDs!), and the entire core rendering API that lets you draw stippled lines, polygons, wide arcs and many more state-of-the-1980s style graphics primitives. For many things we've been able to keep the X.org server modern by adding extension such as XRandR, XRender and COMPOSITE ... With Wayland we can move the X server and all its legacy technology to an optional code path. Getting to a point where the X server is a compatibility option instead of the core rendering system will take a while, but we'll never get there if [we] don't plan for it.}}

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.{{r|Høgsberg remotewl}}

It was attempted as a Google Summer of Code project in 2011, but was not successful.{{r|Larabel 2011 remote}}

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).{{r|Jackson remotewl}} As of early 2013, Høgsberg was experimenting with network transparency using a proxy Wayland server which sends compressed images to the real compositor.{{r|Stone 2013 LCA}}{{r|Willis 2013}} In August 2017, GNOME saw the first such pixel-scraping VNC server implementation under Wayland.{{r|GNOME Remote Desktop}} In modern Wayland compositors, network transparency is handled in an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] that implements the RemoteDesktop portal.

Many Wayland compositors also include an [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal implementation] for common tasks such as a native file picker for native applications and sandboxes such as Flatpak ([https://github.com/flatpak/xdg-desktop-portal-gtk 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.

File:Wayland protocol architecture.svg

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:{{r|hellowl}}

• A low-level layer or wire protocol that handles the inter-process communication between the two involved processes{{mdashb}}client and compositor{{mdashb}}and 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.{{cite web |url=https://wayland.freedesktop.org/docs/html/ch04.html#sect-Protocol-Wire-Format |title=Chapter 4. Wayland Protocol and Model of Operation |at=Wire Format |work=The Wayland Protocol |last=Høgsberg |first=Kristian}}
• 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".{{cite web |url=https://wayland.freedesktop.org/docs/html/ch04.html#sect-Protocol-Basic-Principles |title=Chapter 4. Wayland Protocol and Model of Operation |at=Basic Principles |work=The Wayland Protocol |last=Høgsberg |first=Kristian}}

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.{{r|wlprotoxml}} 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.{{cite web |url=https://wayland.freedesktop.org/docs/html/apb.html#id-1.10.2 |title=Appendix B. Client API |at=Introduction |work=The Wayland Protocol |last=Høgsberg |first=Kristian}}

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.{{r|Paalanen 2014}}

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.{{cite web |url=https://wayland.freedesktop.org/docs/html/ch04.html#sect-Protocol-Interfaces |title=Chapter 4. Wayland Protocol and Model of Operation |at=Interfaces |work=The Wayland Protocol |last=Høgsberg |first=Kristian}} 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.{{cite web |url=https://wayland.freedesktop.org/docs/html/ch04.html#sect-Protocol-Versioning |title=Chapter 4. Wayland Protocol and Model of Operation |at=Versioning |work=The Wayland Protocol |last=Høgsberg |first=Kristian}}

The interfaces of the current version of Wayland protocol are defined in the file {{mono|protocol/wayland.xml}} of the Wayland source code.{{r|wlprotoxml}} 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{{snd}} the core global object, a special object to encapsulate the Wayland protocol itself
• wl_registry{{snd}} the global registry object, in which the compositor registers all the global objects that it wants to be available to all clients
• wl_compositor{{snd}} an object that represents the compositor, and is in charge of combining the different surfaces into one output
• wl_surface{{snd}} an object representing a rectangular area on the screen, defined by a location, size and pixel content
• wl_buffer{{snd}} an object that, when attached to a wl_surface object, provides its displayable content
• wl_output{{snd}} an object representing the displayable area of a screen
• wl_pointer, wl_keyboard, wl_touch{{snd}} objects representing different input devices like pointers or keyboards
• wl_seat{{snd}} 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.{{r|Paalanen 2014}}

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{{r|wayland 1.4}}).

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 {{mono|libwayland-client}}. An implementation of the xdg-shell protocol, on the contrary, is supposed to be provided by the Wayland compositor. So you will find the {{mono|xdg-shell-client-protocol.h}} 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.{{r|xdg-shell}}

IVI-Shell is an extension to the Wayland core protocol, targeting in-vehicle infotainment (IVI) devices.{{cite web|url=https://github.com/GENIVI/wayland-ivi-extension|title=GENIVI/wayland-ivi-extension|website=GitHub|date=17 November 2021|access-date=17 August 2016|archive-date=24 March 2017|archive-url=https://web.archive.org/web/20170324145817/https://github.com/GENIVI/wayland-ivi-extension|url-status=live}}

File:The Linux Graphics Stack and glamor.svg and its clients use EGL to draw directly into the framebuffer; X.Org Server with XWayland and Glamor.]]

The Wayland protocol does not include a rendering API.{{cite web |url=https://wayland.freedesktop.org/docs/html/ch03.html#sect-Wayland-Architecture-wayland_architecture |title=Chapter 3. Wayland Architecture |at=X vs. Wayland Architecture |work=The Wayland Protocol |last=Høgsberg |first=Kristian}}{{r|Wayland FAQ}}{{r|Vervloesem 2012}}{{r|Barnes slides|p=2}} Instead, Wayland follows a direct rendering model, in which the client must render the window contents to a buffer shareable with the compositor.{{cite web |url=https://wayland.freedesktop.org/docs/html/ch03.html#sect-Wayland-Architecture-wayland_rendering |title=Chapter 3. Wayland Architecture |at=Wayland Rendering |work=The Wayland Protocol |last=Høgsberg |first=Kristian}} 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{{cite web |url=https://wayland.freedesktop.org/docs/html/apa.html#protocol-spec-wl_shm |title=Appendix A. Wayland Protocol Specification |at=wl_shm - shared memory support |work=The Wayland Protocol |last=Høgsberg |first=Kristian}} and wl_shm_pool{{cite web |url=https://wayland.freedesktop.org/docs/html/apa.html#protocol-spec-wl_shm_pool |title=Appendix A. Wayland Protocol Specification |at=wl_shm_pool - a shared memory pool |work=The Wayland Protocol |last=Høgsberg |first=Kristian}} 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.{{r|Paalanen 2012}} 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.{{r|hellowl}} 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.{{r|Wayland doc|page=7}} The procedure used for rendering, including the number of buffers involved and their management, is entirely under the client control.{{r|Wayland doc|page=7}}

{{See also|Mir (software)#Software architecture|label 1=Mir software architecture}}

There are several differences between Wayland and X with regard to performance, code maintainability, and security:{{r|Griffith 2013}}

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

; 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.{{r|Wayland Compositor|pages=8-11}}

; 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.).{{r|Wayland architecture}}{{r|Vervloesem 2012}} 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-in [https://wayland.app/protocols/xdg-decoration-unstable-v1 xdg-decoration] protocol, if the compositor chooses to implement such functionality.{{r|Graesslin 2013 decorations}}

; 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,{{r|Kerrisk 2012}}{{r|Peres 2014}}{{r|Graesslin 2015 security}} although some extensions have been developed trying to mitigate it.{{r|X.Org Security}}{{r|X11 Security extension}}{{r|XACE}}

: Also, with the vast majority of the code running in the client, less code needs to run with root privileges, improving security,{{r|Kerrisk 2012}} although multiple popular Linux distributions now allow the X server to be run without root privileges.{{cite web|url=https://www.phoronix.com/scan.php?page=news_item&px=Debian-Non-Root-X|title=Debian Moves To Non-Root X.Org Server By Default - Phoronix|website=www.phoronix.com|access-date=2 April 2018|archive-date=2 April 2018|archive-url=https://web.archive.org/web/20180402225807/https://www.phoronix.com/scan.php?page=news_item&px=Debian-Non-Root-X|url-status=live}}{{cite web|url=https://wiki.gentoo.org/wiki/Non_root_Xorg|title=Non root Xorg - Gentoo Wiki|website=wiki.gentoo.org|access-date=2 April 2018|archive-date=2 April 2018|archive-url=https://web.archive.org/web/20180402163248/https://wiki.gentoo.org/wiki/Non_root_Xorg|url-status=live}}{{cite web|url=https://wiki.ubuntu.com/X/Rootless|title=X/Rootless - Ubuntu Wiki|website=wiki.ubuntu.com|access-date=2 April 2018|archive-date=2 April 2018|archive-url=https://web.archive.org/web/20180402225623/https://wiki.ubuntu.com/X/Rootless|url-status=live}}{{cite web|url=https://bugzilla.redhat.com/show_bug.cgi?id=1078902|title=1078902 – Xorg without root rights|website=bugzilla.redhat.com|access-date=2 April 2018|archive-date=2 April 2018|archive-url=https://web.archive.org/web/20180402225512/https://bugzilla.redhat.com/show_bug.cgi?id=1078902|url-status=live}}

; 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;{{r|Wayland FAQ}} 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.{{r|Willis 2013}}

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.{{r|xwayland}} 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.{{r|xorg 1.16}}

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

{{Main|List of display servers#Wayland|l1=List of Wayland compositors}}

File:Window (windowing system).svg. The Wayland protocol does not specify what software is responsible for rendering the window decoration.{{r|Graesslin 2013 decorations}}]]

File:KDE Plasma 5.24 on Arch Linux screenshot.png|thumb]]

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{{cite web|url=https://gitlab.freedesktop.org/wlroots/wlroots/-/blob/master/README.md|title=README.md|work=wlroots project on GitLab|date=2 February 2023 }}

Some notable Wayland compositors are:

• Weston{{snd}}an implementation from the Wayland development team. Weston implements client side decorations.
• Enlightenment claimed full Wayland support since version 0.20{{r|Larabel 2015 e20}} but work is currently underway to land a complete Wayland compositor{{Cite web|url=https://www.enlightenment.org/about-wayland|title=Wayland|website=www.enlightenment.org|access-date=8 March 2016|archive-date=9 March 2016|archive-url=https://web.archive.org/web/20160309102604/https://www.enlightenment.org/about-wayland|url-status=live}}
• KWin has nearly complete Wayland support as of 2021{{Cite web|date=2021-02-16|title=Plasma 5.21|url=https://kde.org/announcements/plasma/5/5.21.0/|access-date=2021-03-09|website=KDE Community|language=en|archive-date=8 March 2021|archive-url=https://web.archive.org/web/20210308140934/https://kde.org/announcements/plasma/5/5.21.0/|url-status=live}}
• Mutter maintained a separate branch for the integration of Wayland for GNOME 3.9 (in September 2013);{{r|mutter wayland}} in the 3.13.1 release in 2014, the Wayland branch was merged into the main repository.{{cite web |url=https://gitlab.gnome.org/GNOME/mutter/-/commit/a7665a3e05bdbfa5540dc1ea92bac10517909d15 |title=Bump version to 3.13.1|date=30 April 2014}}
• 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.{{cite web|url=https://swaywm.org/|title=Sway|website=swaywm.org|access-date=2018-12-20|archive-date=20 December 2018|archive-url=https://web.archive.org/web/20181220230525/https://swaywm.org/|url-status=live}}{{cite web |title=swaywm/wlroots |url=https://github.com/swaywm/wlroots |access-date=2018-10-28 |website=GitHub |language=en |archive-date=19 December 2018 |archive-url=https://web.archive.org/web/20181219001720/https://github.com/swaywm/wlroots |url-status=live}}{{cite web |title=swaywm/sway |url=https://github.com/swaywm/sway |access-date=2018-10-28 |website=GitHub |language=en |archive-date=28 August 2019 |archive-url=https://web.archive.org/web/20190828153524/https://github.com/swaywm/sway |url-status=live}}
• Hyprland{{snd}}an 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.{{Cite web |title=Hyprland - ArchWiki |url=https://wiki.archlinux.org/title/Hyprland |access-date=2024-01-28 |website=wiki.archlinux.org}}{{Cite web |title=Hyprland: Dynamic tiling window compositor with the looks |url=https://hyprland.org/ |access-date=2024-01-28 |website=hyprland.org |language=en}}
• Woodland{{snd}}wlroots-based window-stacking compositor for Wayland written in C, inspired by TinyWL and focused on simplicity and stability.
• labwc{{snd}}a wlroots-based window-stacking compositor for Wayland, inspired by Openbox. It follows a similar approach and coding style to Sway.{{Cite web |title=labwc |url=https://labwc.github.io/ |access-date=2025-05-28 |website=labwc.github.io |language=en}}

Weston is a Wayland compositor previously developed as the reference implementation of the protocol by the Wayland project.{{cite web |last1=Ser |first1=Simon |title=Remove "the reference Wayland compositor" |url=https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1014 |website=FreeDesktop GitLab |access-date=14 May 2025}}{{cite web |url=https://gitlab.freedesktop.org/wayland/weston/-/raw/main/README.md |title=README |website=gitlab.freedesktop.org |access-date=4 August 2024}} 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.{{r|Larabel 2013 freebsd}}

The compositor supports High-bandwidth Digital Content Protection (HDCP){{cite web|url=https://gitlab.freedesktop.org/wayland/weston/merge_requests/48/diffs?commit_id=05dc6b86431fe040f91ca7b4cf122fa9dc4dd8dd|title=Adding Content protection support in drm-backend (!48) · Merge Requests · wayland / weston|website=GitLab|date=6 November 2018 |language=en|access-date=2019-10-27|archive-date=27 August 2022|archive-url=https://web.archive.org/web/20220827010905/https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/48/diffs?commit_id=05dc6b86431fe040f91ca7b4cf122fa9dc4dd8dd|url-status=live}} 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.{{r|Willis 2013}} Applications are responsible for rendering their own window decorations.

Weston supports rendering via OpenGL ES{{r|Paalanen 2012 EGL}} or the pixman library for software rendering.{{r|Larabel 2013 pixman}} The full OpenGL stack is avoided to prevent pulling in GLX and other X Window System dependencies.{{r|Høgsberg wayland GL}}

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

File:Maynard desktop.png

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.{{r|maynard}}

The Raspberry Pi in collaboration with Collabora released Maynard.{{r|Collabora RPi}}{{r|RPi wayland}}

{{Clear}}

File:Libinput for Wayland compositors.svg

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.{{r|wayland 1.5}}{{r|libinput announce}}

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{{clarify|reason=both input and output devices?|date=December 2016}} (via udev), device handling, input device event processing and abstraction.{{r|libinput}}{{r|XDC2014 libinput}}

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.{{r|libinput stable API}}

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

With version 1.16, the X.Org Server obtained support for the libinput library in form of a wrapper called {{mono|xf86-input-libinput}}.{{r|Hutterer 2014}}{{r|libinputfosdem15}}

{{Clear}}

Wayland Security Module is a proposition that resembles the Linux Security Module interface found in the Linux kernel.{{r|XDC2014 wayland security}}

Some applications (especially the ones related to accessibility) require privileged capabilities that should work across different Wayland compositors. Currently,{{When|date=October 2014}} applications under Wayland are generally unable to perform any sensitive tasks such as taking screenshots or injecting input events without going through [https://github.com/flatpak/xdg-desktop-portal 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.{{r|XDC2014 wayland security}}

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. {{As of|July 2014}} 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.

{{As of|2020}} 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.{{cite web|url=https://wiki.debian.org/NewInBuster|title=NewInBuster - Debian Wiki|website=wiki.debian.org|access-date=2019-07-15|archive-date=25 September 2019|archive-url=https://web.archive.org/web/20190925065917/https://wiki.debian.org/NewInBuster|url-status=live}}
• 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.{{Cite web |title=Changes/WaylandByDefault - Fedora Project Wiki |url=https://fedoraproject.org/wiki/Changes/WaylandByDefault |access-date=2020-11-09 |website=fedoraproject.org |archive-date=27 December 2015 |archive-url=https://web.archive.org/web/20151227103524/https://fedoraproject.org/wiki/Changes/WaylandByDefault |url-status=live}} 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).{{cite web |title=Manjaro 20.2 Nibia got released |date=3 December 2020 |url=https://forum.manjaro.org/t/manjaro-20-2-nibia-got-released/41034 |access-date=3 December 2020 |archive-date=4 December 2020 |archive-url=https://web.archive.org/web/20201204122710/https://forum.manjaro.org/t/manjaro-20-2-nibia-got-released/41034 |url-status=live}}
• 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{{cite web|url=https://www.phoronix.com/scan.php?page=news_item&px=RBOS-2016-02-08|title=Wayland Live OS Is Now Based On Debian Testing, Working KDE Wayland Support|publisher=Phoronix|access-date=14 January 2020|archive-date=11 August 2019|archive-url=https://web.archive.org/web/20190811055252/https://www.phoronix.com/scan.php?page=news_item&px=RBOS-2016-02-08|url-status=live}} 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.{{cite web|url=https://sourceforge.net/projects/rebeccablackos/|title=RebeccaBlackOS|publisher=Sourceforge|access-date=11 October 2016|archive-date=25 November 2016|archive-url=https://web.archive.org/web/20161125215104/https://sourceforge.net/projects/rebeccablackos/|url-status=live}} It has been used since as early as 2012 to showcase Wayland.{{cite web|url=https://www.phoronix.com/scan.php?page=news_item&px=MTA3Njk|title=Trying Out Wayland With Rebecca Black|publisher=Phoronix|access-date=14 January 2020|archive-date=18 May 2020|archive-url=https://web.archive.org/web/20200518210256/https://www.phoronix.com/scan.php?page=news_item&px=MTA3Njk|url-status=live}}{{cite web|url=https://www.phoronix.com/scan.php?page=news_item&px=MTUzNTU|title=New Wayland Live CD Has A Lot Of Features|publisher=Phoronix|access-date=14 January 2020|archive-date=18 May 2020|archive-url=https://web.archive.org/web/20200518212840/https://www.phoronix.com/scan.php?page=news_item&px=MTUzNTU|url-status=live}}
• Red Hat Enterprise Linux ships Wayland as the default session in version 8, released 7 May 2019.{{cite web|url=https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.0_release_notes/rhel-8_0_0_release#desktop|title=Release notes for Red Hat Enterprise Linux 8.0|website=Red Hat Customer Portal|language=en|access-date=2020-12-25|archive-date=25 November 2020|archive-url=https://web.archive.org/web/20201125003517/https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.0_release_notes/rhel-8_0_0_release#desktop|url-status=live}}
• Ubuntu shipped with Wayland by default in Ubuntu 17.10 (Artful Aardvark).{{cite web|url=https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes#Ubuntu_Desktop|title=ReleaseNotes for Ubuntu 17.10|publisher=Canonical|access-date=10 November 2017|archive-date=24 November 2017|archive-url=https://web.archive.org/web/20171124175600/https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes#Ubuntu_Desktop|url-status=live}} However, Ubuntu 18.04 LTS reverted to X.Org by default due to several issues.{{cite web|url=https://www.neowin.net/news/ubuntu-1804-will-revert-to-long-in-the-tooth-xorg/|title=Ubuntu 18.04 will revert to long-in-the-tooth Xorg|access-date=16 December 2023}}{{cite web|url=https://insights.ubuntu.com/2018/01/26/bionic-beaver-18-04-lts-to-use-xorg-by-default/|title=Bionic Beaver 18.04 LTS to use Xorg by default|publisher=Canonical|access-date=18 February 2018|archive-date=18 February 2018|archive-url=https://web.archive.org/web/20180218211218/https://insights.ubuntu.com/2018/01/26/bionic-beaver-18-04-lts-to-use-xorg-by-default/|url-status=live}} Since Ubuntu 21.04, Wayland is the default again.{{cite web|title=Ubuntu 21.04 is here|url=https://ubuntu.com/blog/ubuntu-21-04-is-here|url-status=live|archive-url=https://web.archive.org/web/20210422140245/https://ubuntu.com//blog/ubuntu-21-04-is-here|archive-date=22 April 2021|access-date=14 June 2021|website=Canonical Ubuntu Blog}}
• Slackware Linux included Wayland on 20 February 2020{{cite web|url=http://www.slackware.com/changelog/current.php?cpu=x86_64|title=Slackware ChangeLogs|publisher=Slackware Linux|access-date=2020-02-26|archive-date=30 January 2020|archive-url=https://web.archive.org/web/20200130153903/http://www.slackware.com/changelog/current.php?cpu=x86_64|url-status=live}} for the development version, -current, which became version 15.0.

Toolkits supporting Wayland include the following:

• Clutter has complete Wayland support.{{r|clutter 1.6}}{{r|Bradford 2011}}{{r|clutter 1.16}}
• EFL has complete Wayland support, except for selection.{{r|efl wayland}}
• GTK 3.20 has complete Wayland support.{{r|gtk+ wayland}}
• 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{{r|sdl2 wayland}} and was enabled by default since version 2.0.4.{{r|Larabel 2016 SDL2}}
• GLFW 3.2 has Wayland support.{{r|glfw wayland}}
• FreeGLUT has initial Wayland support.{{r|freeglut wayland}}
• FLTK supports Wayland since version 1.4.0 (Nov. 2024).{{cite web |last1=S |first1=A |title=FLTK 1.4.0-1 released on Nov. 18, 2024 |url=https://www.fltk.org/articles.php?L1955 |website=FLTK |publisher=AlbrechtS}}

Desktop environments in the process of being ported from X to Wayland include GNOME,{{r|GNOME wl}} KDE Plasma 6{{r|KDE wl}} and Enlightenment.{{r|enlightenment wl}}

In November 2015, Enlightenment e20 was announced with full Wayland support.{{r|e20 wl}}{{r|Larabel 2015 e20}}{{r|FOSDEM2016 wl}} GNOME 3.20 was the first version to have a full Wayland session.{{r|GNOME release plan}} GNOME 3.22 included much improved Wayland support across GTK, Mutter, and GNOME Shell.{{cite web|url=https://www.phoronix.com/scan.php?page=article&item=gnome-322-features&num=1|title=A Look At The Exciting Features/Improvements Of GNOME 3.22|publisher=Phoronix|access-date=14 January 2020|archive-date=12 August 2020|archive-url=https://web.archive.org/web/20200812095126/https://www.phoronix.com/scan.php?page=article&item=gnome-322-features&num=1|url-status=live}} GNOME 3.24 shipped support for the proprietary Nvidia drivers under Wayland.{{cite web|url=https://www.phoronix.com/scan.php?page=news_item&px=GNOME-Mutter-Mainline-EGLStream|title=GNOME Lands Mainline NVIDIA Wayland Support Using EGLStreams|publisher=Phoronix|access-date=14 January 2020|archive-date=8 August 2019|archive-url=https://web.archive.org/web/20190808131309/https://www.phoronix.com/scan.php?page=news_item&px=GNOME-Mutter-Mainline-EGLStream|url-status=live}}

Wayland support for KDE Plasma was delayed until the release of Plasma 5,{{r|vizzzion}} though previously KWin 4.11 got an experimental Wayland support.{{r|Larabel 2013 kwin}} The version 5.4 of Plasma was the first with a Wayland session.{{r|Graesslin 2015}} During 2020 Klipper was ported to Wayland and Plasma 5.20, released in October 2020, improved screen casting and recording.{{Cite web |last=Sneddon |first=Joey |date=2020-09-17 |title=KDE Plasma 5.20 Looks Like an Awesome Update |url=https://www.omgubuntu.co.uk/2020/09/kde-plasma-5-20-release-features |access-date=2024-06-14 |website=OMG! Ubuntu |language=en-GB}}{{Cite web |last=Nestor |first=Marius |date=2020-10-13 |title=KDE Plasma 5.20 Desktop Environment Officially Released, Here's What's New |url=https://9to5linux.com/kde-plasma-5-20-desktop-environment-officially-released-heres-whats-new |access-date=2024-06-14 |website=9to5Linux |language=en-US}} In Plasma 6, the default graphical session that uses Wayland was set as the default, making the X11 session secondary.{{Cite web |last=Wallen |first=Jack |date=2024-02-14 |title=The first Linux distribution to deliver a pure KDE Plasma 6 environment is here |url=https://www.zdnet.com/article/the-first-linux-distribution-to-deliver-a-pure-kde-plasma-6-environment-is-here/ |access-date=2024-03-24 |website=ZDNET |language=en}}

Other software supporting Wayland includes the following:

• Intelligent Input Bus is working on Wayland support, it could be ready for Fedora 22.{{r|Schaller 2014}}
• RealVNC published a Wayland developer preview in July 2014.{{r|RealVNC remote}}{{r|autoref0005}}{{r|autoref0006}}
• [https://github.com/any1/wayvnc wayvnc] is a VNC server for wlroots-based Wayland compositors.
• Maliit is an input method framework that runs under Wayland.{{r|autoref0007}}{{r|autoref0008}}{{r|Maliit}}
• kmscon supports Wayland with wlterm.{{r|kmscon wl}}
• Mesa has Wayland support integrated.{{r|Hillesley 2012 p3}}
• Eclipse was made to run on Wayland during a GSoC-Project in 2014.{{r|eclipse wl}}
• 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.{{r|Collabora vulkan}}
• Waydroid (formerly called Anbox-Halium), a container for Android applications to run on Linux distributions using Wayland.

File:PostmarketOS and Weston compositor running on Motorola Moto G.jpg]]

Mobile and embedded hardware supporting Wayland includes the following:

• postmarketOS
• GENIVI Alliance: The GENIVI Aliance, now COVESA, for in-vehicle infotainment (IVI) supports Wayland.{{r|genivi}}
• 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.{{r|auto}}{{r|auto1}}{{r|auto2}}
• Tizen: Tizen up to 2.x supports Wayland in in-vehicle infotainment (IVI) setups{{r|tizen 2.0}} and from 3.0 onward defaults to Wayland.{{r|tizen 3.0}}{{cite web

|url = https://arstechnica.com/gadgets/2017/05/the-samsung-z4-is-tizens-new-flagship-smartphone/

|title = The Samsung Z4 is Tizen's new flagship smartphone

|last = Amadeo

|first = Ron

|work = Ars Technica

|date = 12 May 2017

|access-date = 13 May 2017

|archive-date = 13 May 2017

|archive-url = https://web.archive.org/web/20170513000659/https://arstechnica.com/gadgets/2017/05/the-samsung-z4-is-tizens-new-flagship-smartphone/

|url-status = live

}}

{{Clear}}

File:Linux graphics drivers DRI Wayland.svg over EGL.]]

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.{{r|Høgsberg 2008}}{{r|FOSDEM2012 interview}}{{r|Hillesley 2012}}{{r|LPC2009}} 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).{{r|Hillesley 2012}}{{r|Jenkins 2011}}

In October 2010, Wayland became a freedesktop.org project.{{r|Larabel 2010 freedesktop}}{{r|wayland freedesktop}} 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,{{r|original license}} while the reference compositor Weston and some example clients used the GNU General Public License version 2.{{r|license clarification}} 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".{{r|license change GPL}} 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).{{r|License}}

Wayland works with all Mesa-compatible drivers with DRI2 support{{r|Hillesley 2012 p3}} as well as Android drivers via the Hybris project.{{r|wayland part1}}{{r|wayland part2}}{{r|Larabel 2013 Jolla}}

{{Portal|Free and open-source software}}

• Mir (software)
• X Window System

{{reflist|refs=

{{cite web|url=https://gitlab.freedesktop.org/wayland/wayland/-/blob/main/COPYING|title=wayland/wayland: root/COPYING|website=gitlab.freedesktop.org|date=9 June 2015 |access-date=4 August 2024}}

{{cite web|title=Wayland|url=https://wayland.freedesktop.org/|website=Wayland project|access-date=9 May 2016|archive-date=2 March 2011|archive-url=https://web.archive.org/web/20110302122757/http://wayland.freedesktop.org/|url-status=live}}

{{cite web|title=Wayland FAQ|url=https://wayland.freedesktop.org/faq.html|website=Wayland project|access-date=9 May 2016|archive-date=2 April 2016|archive-url=https://web.archive.org/web/20160402202316/https://wayland.freedesktop.org/faq.html|url-status=live}}

{{cite web|title=Wayland Architecture|url=https://wayland.freedesktop.org/architecture.html|website=Wayland project|access-date=9 May 2016|archive-date=13 March 2016|archive-url=https://web.archive.org/web/20160313044952/https://wayland.freedesktop.org/architecture.html|url-status=live}}

{{cite web|title=X Clients under Wayland (XWayland)|url=https://wayland.freedesktop.org/xserver.html|publisher=Wayland project|access-date=18 July 2014|archive-date=27 August 2022|archive-url=https://web.archive.org/web/20220827010905/https://wayland.freedesktop.org/xserver.html|url-status=live}}

{{cite web|url=https://wayland.freedesktop.org/releases.html|title=Wayland|publisher=Wayland.freedesktop.org|access-date=15 July 2013|archive-date=7 July 2013|archive-url=https://web.archive.org/web/20130707081706/http://wayland.freedesktop.org/releases.html|url-status=live}}

{{cite web|last1=Høgsberg|first1=Kristian|title=protocol/wayland.xml|url=https://gitlab.freedesktop.org/wayland/wayland/-/blob/main/protocol/wayland.xml|website=gitlab.freedesktop.org|date=8 May 2024 |access-date=5 August 2024}}

{{cite web|last1=Høgsberg|first1=Kristian|title=Wayland Documentation 1.3|url=https://wayland.freedesktop.org/docs/pdf/Documentation-1.3-Wayland-en-US.pdf|access-date=16 March 2016|archive-date=10 September 2015|archive-url=https://web.archive.org/web/20150910045252/http://wayland.freedesktop.org/docs/pdf/Documentation-1.3-Wayland-en-US.pdf|url-status=live}}

{{cite web|last1=Bradford|first1=Rob|title=Clutter & Cogl Wayland update|url=http://www.robster.org.uk/2011/12/16/clutter-cogl-wayland-update/|archive-url=https://web.archive.org/web/20160310025835/http://www.robster.org.uk/2011/12/16/clutter-cogl-wayland-update/|url-status=dead|archive-date=10 March 2016|date=16 December 2011|access-date=9 March 2016|quote=The Clutter client side support is basically complete}}

{{cite web|last1=Corbet|first1=Jonathan|title=LPC: Life after X|url=https://lwn.net/Articles/413335/|website=LWN.net|date=5 November 2010|access-date=17 April 2016|archive-date=28 April 2016|archive-url=https://web.archive.org/web/20160428103400/https://lwn.net/Articles/413335/|url-status=live}}

{{cite web|last1=Edge|first1=Jake|title=LFCS 2012: X and Wayland|url=https://lwn.net/Articles/491509/|website=LWN.net|date=11 April 2012|access-date=17 April 2016|archive-date=30 April 2016|archive-url=https://web.archive.org/web/20160430024705/http://lwn.net/Articles/491509/|url-status=live}}

{{cite web|last1=Graesslin|first1=Martin|title=Client Side Window Decorations and Wayland|url=https://blog.martin-graesslin.com/blog/2013/02/client-side-window-decorations-and-wayland/|date=7 February 2013|access-date=17 April 2016|archive-date=13 April 2016|archive-url=https://web.archive.org/web/20160413200359/https://blog.martin-graesslin.com/blog/2013/02/client-side-window-decorations-and-wayland/|url-status=live}}

{{cite web|last1=Graesslin|first1=Martin|title=Four years later|url=https://blog.martin-graesslin.com/blog/2015/06/four-years-later/|date=29 June 2015|access-date=17 April 2016|archive-date=31 March 2016|archive-url=https://web.archive.org/web/20160331202154/http://blog.martin-graesslin.com/blog/2015/06/four-years-later/|url-status=live}}

{{cite web|last1=Graesslin|first1=Martin|title=Looking at the security of Plasma/Wayland|url=https://blog.martin-graesslin.com/blog/2015/11/looking-at-the-security-of-plasmawayland/|date=23 November 2015|access-date=18 April 2016|archive-date=27 August 2022|archive-url=https://web.archive.org/web/20220827010908/https://blog.martin-graesslin.com/blog/2015/11/looking-at-the-security-of-plasmawayland/|url-status=live}}

{{cite web|last1=Griffith|first1=Eric|title=The Wayland Situation: Facts About X vs. Wayland|url=https://www.phoronix.com/scan.php?page=article&item=x_wayland_situation|website=Phoronix.com|date=7 June 2013|access-date=17 April 2016|page=2|archive-date=24 September 2015|archive-url=https://web.archive.org/web/20150924091609/http://www.phoronix.com/scan.php?page=article&item=x_wayland_situation|url-status=live}}

{{cite web|last1=Hillesley|first1=Richard|title=Wayland - Beyond X|url=http://www.h-online.com/open/features/Wayland-Beyond-X-1432046.html|website=The H Open|publisher=Heise Media UK|date=13 February 2012|access-date=8 March 2016|archive-date=6 December 2013|archive-url=https://web.archive.org/web/20131206201020/http://www.h-online.com/open/features/Wayland-Beyond-X-1432046.html|url-status=dead}}

Hillesley, p. 3.

{{cite web|last1=Høgsberg|first1=Kristian|title=Premature publicity is better than no publicity|url=https://hoegsberg.blogspot.com/2008/11/premature-publicity-is-better-than-no.html|date=3 November 2008|access-date=6 April 2016|archive-date=28 March 2016|archive-url=https://web.archive.org/web/20160328164015/http://hoegsberg.blogspot.com/2008/11/premature-publicity-is-better-than-no.html|url-status=live}}

{{cite web|last1=Høgsberg|first1=Kristian|title=Multiple backends for GTK|url=https://hoegsberg.blogspot.com/2011/01/multiple-backends-for-gtk.html|date=3 January 2011|access-date=10 March 2016|archive-date=27 August 2022|archive-url=https://web.archive.org/web/20220827010908/https://hoegsberg.blogspot.com/2011/01/multiple-backends-for-gtk.html|url-status=live}}

{{cite web|last1=Hutterer|first1=Peter|title=libinput - a common input stack for Wayland compositors and X.Org drivers|url=https://who-t.blogspot.com/2014/09/libinput-common-input-stack-for-wayland.html|date=24 September 2014|access-date=17 April 2016|archive-date=7 April 2016|archive-url=https://web.archive.org/web/20160407130835/http://who-t.blogspot.com/2014/09/libinput-common-input-stack-for-wayland.html|url-status=live}}

{{cite web|last1=Jenkins|first1=Evan|title=The Linux graphics stack from X to Wayland|url=https://arstechnica.com/information-technology/2011/03/the-linux-graphics-stack-from-x-to-wayland/|website=Ars Technica|date=22 March 2011|access-date=17 April 2016|archive-date=10 April 2016|archive-url=https://web.archive.org/web/20160410131105/http://arstechnica.com/information-technology/2011/03/the-linux-graphics-stack-from-x-to-wayland/|url-status=live}}

{{cite web|last1=Kerrisk|first1=Michael|title=XDC2012: Graphics stack security|url=https://lwn.net/Articles/517375/|website=LWN.net|date=25 September 2012|access-date=13 April 2016|archive-date=28 March 2016|archive-url=https://web.archive.org/web/20160328041629/https://lwn.net/Articles/517375/|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=Wayland Becomes A FreeDesktop.org Project|url=https://www.phoronix.com/scan.php?page=news_item&px=ODczNQ|website=Phoronix.com|date=29 October 2010|access-date=17 April 2016|archive-date=14 April 2016|archive-url=https://web.archive.org/web/20160414125119/http://www.phoronix.com/scan.php?page=news_item&px=ODczNQ|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=Remote Wayland Server Project: Does It Work Yet?|url=https://www.phoronix.com/scan.php?page=news_item&px=OTgxMQ|website=Phoronix.com|date=18 August 2011|access-date=17 April 2016|archive-date=25 April 2016|archive-url=https://web.archive.org/web/20160425222517/https://www.phoronix.com/scan.php?page=news_item&px=OTgxMQ|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=A Software-Based Pixman Renderer For Wayland's Weston|url=https://www.phoronix.com/scan.php?page=news_item&px=MTI2Nzg|website=Phoronix.com|date=6 January 2013|access-date=17 April 2016|archive-date=25 April 2016|archive-url=https://web.archive.org/web/20160425225043/https://www.phoronix.com/scan.php?page=news_item&px=MTI2Nzg|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=Wayland Begins Porting Process To FreeBSD|url=https://www.phoronix.com/scan.php?page=news_item&px=MTMwMzE|website=Phoronix.com|date=16 February 2013|access-date=17 April 2016|archive-date=25 April 2016|archive-url=https://web.archive.org/web/20160425223407/https://www.phoronix.com/scan.php?page=news_item&px=MTMwMzE|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=Jolla Brings Wayland Atop Android GPU Drivers|url=https://www.phoronix.com/scan.php?page=news_item&px=MTM0OTE|website=Phoronix.com|date=11 April 2013|access-date=17 April 2016|archive-date=25 April 2016|archive-url=https://web.archive.org/web/20160425233250/https://www.phoronix.com/scan.php?page=news_item&px=MTM0OTE|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=Wayland 1.1 Officially Released With Weston 1.1|url=https://www.phoronix.com/scan.php?page=news_item&px=MTM1Mjk|website=Phoronix.com|date=16 April 2013|access-date=17 April 2016|archive-date=25 April 2016|archive-url=https://web.archive.org/web/20160425213252/https://www.phoronix.com/scan.php?page=news_item&px=MTM1Mjk|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=KDE 4.11 Beta Released, Works On Wayland|url=https://www.phoronix.com/scan.php?page=news_item&px=MTM4OTE|website=Phoronix.com|date=14 June 2013|access-date=17 April 2016|archive-date=25 April 2016|archive-url=https://web.archive.org/web/20160425231258/https://www.phoronix.com/scan.php?page=news_item&px=MTM4OTE|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=Wayland 1.2.0 Released, Joined By Weston Compositor|url=https://www.phoronix.com/scan.php?page=news_item&px=MTQwOTg|website=Phoronix.com|date=13 July 2013|access-date=17 April 2016|archive-date=14 April 2016|archive-url=https://web.archive.org/web/20160414124843/http://www.phoronix.com/scan.php?page=news_item&px=MTQwOTg|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=Wayland's MIT License To Be Updated/Corrected|url=https://www.phoronix.com/scan.php?page=news_item&px=Wayland-License-MIT-Update|website=Phoronix.com|date=10 June 2015|access-date=17 April 2016|archive-date=25 April 2016|archive-url=https://web.archive.org/web/20160425220839/https://www.phoronix.com/scan.php?page=news_item&px=Wayland-License-MIT-Update|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=Enlightenment 0.20 Arrives With Full Wayland Support & Better FreeBSD Support|url=https://www.phoronix.com/scan.php?page=news_item&px=Enlightenment-0.20-Released|website=Phoronix.com|date=30 November 2015|access-date=17 April 2016|archive-date=15 March 2016|archive-url=https://web.archive.org/web/20160315085313/http://www.phoronix.com/scan.php?page=news_item&px=Enlightenment-0.20-Released|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=SDL 2.0.4 Was Quietly Released Last Week With Wayland & Mir By Default|url=https://www.phoronix.com/scan.php?page=news_item&px=SDL-2.0.4-Released|website=Phoronix.com|date=9 January 2016|access-date=17 April 2016|archive-date=16 March 2016|archive-url=https://web.archive.org/web/20160316155452/http://www.phoronix.com/scan.php?page=news_item&px=SDL-2.0.4-Released|url-status=live}}

{{cite web|last1=Larabel|first1=Michael|title=Wayland 1.10 Officially Released|url=https://www.phoronix.com/scan.php?page=news_item&px=Wayland-1.10-Released|website=Phoronix.com|date=16 February 2016|access-date=17 April 2016|archive-date=21 June 2017|archive-url=https://web.archive.org/web/20170621204439/http://www.phoronix.com/scan.php?page=news_item&px=Wayland-1.10-Released|url-status=live}}

{{cite web|last1=Paalanen|first1=Pekka|title=What does EGL do in the Wayland stack|url=https://ppaalanen.blogspot.com/2012/03/what-does-egl-do-in-wayland-stack.html|date=10 March 2012|access-date=19 May 2016|archive-date=12 October 2016|archive-url=https://web.archive.org/web/20161012073727/http://ppaalanen.blogspot.com/2012/03/what-does-egl-do-in-wayland-stack.html|url-status=live}}

{{cite web|last1=Paalanen|first1=Pekka|title=On supporting Wayland GL clients and proprietary embedded platforms|url=https://ppaalanen.blogspot.com/2012/11/on-supporting-wayland-gl-clients-and.html|date=21 November 2012|access-date=6 April 2016|quote=Buffer sharing works by creating a handle for a buffer, and passing that handle to another process which then uses the handle to make the GPU access again the same buffer.|archive-date=6 April 2016|archive-url=https://web.archive.org/web/20160406145639/http://ppaalanen.blogspot.com/2012/11/on-supporting-wayland-gl-clients-and.html|url-status=live}}

{{cite web|last1=Paalanen|first1=Pekka|title=Wayland protocol design: object lifespan|url=https://ppaalanen.blogspot.com/2014/07/wayland-protocol-design-object-lifespan.html|date=25 July 2014|access-date=6 April 2016|archive-date=29 May 2016|archive-url=https://web.archive.org/web/20160529024658/http://ppaalanen.blogspot.com/2014/07/wayland-protocol-design-object-lifespan.html|url-status=live}}

{{cite web|last1=Peres|first1=Martin|title=Wayland Compositors - Why and How to Handle Privileged Clients!|url=https://mupuf.org/blog/2014/02/19/wayland-compositors-why-and-how-to-handle/|date=21 February 2014|access-date=17 April 2016|archive-date=10 March 2016|archive-url=https://web.archive.org/web/20160310111112/http://www.mupuf.org/blog/2014/02/19/wayland-compositors-why-and-how-to-handle/|url-status=live}}

{{cite web|last1=Schaller|first1=Christian|title=Wayland in Fedora Update|url=https://blogs.gnome.org/uraeus/2014/07/03/wayland-in-fedora-update/|website=blogs.gnome.org|date=3 July 2014|access-date=17 April 2016|archive-date=1 May 2016|archive-url=https://web.archive.org/web/20160501170950/https://blogs.gnome.org/uraeus/2014/07/03/wayland-in-fedora-update/|url-status=live}}

{{cite web|last1=Scherschel|first1=Fabian|title=Wayland's 1.0 milestone fixes graphics protocol|url=http://www.h-online.com/open/news/item/Wayland-s-1-0-milestone-fixes-graphics-protocol-1734638.html|website=The H Open|publisher=Heise Media UK|date=23 October 2012|access-date=17 April 2016|archive-date=7 December 2013|archive-url=https://web.archive.org/web/20131207164236/http://www.h-online.com/open/news/item/Wayland-s-1-0-milestone-fixes-graphics-protocol-1734638.html|url-status=dead}}

{{cite web|last1=Vervloesem|first1=Koen|title=FOSDEM: The Wayland display server|url=https://lwn.net/Articles/481490/|website=LWN.net|date=15 February 2012|access-date=9 May 2016|archive-date=5 June 2016|archive-url=https://web.archive.org/web/20160605025115/https://lwn.net/Articles/481490/|url-status=live}}

{{cite web|last1=Willis|first1=Nathan|title=LCA: The ways of Wayland|url=https://lwn.net/Articles/536862/|website=LWN.net|access-date=19 May 2016|date=13 February 2013|archive-date=24 June 2016|archive-url=https://web.archive.org/web/20160624135326/https://lwn.net/Articles/536862/|url-status=live}}

{{cite web|url=https://linuxplumbersconf.org/ocw/users/73|title=Wayland – A New Display Server for Linux|last=Høgsberg|first=Kristian|publisher=Linux Plumbers Conference, 2009|archive-url=https://web.archive.org/web/20170811103724/http://linuxplumbersconf.org/ocw/users/73|archive-date=2017-08-11|url-status=dead}}

{{cite web|title=Interview: Kristian Høgsberg|url=https://archive.fosdem.org/2012/interview/kristian-hogsberg.html|website=FOSDEM Archive|access-date=8 March 2016|date=29 January 2012|archive-date=4 March 2016|archive-url=https://web.archive.org/web/20160304040036/https://archive.fosdem.org/2012/interview/kristian-hogsberg.html|url-status=live}}

{{cite speech|title=Consolidating the input stacks with libinput|first=Peter|last=Hutterer|event=The X.Org Developer Conference 2014|location=Bordeaux|date=8 October 2014|url=https://www.x.org/wiki/Events/XDC2014/XDC2014HuttererLibInput/|access-date=14 January 2020|archive-date=1 November 2020|archive-url=https://web.archive.org/web/20201101021025/https://www.x.org/wiki/Events/XDC2014/XDC2014HuttererLibInput/|url-status=live}}

{{cite speech|title=Security in Wayland-based Desktop Environments: Privileged Clients, Authorization, Authentication and Sandboxing!|first1=Steve|last1=Dodier-Lazaro|first2=Martin|last2=Peres|event=The X.Org Developer Conference 2014|location=Bordeaux|date=9 October 2014|url=https://phd.mupuf.org/publication/2014/10/09/security-in-wayland-based-desktop-environments/|access-date=18 April 2016|archive-date=9 April 2016|archive-url=https://web.archive.org/web/20160409004644/http://phd.mupuf.org/publication/2014/10/09/security-in-wayland-based-desktop-environments/|url-status=live}}

{{cite web|title=The Enlightenment of Wayland|url=https://fosdem.org/2016/schedule/event/enlightenment_of_wayland/|website=FOSDEM.org|access-date=8 March 2016|archive-date=9 March 2016|archive-url=https://web.archive.org/web/20160309103352/https://fosdem.org/2016/schedule/event/enlightenment_of_wayland/|url-status=live}}

{{cite web|title=The Hello Wayland Tutorial|date=8 July 2014|url=https://hdante.wordpress.com/2014/07/08/the-hello-wayland-tutorial/|access-date=25 July 2014|archive-date=13 July 2014|archive-url=https://web.archive.org/web/20140713131846/http://hdante.wordpress.com/2014/07/08/the-hello-wayland-tutorial/|url-status=live}}

{{cite web|title=QtWayland|url=https://wiki.qt.io/QtWayland|website=Qt Wiki|access-date=9 March 2016|archive-date=10 March 2016|archive-url=https://web.archive.org/web/20160310090205/http://wiki.qt.io/QtWayland|url-status=live}}

{{cite web|title=Full Wayland support in GTK+|url=https://wiki.gnome.org/Initiatives/Wayland/GTK%2B|website=GNOME wiki|access-date=10 March 2016|archive-date=7 September 2015|archive-url=https://web.archive.org/web/20150907010626/https://wiki.gnome.org/Initiatives/Wayland/GTK%2B|url-status=live}}

{{cite web|url=https://download.gnome.org/sources/mutter-wayland/|title=Index of /sources/mutter-wayland|website=download.gnome.org|access-date=27 May 2014|archive-date=21 May 2014|archive-url=https://web.archive.org/web/20140521205013/https://download.gnome.org/sources/mutter-wayland/|url-status=live}}

{{cite web|url=https://blog.barisione.org/2014-04/maynard/|title=Maynard announcement|date=16 April 2014|access-date=16 April 2014|archive-date=8 March 2017|archive-url=https://web.archive.org/web/20170308063842/http://blog.barisione.org/2014-04/maynard/|url-status=live}}

{{cite web|title=libinput|url=https://www.freedesktop.org/wiki/Software/libinput/|publisher=Freedesktop.org|access-date=21 May 2014|archive-date=19 April 2014|archive-url=https://web.archive.org/web/20140419205348/http://www.freedesktop.org/wiki/Software/libinput/|url-status=live}}

{{cite web|url=https://rajeeshknambiar.wordpress.com/2015/02/22/libinput-support-added-to-touchpad-kcm/|title=Libinput support added to Touchpad KCM|date=22 February 2015|access-date=24 February 2015|archive-date=24 February 2015|archive-url=https://web.archive.org/web/20150224161745/https://rajeeshknambiar.wordpress.com/2015/02/22/libinput-support-added-to-touchpad-kcm/|url-status=live}}

{{cite web|url=http://linuxg.net/the-first-jolla-smartphone-runs-with-wayland/|title=The First Jolla Smartphone Runs With Wayland|publisher=LinuxG.net|date=14 July 2013|access-date=8 October 2013|archive-date=28 June 2014|archive-url=https://web.archive.org/web/20140628095653/http://linuxg.net/the-first-jolla-smartphone-runs-with-wayland/|url-status=live}}

{{cite tweet|user=VDVsx|author=VDVsx|number=356029626759385088|date=13 July 2013|title=#sailfishos main components diagram. #Qt5 #Wayland #JollaHQ #Akademy}}

{{cite tweet|user=JollaHQ|author=Jolla|number=356034168351756290|date=13 July 2013|title=@faenil @PeppeLaKappa @VDVsx our first Jolla will ship with wayland, yes}}

{{cite web|url=http://www.chaosreigns.com/wiki/Wayland_State#The_state_of_Wayland.2C_2013-01-26|access-date=6 March 2013|title=Wayland – Enlightenment|url-status=dead|archive-url=https://web.archive.org/web/20130329104629/http://www.chaosreigns.com/wiki/Wayland_State#The_state_of_Wayland.2C_2013-01-26|archive-date=29 March 2013|df=dmy-all}}

{{cite web|url=https://wiki.gnome.org/Projects/GTK/Roadmap|title=GTK+ Roadmap|access-date=8 March 2016}}

{{cite web|last=Lantinga|first=Sam|title=SDL 2.0.2 RELEASED!|url=https://forums.libsdl.org/viewtopic.php?t=10088|date=8 March 2014|publisher=SDL Project|access-date=18 March 2014|archive-date=15 March 2014|archive-url=https://web.archive.org/web/20140315054158/http://forums.libsdl.org/viewtopic.php?t=10088|url-status=live}}

{{cite web|last=Berglund|first=Camilla|title=Implementation for Wayland · Issue #106 · glfw/glfw · GitHub|website=GitHub|url=https://github.com/glfw/glfw/issues/106#issuecomment-39872275|date=8 April 2014|access-date=14 August 2014|archive-date=27 August 2022|archive-url=https://web.archive.org/web/20220827010908/https://github.com/glfw/glfw/issues/106#issuecomment-39872275|url-status=live}}

{{cite web|title=GNOME Initiatives - Wayland|url=https://wiki.gnome.org/Initiatives/Wayland|website=GNOME Wiki|access-date=8 March 2016|archive-date=7 March 2016|archive-url=https://web.archive.org/web/20160307164016/https://wiki.gnome.org/Initiatives/Wayland|url-status=live}}

{{cite web|title=KWin/Wayland|url=https://community.kde.org/KWin/Wayland|website=KDE Community Wiki|access-date=8 March 2016|archive-date=10 March 2016|archive-url=https://web.archive.org/web/20160310115021/https://community.kde.org/KWin/Wayland|url-status=live}}

{{cite web|title=Enlightenment - Wayland|url=https://www.enlightenment.org/about-wayland|website=Enlightenment.org|access-date=8 March 2016|archive-date=9 March 2016|archive-url=https://web.archive.org/web/20160309102604/https://www.enlightenment.org/about-wayland|url-status=live}}

{{cite web|title=Enlightenment DR 0.20.0 Release|url=https://phab.enlightenment.org/phame/post/view/167/enlightenment_dr_0.20.0_release/|website=Enlightenment.org|access-date=8 March 2016|archive-date=21 June 2018|archive-url=https://web.archive.org/web/20180621015953/https://phab.enlightenment.org/phame/post/view/167/enlightenment_dr_0.20.0_release/|url-status=dead}}

{{cite web|title=ReleasePlanning/FeaturesPlans|url=https://wiki.gnome.org/ReleasePlanning/FeaturePlans|publisher=GNOME Project|access-date=31 May 2015|archive-date=31 May 2015|archive-url=https://web.archive.org/web/20150531015800/https://wiki.gnome.org/ReleasePlanning/FeaturePlans|url-status=live}}

{{cite web|url=http://vizzzion.org/blog/2014/07/plasmas-road-to-wayland/|title=Plasma's Road to Wayland|date=25 July 2014|access-date=25 July 2014|archive-date=27 July 2014|archive-url=https://web.archive.org/web/20140727191427/http://vizzzion.org/blog/2014/07/plasmas-road-to-wayland/|url-status=dead}}

{{cite web|url=http://www.realvnc.com/products/vnc/wayland/|title=VNC® Wayland Developer Preview|date=8 July 2014|url-status=dead|archive-url=https://web.archive.org/web/20140714205900/http://www.realvnc.com/products/vnc/wayland/|archive-date=14 July 2014|df=dmy-all}}

{{cite web|url=http://mikhas.posterous.com/maliit-status-update|title=Maliit Status Update|publisher=Posterous|date=2 April 2013|archive-url=https://web.archive.org/web/20130517213318/http://mikhas.posterous.com/maliit-status-update|archive-date=17 May 2013|url-status=dead|access-date=14 October 2013}}

{{cite web|url=https://www.murrayc.com/permalink/2013/04/02/more-maliit-keyboard-improvements-qtquick2/|title=More Maliit Keyboard Improvements: QtQuick2|publisher=Murray's Blog|date=2 April 2013|access-date=14 October 2013|archive-date=13 October 2013|archive-url=https://web.archive.org/web/20131013194426/http://www.murrayc.com/permalink/2013/04/02/more-maliit-keyboard-improvements-qtquick2/|url-status=live}}

{{cite web|url=https://wiki.maliit.org/Wayland_Input_Method_System_Proposal|archive-url=https://web.archive.org/web/20130611231511/https://wiki.maliit.org/Wayland_Input_Method_System_Proposal|url-status=dead|archive-date=11 June 2013|title=Maliit under Wayland|access-date=14 September 2013}}

{{cite web|url=https://www.freedesktop.org/wiki/Software/kmscon/wlterm/|title=wlterm|publisher=Freedesktop.org|access-date=8 July 2014|archive-date=14 July 2014|archive-url=https://web.archive.org/web/20140714182643/http://www.freedesktop.org/wiki/Software/kmscon/wlterm/|url-status=live}}

{{cite web|url=http://blog.vogella.com/2014/08/18/eclipse-now-runs-on-wayland/|title=Eclipse now runs on Wayland|date=18 August 2014|access-date=17 September 2014|archive-date=23 August 2014|archive-url=https://web.archive.org/web/20140823203722/http://blog.vogella.com/2014/08/18/eclipse-now-runs-on-wayland/|url-status=live}}

{{cite web|last1=Stone|first1=Daniel|title=Vulkan 1.0 specification released with day-one support for Wayland|url=https://www.collabora.com/about-us/blog/2016/02/16/vulkan-1.0-specification-released-with-day-one-support-for-wayland/|date=16 February 2016|access-date=27 February 2016|archive-date=24 June 2016|archive-url=https://web.archive.org/web/20160624004927/https://www.collabora.com/about-us/blog/2016/02/16/vulkan-1.0-specification-released-with-day-one-support-for-wayland/|url-status=live}}

{{cite web|url=http://projects.genivi.org/ivi-layer-management/node/17|archive-url=https://web.archive.org/web/20140201161624/http://projects.genivi.org/ivi-layer-management/node/17|url-status=dead|archive-date=1 February 2014|title=Wayland Backend DRM | IVI Layer Management|publisher=GENIVI Alliance|access-date=15 July 2013}}

{{cite web|url=http://www.collabora.com/services/case-studies/raspberrypi/|title=Raspberry Pi Case Study|publisher=Collabora|access-date=9 August 2013|archive-date=1 September 2013|archive-url=https://web.archive.org/web/20130901164936/http://www.collabora.com/services/case-studies/raspberrypi/|url-status=live}}

{{cite web|url=https://www.raspberrypi.com/news/wayland-preview/|title=Wayland preview|publisher=Raspberry Pi|date=24 February 2013|access-date=4 August 2024}}

{{cite web|url=https://wiki.tizen.org/w/index.php?title=IVI%2FIVI_Setup&oldid=1037|title=IVI/IVI Setup|publisher=Tizen Wiki|access-date=8 April 2013|archive-date=10 February 2017|archive-url=https://web.archive.org/web/20170210051856/https://wiki.tizen.org/w/index.php?title=IVI%2FIVI_Setup&oldid=1037|url-status=live}}

{{cite web|last=Munk|first=Carsten|url=https://mer-project.blogspot.com/2013/04/wayland-utilizing-android-gpu-drivers.html|title=Wayland utilizing Android GPU drivers on glibc based systems, Part 1|publisher=Mer Project|date=11 April 2013|access-date=3 July 2013|archive-date=19 April 2013|archive-url=https://web.archive.org/web/20130419050731/http://mer-project.blogspot.com/2013/04/wayland-utilizing-android-gpu-drivers.html|url-status=live}}

{{cite web|last=Munk|first=Carsten|url=https://mer-project.blogspot.com/2013/05/wayland-utilizing-android-gpu-drivers.html|title=Wayland utilizing Android GPU drivers on glibc based systems, Part 2|publisher=Mer Project|date=8 June 2013|access-date=3 July 2013|archive-date=24 October 2013|archive-url=https://web.archive.org/web/20131024095141/http://mer-project.blogspot.com/2013/05/wayland-utilizing-android-gpu-drivers.html|url-status=live}}

{{cite web|url=https://news.softpedia.com/news/wayland-1-10-display-server-officially-released-wayland-1-11-arrives-in-may-2016-500558.shtml|title=Wayland 1.10 Display Server Officially Released, Wayland 1.11 Arrives in May 2016|last=Nestor|first=Marius|date=18 February 2016|work=Softpedia|access-date=14 January 2020|archive-date=14 January 2020|archive-url=https://web.archive.org/web/20200114134844/https://news.softpedia.com/news/wayland-1-10-display-server-officially-released-wayland-1-11-arrives-in-may-2016-500558.shtml|url-status=live}}

{{cite web|url=https://www.x.org/wiki/Development/Documentation/Security/|title=X.Org Security|work=X.Org Foundation|access-date=2 July 2017|quote=The X server has long included an extension, SECURITY, which provides support for a simple trusted/untrusted connection model.|archive-date=22 December 2017|archive-url=https://web.archive.org/web/20171222000004/https://www.x.org/wiki/Development/Documentation/Security/|url-status=live}}

{{cite web|url=https://www.x.org/releases/current/doc/xextproto/security.html|title=Security Extension Specification|last=Wiggins|first=David P.|work=X Consortium Standard|date=15 November 1996|access-date=2 July 2017|archive-date=8 December 2018|archive-url=https://web.archive.org/web/20181208112056/https://www.x.org/releases/current/doc/xextproto/security.html|url-status=live}}

{{cite web|url=https://www.x.org/releases/X11R7.6/doc/xorg-docs/specs/Xserver/XACE-Spec.html|title=X Access Control Extension Specification|last=Walsh|first=Eamon F.|date=2009|access-date=2 July 2017|archive-date=9 January 2016|archive-url=https://web.archive.org/web/20160109051310/http://www.x.org/releases/X11R7.6/doc/xorg-docs/specs/Xserver/XACE-Spec.html|url-status=live}}

{{cite web|url=https://ctrl.blog/entry/wayland-gnome-remote-desktop|title=Remote desktop capabilities set to make a comeback in GNOME on Wayland|website=Ctrl.blog|first=Daniel|last=Aleksandersen|date=28 August 2017 |access-date=29 August 2017|archive-date=28 August 2017|archive-url=https://web.archive.org/web/20170828230844/https://ctrl.blog/entry/wayland-gnome-remote-desktop|url-status=live}}

{{cite web|last1=Barnes|first1=Jesse|title=Introduction to Wayland|url=https://www.tizen.org/sites/default/files/lfcs2012_barnes.pdf|publisher=Intel Open Source Technology Center|access-date=18 April 2016|quote=Does not include a rendering API – Clients use what they want and send buffer handles to the server|archive-date=6 April 2016|archive-url=https://web.archive.org/web/20160406214636/https://www.tizen.org/sites/default/files/lfcs2012_barnes.pdf|url-status=live}}

{{cite web|title=Wayland/X Compositor Architecture By Example: Enlightenment DR19|url=https://events.static.linuxfound.org/sites/events/files/slides/presentation_0.pdf|access-date=4 August 2024}}

{{cite web|last1=de Goede|first1=Hans|title=Replacing xorg input - Drivers with libinput|url=https://archive.fosdem.org/2015/schedule/event/libinput/attachments/slides/591/export/events/attachments/libinput/slides/591/libinput_xorg.pdf|date=1 February 2015|access-date=18 April 2016|archive-date=22 November 2021|archive-url=https://web.archive.org/web/20211122215450/https://archive.fosdem.org/2015/schedule/event/libinput/attachments/slides/591/export/events/attachments/libinput/slides/591/libinput_xorg.pdf|url-status=live}}

{{cite speech|title=The real story behind Wayland and X|first=Daniel|last=Stone|event=linux.conf.au 2013|location=Canberra|date=28 January 2013|url=https://mirror.linux.org.au/pub/linux.conf.au/2013/mp4/The_real_story_behind_Wayland_and_X.mp4|access-date=13 April 2016|archive-date=10 August 2017|archive-url=https://web.archive.org/web/20170810013908/http://mirror.linux.org.au/pub/linux.conf.au/2013/mp4/The_real_story_behind_Wayland_and_X.mp4|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2015-September/024226.html|title=[ANNOUNCE] wayland 1.8.93|first=Bryce|last=Harrington|date=15 September 2015|mailing-list=freedesktop.org|access-date=14 January 2020|archive-date=25 October 2020|archive-url=https://web.archive.org/web/20201025230202/https://lists.freedesktop.org/archives/wayland-devel/2015-September/024226.html|url-status=live}}

{{cite web|url=https://lists.freedesktop.org/archives/wayland-devel/2010-November/000097.html|title=Network transparency argument|last=Høgsberg|first=Kristian|date=9 November 2010|quote=Wayland isn't a remote rendering API like X, but that doesn't exclude network transparency. Clients render into a shared buffer and then have to tell the compositor (...) what they changed. The compositor can then send the new pixels in that region out over the network. The Wayland protocol is already violently asynchronous, so it should be able to handle a bit of network lag gracefully. Remote fullscreen video viewing or gaming isn't going to work well, [but] I don't know any other display system that handles that well and transparently.|access-date=14 January 2020|archive-date=15 August 2020|archive-url=https://web.archive.org/web/20200815074353/https://lists.freedesktop.org/archives/wayland-devel/2010-November/000097.html|url-status=live}}

{{cite mailing list|url=https://lists.fedoraproject.org/pipermail/devel/2010-November/145306.html|title=[Re:] Ubuntu moving towards Wayland|last=Jackson|first=Adam|date=9 November 2010|mailing-list=devel@lists.fedoraproject.org|access-date=14 January 2020|archive-date=8 March 2021|archive-url=https://web.archive.org/web/20210308134805/https://lists.fedoraproject.org/pipermail/devel/2010-November/145306.html|url-status=dead}}

{{cite web|url=https://lists.x.org/archives/xorg-announce/2014-July/002457.html|title=ANNOUNCE: xorg-server 1.16.0|publisher=freedesktop.org|date=17 July 2014|access-date=14 January 2020|archive-date=8 March 2021|archive-url=https://web.archive.org/web/20210308121411/https://lists.x.org/archives/xorg-announce/2014-July/002457.html|url-status=live}}

{{cite web|url=https://lists.freedesktop.org/archives/wayland-devel/2010-December/000330.html|title=Blender3D & cursor clamping.|date=9 December 2010|last=Høgsberg|first=Kristian|access-date=14 January 2020|archive-date=25 October 2020|archive-url=https://web.archive.org/web/20201025214539/https://lists.freedesktop.org/archives/wayland-devel/2010-December/000330.html|url-status=live}}

{{cite web|url=https://lists.freedesktop.org/archives/wayland-devel/2013-October/011536.html|title=[RFC weston] remote access interface module|publisher=freedesktop.org|date=18 October 2013|access-date=14 January 2020|archive-date=25 October 2020|archive-url=https://web.archive.org/web/20201025220521/https://lists.freedesktop.org/archives/wayland-devel/2013-October/011536.html|url-status=live}}

{{cite web|url=https://lists.freedesktop.org/archives/wayland-devel/2015-February/020131.html|title=libinput: the road to 1.0|first=Peter|last=Hutterer|date=22 February 2015|access-date=9 November 2019|archive-date=25 October 2020|archive-url=https://web.archive.org/web/20201025225206/https://lists.freedesktop.org/archives/wayland-devel/2015-February/020131.html|url-status=live}}

{{cite mailing list|url=https://lists.fedoraproject.org/pipermail/devel/2015-February/208204.html|title=Libinput now enabled as default xorg driver for F-22 workstation installs|first=Hans de|last=Goede|date=23 February 2015|mailing-list=devel@lists.fedoraproject.org|access-date=24 February 2015|archive-date=24 February 2015|archive-url=https://web.archive.org/web/20150224160920/https://lists.fedoraproject.org/pipermail/devel/2015-February/208204.html|url-status=dead}}

{{cite web|url=https://lists.freedesktop.org/archives/wayland-devel/2013-November/011930.html|title=[RFC] Common input device library|last=Ådahl|first=Jonas|publisher=Wayland mailing list|date=12 November 2013|access-date=14 January 2020|archive-date=25 October 2020|archive-url=https://web.archive.org/web/20201025230036/https://lists.freedesktop.org/archives/wayland-devel/2013-November/011930.html|url-status=live}}

{{cite mailing list|mailing-list=clutter-announce|last=Bassi|first=Emmanuele|title=ANNOUNCE: Clutter 1.6.0 (stable)|date=31 January 2011|url=https://mail.gnome.org/archives/gnome-announce-list/2011-January/msg00072.html|access-date=9 March 2016|archive-date=10 March 2016|archive-url=https://web.archive.org/web/20160310023048/https://mail.gnome.org/archives/gnome-announce-list/2011-January/msg00072.html|url-status=live}}

{{cite mailing list|mailing-list=clutter-announce|last=Bassi|first=Emmanuele|title=ANNOUNCE: Clutter 1.16.0 (stable)|url=https://mail.gnome.org/archives/clutter-list/2013-September/msg00011.html|date=24 September 2013|access-date=9 March 2016|archive-date=10 March 2016|archive-url=https://web.archive.org/web/20160310012628/https://mail.gnome.org/archives/clutter-list/2013-September/msg00011.html|url-status=live}}

{{cite web|url=https://lists.freedesktop.org/archives/wayland-devel/2014-July/015949.html|title=RealVNC Wayland developer preview email|publisher=freedesktop.org|date=9 July 2014|access-date=14 January 2020|archive-date=25 October 2020|archive-url=https://web.archive.org/web/20201025220610/https://lists.freedesktop.org/archives/wayland-devel/2014-July/015949.html|url-status=live}}

{{cite mailing list|mailing-list=IVI|last=VanCutsem|first=Geoffroy|title=[IVI] Tizen IVI 3.0-M1 released|url=https://lists.tizen.org/pipermail/ivi/2013-July/000563.html|date=10 July 2013|access-date=13 July 2013|archive-date=2 October 2013|archive-url=https://web.archive.org/web/20131002140438/https://lists.tizen.org/pipermail/ivi/2013-July/000563.html|url-status=live}}

{{cite web|url=https://groups.google.com/forum/#!topic/wayland-display-server/sfvLwLaHwsE|title=Moving to freedesktop.org|last=Høgsberg|first=Kristian|date=29 October 2010|access-date=31 July 2013|archive-date=9 November 2012|archive-url=https://web.archive.org/web/20121109222635/http://groups.google.com/group/rec.arts.comics.misc/browse_frm/thread/758fa9d13d234863/8d4e36d21137d39e?lnk=st&q=%22Archie+goes+unchallenged%22#!topic/wayland-display-server/sfvLwLaHwsE|url-status=live}}

{{cite mailing list|mailing-list=wayland-display-server|last=Høgsberg|first=Kristian|title=Wayland is now under MIT license|date=3 December 2008|url=https://groups.google.com/forum/#!topic/wayland-display-server/daWzNkr5erE|access-date=8 March 2016|archive-date=9 November 2012|archive-url=https://web.archive.org/web/20121109222635/http://groups.google.com/group/rec.arts.comics.misc/browse_frm/thread/758fa9d13d234863/8d4e36d21137d39e?lnk=st&q=%22Archie+goes+unchallenged%22#!topic/wayland-display-server/daWzNkr5erE|url-status=live}}

{{cite mailing list|mailing-list=wayland-devel|last=Høgsberg|first=Kristian|title=Wayland license clarification|date=22 November 2010|url=https://lists.freedesktop.org/archives/wayland-devel/2010-November/000249.html|access-date=8 March 2016|archive-date=9 March 2016|archive-url=https://web.archive.org/web/20160309101222/https://lists.freedesktop.org/archives/wayland-devel/2010-November/000249.html|url-status=live}}

{{cite mailing list|mailing-list=wayland-devel|last=Høgsberg|first=Kristian|title=License update|date=19 September 2011|url=https://lists.freedesktop.org/archives/wayland-devel/2011-September/001386.html|access-date=8 March 2016|archive-date=29 April 2016|archive-url=https://web.archive.org/web/20160429042115/https://lists.freedesktop.org/archives/wayland-devel/2011-September/001386.html|url-status=live}}

{{cite mailing list|last=Høgsberg|first=Kristian|title=[ANNOUNCE] Wayland and Weston 0.85.0 released|url=https://lists.freedesktop.org/archives/wayland-devel/2012-February/002072.html|mailing-list=wayland-devel|date=9 February 2012|access-date=14 January 2020|archive-date=14 January 2020|archive-url=https://web.archive.org/web/20200114134921/https://lists.freedesktop.org/archives/wayland-devel/2012-February/002072.html|url-status=live}}

{{cite mailing list|last=Høgsberg|first=Kristian|title=Wayland and Weston 0.95.0 released|url=https://lists.freedesktop.org/archives/wayland-devel/2012-July/004542.html|mailing-list=wayland-devel|date=24 July 2012|access-date=14 January 2020|archive-date=25 October 2020|archive-url=https://web.archive.org/web/20201025215619/https://lists.freedesktop.org/archives/wayland-devel/2012-July/004542.html|url-status=live}}

{{cite mailing list|last=Høgsberg|first=Kristian|title=Wayland and Weston 1.0|url=https://lists.freedesktop.org/archives/wayland-devel/2012-October/005967.html|mailing-list=wayland-devel|date=22 October 2012|access-date=14 January 2020|archive-date=23 August 2019|archive-url=https://web.archive.org/web/20190823084549/https://lists.freedesktop.org/archives/wayland-devel/2012-October/005967.html|url-status=live}}

{{cite mailing list|last=Høgsberg|first=Kristian|title=1.1 Released|url=https://lists.freedesktop.org/archives/wayland-devel/2013-April/008631.html|mailing-list=wayland-devel|date=15 April 2013|access-date=14 January 2020|archive-date=27 May 2019|archive-url=https://web.archive.org/web/20190527164726/https://lists.freedesktop.org/archives/wayland-devel/2013-April/008631.html|url-status=live}}

{{cite mailing list|last=Høgsberg|first=Kristian|title=Wayland and Weston 1.2.0 released|url=https://lists.freedesktop.org/archives/wayland-devel/2013-July/010278.html|mailing-list=wayland-devel|date=12 July 2013|access-date=14 January 2020|archive-date=25 June 2019|archive-url=https://web.archive.org/web/20190625192111/https://lists.freedesktop.org/archives/wayland-devel/2013-July/010278.html|url-status=live}}

{{cite mailing list|last=Høgsberg|first=Kristian|title=Wayland and Weston 1.3 releases are out|url=https://lists.freedesktop.org/archives/wayland-devel/2013-October/011419.html|mailing-list=wayland-devel|date=11 October 2013|access-date=11 April 2020|archive-date=8 August 2020|archive-url=https://web.archive.org/web/20200808090510/https://lists.freedesktop.org/archives/wayland-devel/2013-October/011419.html|url-status=live}}

{{cite mailing list|last=Høgsberg|first=Kristian|title=Wayland and Weston 1.4 is out|url=https://lists.freedesktop.org/archives/wayland-devel/2014-January/012903.html|mailing-list=wayland-devel|date=24 January 2014|access-date=14 January 2020|archive-date=5 April 2020|archive-url=https://web.archive.org/web/20200405181817/https://lists.freedesktop.org/archives/wayland-devel/2014-January/012903.html|url-status=live}}

{{cite mailing list|last=Høgsberg|first=Kristian|title=Wayland and Weston 1.5.0 is released|url=https://lists.freedesktop.org/archives/wayland-devel/2014-May/014955.html|mailing-list=wayland-devel|date=20 May 2014|access-date=14 January 2020|archive-date=19 October 2019|archive-url=https://web.archive.org/web/20191019110657/https://lists.freedesktop.org/archives/wayland-devel/2014-May/014955.html|url-status=live}}

{{cite mailing list|last1=Paalanen|first1=Pekka|title=Wayland and Weston 1.6.0 released|url=https://lists.freedesktop.org/archives/wayland-devel/2014-September/017396.html|mailing-list=wayland-devel|date=19 September 2014|access-date=14 January 2020|archive-date=27 May 2019|archive-url=https://web.archive.org/web/20190527164732/https://lists.freedesktop.org/archives/wayland-devel/2014-September/017396.html|url-status=live}}

{{cite mailing list|last1=Harrington|first1=Bryce|title=[ANNOUNCE] wayland 1.7.0|url=https://lists.freedesktop.org/archives/wayland-devel/2015-February/019976.html|mailing-list=wayland-devel|date=14 February 2015|access-date=14 January 2020|archive-date=5 April 2020|archive-url=https://web.archive.org/web/20200405181859/https://lists.freedesktop.org/archives/wayland-devel/2015-February/019976.html|url-status=live}}

{{cite mailing list|last1=Harrington|first1=Bryce|title=[ANNOUNCE] weston 1.7.0|url=https://lists.freedesktop.org/archives/wayland-devel/2015-February/019977.html|mailing-list=wayland-devel|date=14 February 2015|access-date=14 January 2020|archive-date=5 April 2020|archive-url=https://web.archive.org/web/20200405181859/https://lists.freedesktop.org/archives/wayland-devel/2015-February/019977.html|url-status=live}}

{{cite mailing list|last1=Harrington|first1=Bryce|title=[ANNOUNCE] wayland 1.8.0|url=https://lists.freedesktop.org/archives/wayland-devel/2015-June/022415.html|mailing-list=wayland-devel|date=2 June 2015|access-date=14 January 2020|archive-date=15 August 2020|archive-url=https://web.archive.org/web/20200815091351/https://lists.freedesktop.org/archives/wayland-devel/2015-June/022415.html|url-status=live}}

{{cite mailing list|last1=Harrington|first1=Bryce|title=[ANNOUNCE] weston 1.8.0|url=https://lists.freedesktop.org/archives/wayland-devel/2015-June/022416.html|mailing-list=wayland-devel|date=2 June 2015|access-date=14 January 2020|archive-date=15 August 2020|archive-url=https://web.archive.org/web/20200815084805/https://lists.freedesktop.org/archives/wayland-devel/2015-June/022416.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2015-September/024302.html|title=[ANNOUNCE] wayland 1.9.0|first=Bryce|last=Harrington|date=21 September 2015|mailing-list=wayland-devel|access-date=14 January 2020|archive-date=25 October 2020|archive-url=https://web.archive.org/web/20201025222349/https://lists.freedesktop.org/archives/wayland-devel/2015-September/024302.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2015-September/024303.html|title=[ANNOUNCE] weston 1.9.0|first=Bryce|last=Harrington|date=21 September 2015|mailing-list=wayland-devel|access-date=14 January 2020|archive-date=21 September 2020|archive-url=https://web.archive.org/web/20200921044115/https://lists.freedesktop.org/archives/wayland-devel/2015-September/024303.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2016-February/027038.html|title=[ANNOUNCE] wayland 1.10.0|first=Bryce|last=Harrington|date=17 February 2016|mailing-list=wayland-devel|access-date=17 February 2016|archive-date=17 February 2016|archive-url=https://web.archive.org/web/20160217083326/https://lists.freedesktop.org/archives/wayland-devel/2016-February/027038.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2016-February/027039.html|title=[ANNOUNCE] weston 1.10.0|first=Bryce|last=Harrington|date=17 February 2016|mailing-list=wayland-devel|access-date=17 February 2016|archive-date=24 February 2016|archive-url=https://web.archive.org/web/20160224031559/https://lists.freedesktop.org/archives/wayland-devel/2016-February/027039.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2016-June/029163.html|title=[ANNOUNCE] wayland 1.11.0|first=Bryce|last=Harrington|date=1 June 2016|access-date=1 June 2016|mailing-list=wayland-devel|archive-date=1 June 2016|archive-url=https://web.archive.org/web/20160601085111/https://lists.freedesktop.org/archives/wayland-devel/2016-June/029163.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2016-June/029164.html|title=[ANNOUNCE] weston 1.11.0|first=Bryce|last=Harrington|date=1 June 2016|access-date=1 June 2016|mailing-list=wayland-devel|archive-date=8 October 2016|archive-url=https://web.archive.org/web/20161008164235/https://lists.freedesktop.org/archives/wayland-devel/2016-June/029164.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2016-September/031121.html|title=[ANNOUNCE] wayland 1.12.0|first=Bryce|last=Harrington|date=21 September 2016|access-date=21 September 2016|mailing-list=wayland-devel|archive-date=2 April 2017|archive-url=https://web.archive.org/web/20170402020659/https://lists.freedesktop.org/archives/wayland-devel/2016-September/031121.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2016-September/031123.html|title=[ANNOUNCE] weston 1.12.0|first=Bryce|last=Harrington|date=21 September 2016|access-date=21 September 2016|mailing-list=wayland-devel|archive-date=8 October 2016|archive-url=https://web.archive.org/web/20161008110903/https://lists.freedesktop.org/archives/wayland-devel/2016-September/031123.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2017-February/033193.html|title=[ANNOUNCE] wayland 1.13.0|first=Bryce|last=Harrington|date=21 February 2017|access-date=30 April 2017|mailing-list=wayland-devel|archive-date=24 February 2017|archive-url=https://web.archive.org/web/20170224121408/https://lists.freedesktop.org/archives/wayland-devel/2017-February/033193.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2017-February/033231.html|title=[ANNOUNCE] weston 2.0.0|first=Bryce|last=Harrington|date=25 February 2017|access-date=30 April 2017|mailing-list=wayland-devel|archive-date=2 March 2017|archive-url=https://web.archive.org/web/20170302071023/https://lists.freedesktop.org/archives/wayland-devel/2017-February/033231.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2017-August/034748.html|title=[ANNOUNCE] wayland 1.14.0|first=Bryce|last=Harrington|date=8 August 2017|access-date=25 March 2018|mailing-list=wayland-devel|archive-date=20 October 2018|archive-url=https://web.archive.org/web/20181020173506/https://lists.freedesktop.org/archives/wayland-devel/2017-August/034748.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2017-August/034749.html|title=[ANNOUNCE] weston 3.0.0|first=Bryce|last=Harrington|date=8 August 2017|access-date=25 March 2018|mailing-list=wayland-devel|archive-date=20 October 2018|archive-url=https://web.archive.org/web/20181020180931/https://lists.freedesktop.org/archives/wayland-devel/2017-August/034749.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2018-April/037767.html|title=[ANNOUNCE] wayland 1.15.0|first=Derek|last=Foreman|date=9 April 2018|access-date=15 April 2018|mailing-list=wayland-devel|archive-date=10 April 2018|archive-url=https://web.archive.org/web/20180410072116/https://lists.freedesktop.org/archives/wayland-devel/2018-April/037767.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2018-April/037768.html|title=[ANNOUNCE] weston 4.0.0|first=Derek|last=Foreman|date=9 April 2018|access-date=15 April 2018|mailing-list=wayland-devel|archive-date=10 April 2018|archive-url=https://web.archive.org/web/20180410202212/https://lists.freedesktop.org/archives/wayland-devel/2018-April/037768.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2018-August/039358.html|title=[ANNOUNCE] wayland 1.16.0|first=Derek|last=Foreman|date=24 August 2018|access-date=30 November 2018|mailing-list=wayland-devel|archive-date=28 August 2018|archive-url=https://web.archive.org/web/20180828103108/https://lists.freedesktop.org/archives/wayland-devel/2018-August/039358.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2018-August/039359.html|title=[ANNOUNCE] weston 5.0.0|first=Derek|last=Foreman|date=24 August 2018|access-date=30 November 2018|mailing-list=wayland-devel|archive-date=25 August 2018|archive-url=https://web.archive.org/web/20180825180241/https://lists.freedesktop.org/archives/wayland-devel/2018-August/039359.html|url-status=live}}

{{cite mailing list |url=https://lists.freedesktop.org/archives/wayland-devel/2019-March/040335.html |title=[ANNOUNCE] wayland 1.17.0 |website=Wayland |date=28 March 2019 |first=Derek |last=Foreman |access-date=17 June 2019 |archive-date=25 March 2019 |archive-url=https://web.archive.org/web/20190325203121/https://lists.freedesktop.org/archives/wayland-devel/2019-March/040335.html |url-status=live}}

{{cite mailing list |url=https://lists.freedesktop.org/archives/wayland-devel/2019-March/040356.html |title=[ANNOUNCE] weston 6.0.0 |website=Wayland |date=21 March 2019 |first=Derek |last=Foreman |access-date=17 June 2019 |archive-date=31 March 2019 |archive-url=https://web.archive.org/web/20190331194923/https://lists.freedesktop.org/archives/wayland-devel/2019-March/040356.html |url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2020-February/041207.html|title=[ANNOUNCE] wayland 1.18|website=Wayland|date=11 February 2020|first=Simon|last=Ser|access-date=12 February 2020|archive-date=1 April 2021|archive-url=https://web.archive.org/web/20210401042718/https://lists.freedesktop.org/archives/wayland-devel/2020-February/041207.html|url-status=live}}

{{cite mailing list |url=https://lists.freedesktop.org/archives/wayland-devel/2019-August/040812.html |title=[ANNOUNCE] weston 7.0.0 |website=Wayland |date=23 August 2019 |first=Simon |last=Ser |access-date=22 October 2019 |archive-date=25 August 2019 |archive-url=https://web.archive.org/web/20190825033310/https://lists.freedesktop.org/archives/wayland-devel/2019-August/040812.html |url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2020-January/041147.html|title=[ANNOUNCE] weston 8.0.0|website=Wayland|date=24 January 2020|first=Simon|last=Ser|access-date=12 February 2020}}

{{Cite mailing list |url=https://lists.freedesktop.org/archives/wayland-devel/2020-September/041595.html |title=[ANNOUNCE] weston 9.0.0 |date=4 September 2020 |first=Simon |last=Ser|access-date=30 October 2020 |archive-date=29 September 2020 |archive-url=https://web.archive.org/web/20200929211532/https://lists.freedesktop.org/archives/wayland-devel/2020-September/041595.html |url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2021-January/041692.html|title=[ANNOUNCE] wayland 1.19.0|mailing-list=wayland-devel|date=27 January 2021|first=Simon|last=Ser|access-date=27 January 2021|archive-date=1 February 2021|archive-url=https://web.archive.org/web/20210201091228/https://lists.freedesktop.org/archives/wayland-devel/2021-January/041692.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2021-December/042064.html|title=[ANNOUNCE] wayland 1.20.0|mailing-list=wayland-devel|date=27 January 2021|first=Simon|last=Ser|access-date=27 January 2021|archive-date=11 December 2021|archive-url=https://web.archive.org/web/20211211142112/https://lists.freedesktop.org/archives/wayland-devel/2021-December/042064.html|url-status=live}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2022-February/042103.html|title=[ANNOUNCE] weston 10.0.0|website=Wayland|date=1 February 2022|first=Simon|last=Ser|access-date=12 February 2022|archive-date=4 February 2022|archive-url=https://web.archive.org/web/20220204232432/https://lists.freedesktop.org/archives/wayland-devel/2022-February/042103.html|url-status=live}}

{{cite mailing list | url=https://lists.freedesktop.org/archives/wayland-devel/2023-August/042925.html | title=[ANNOUNCE] weston 10.0.5 | mailing-list=wayland-devel | first=Marius | last=Vlad | date=2 August 2023}}

{{cite mailing list | url=https://lists.freedesktop.org/archives/wayland-devel/2022-June/042268.html | title=[ANNOUNCE] wayland 1.21.0 | mailing-list=wayland-devel | first=Simon | last=Ser | date=30 June 2022}}

{{cite mailing list | url=https://lists.freedesktop.org/archives/wayland-devel/2022-September/042410.html | title=[ANNOUNCE] weston 11.0.0 | mailing-list=wayland-devel | first=Simon | last=Ser | date=22 September 2022}}

{{cite mailing list | url=https://lists.freedesktop.org/archives/wayland-devel/2023-August/042924.html | title=[ANNOUNCE] weston 11.0.3 | mailing-list=wayland-devel | first=Marius | last=Vlad | date=2 August 2023}}

{{cite mailing list|url=https://lists.freedesktop.org/archives/wayland-devel/2023-April/042647.html|title=[ANNOUNCE] wayland 1.22.0|mailing-list=wayland-devel|date=4 April 2023|first=Simon|last=Ser|access-date=9 April 2023}}

{{cite mailing list | url=https://lists.freedesktop.org/archives/wayland-devel/2023-May/042720.html | title=[ANNOUNCE] weston 12.0.0 | mailing-list=wayland-devel | first=Marius | last=Vlad | date=17 May 2023}}

https://lists.freedesktop.org/archives/wayland-devel/2025-April/044163.html

{{cite mailing list | url=https://lists.freedesktop.org/archives/wayland-devel/2023-November/043326.html | title=[ANNOUNCE] weston 13.0.0 | mailing-list=wayland-devel | first=Marius | last=Vlad | date=28 November 2023}}

https://lists.freedesktop.org/archives/wayland-devel/2025-April/044159.html

{{cite mailing list | url=https://lists.freedesktop.org/archives/wayland-devel/2024-May/043636.html | title=[ANNOUNCE] wayland 1.23.0 | mailing-list=wayland-devel | first=Simon | last=Ser | date=30 May 2024}}

{{cite mailing list | url=https://lists.freedesktop.org/archives/wayland-devel/2024-September/043776.html | title=[ANNOUNCE] weston 14.0.0 | mailing-list=wayland-devel | first=Marius | last=Vlad | date=4 September 2024}}

https://lists.freedesktop.org/archives/wayland-devel/2025-April/044158.html

{{cite web|url=https://gitlab.freedesktop.org/wayland/weston/-/commit/3c4dc74cebe1de6f71ec9eeb9794eaaff4327e95|title=xdg_shell: Adding a new shell protocol|work=freedesktop.org|date=3 December 2013|access-date=4 August 2024}}

{{cite web|url=https://github.com/dcnieho/FreeGLUT/commit/9b30564b6d9c9f106c7d079d6cf9207363a49111|title=FreeGLUT: Implement initial Wayland support|website=GitHub|access-date=7 April 2015|archive-date=10 November 2020|archive-url=https://web.archive.org/web/20201110020151/https://github.com/dcnieho/FreeGLUT/commit/9b30564b6d9c9f106c7d079d6cf9207363a49111|url-status=live}}

}}

{{Wikibooks|Linux Guide/Applications supported via Wayland|Linux Guide/Applications supported via Wayland}}

• {{Official website|https://wayland.freedesktop.org/}}

{{Freedesktop.org}}

{{Desktop environments and window managers for X11 and Wayland}}

Category:Collabora

Category:Free software programmed in C

Category:Software using the MIT license