Most Wayland compositors only work on systems using Kernel mode setting. Wayland by itself does not provide a graphical environment; for this you also need a compositor (see the following section), or a desktop environment that includes a compositor (e.g. GNOME or KDE).
|Buffer API||GPU driver support||Wayland compositor support|
|GBM||All except NVIDIA||All|
|EGLStreams||NVIDIA||GNOME, KDE, Weston (with a third-party patch)|
See Window manager#Types for the difference between Tiling and Stacking.
- https://github.com/project-repo/cagebreak || AUR AUR
- Cardboard — Scrolling compositor, inspired by PaperWM, based on wlroots.
- dwl — dwm-like Wayland compositor based on wlroots.
- japokwm — Dynamic Wayland tiling compositor based around creating layouts, based on wlroots.
- river — Dynamic tiling Wayland compositor inspired by dwm and bspwm.
- waymonad — Wayland compositor inspired by xmonad written in Haskell.
- Greenfield — Runs in a web browser and can display remote applications.
- Grefsen — Qt/Wayland compositor providing a minimal desktop environment.
- hikari — wlroots-based compositor inspired by cwm which is actively developed on FreeBSD but also supports Linux.
- Liri Shell — Part of Liri, built using QtQuick and QtCompositor as a compositor for Wayland.
- labwc — wlroots-based compositor inspired by Openbox.
- wayfire — 3D compositor inspired by Compiz and based on wlroots.
- https://wayfire.org/ || AUR
- Weston — reference implementation of a Wayland compositor.
- wio — wlroots-based compositor that aims to replicate the look and feel of Plan 9's Rio desktop.
- Cage — Displays a single fullscreen application like a kiosk.
- Maze Compositor — Renders windows in a 3D maze using Qt.
- Motorcar — Wayland compositor to explore 3D windowing using virtual reality.
Some of the above may support display managers. Check
/usr/share/wayland-sessions/compositor.desktop to see how they are started.
Display managers listed below support launching Wayland compositors. The "Type" column indicates whether the display manager supports running itself on Wayland or not.
|GDM||Runs on Wayland||GNOME display manager.|
|greetd||Login daemon||Minimal and flexible login daemon.|
|LightDM||Runs on X11||Cross-desktop display manager.|
|Ly||Runs in console||TUI display manager written in C|
|SDDM||Runs on X11||QML-based display manager.|
|tbsm||Runs in console||Simple CLI session launcher written in pure bash.|
See details on the official website.
To enable Wayland support in Qt 5 or 6, install the or package, respectively.
To run a Qt application with the Wayland plugin , use
-platform wayland or
QT_QPA_PLATFORM=wayland environment variable. To force the usage of X11 on a Wayland session, use
QT_QPA_PLATFORM=xcb. This might be necessary for some proprietary applications that do not use the system's implementation of Qt, such as AUR.
On some compositors, for example sway, Qt applications running natively might have missing functionality. For example, KeepassXC will be unable to minimize to tray. This can be solved by installing and setting
QT_QPA_PLATFORMTHEME=qt5ct before running the application.
The Clutter toolkit has a Wayland backend that allows it to run as a Wayland client. The backend is enabled in thepackage.
To run a Clutter application on Wayland, set
To run a SDL2 application on Wayland, set
SDL_VIDEODRIVER=wayland. To force the application to run with XWayland, set
To use GLFW with the Wayland backend, install thepackage (instead of ).
The FS#62713.AUR package currently still does not work with a lot of GLEW-based applications, so the only option is to use with Xwayland. See
EFL has complete Wayland support. To run a EFL application on Wayland, see Wayland project page.
Winit is a window handling library in Rust. It will default to the Wayland backend, but it is possible to override it to Xwayland by modifying an environment variable:
In order to use it, install the package.
XWayland is started via a compositor, so you should check for XWayland compatibility and instructions on how to start XWayland, with the compositor of your choice.
- Regarding Security: XWayland is an X Server, so it does not have the security features of Wayland!
- For now the Nvidia proprietary driver does not support GPU acceleration for XWayland. See this pull request for the status of XWayland support.
Slow motion, graphical glitches, and crashes
Gnome-shell users may experience display issues when they switch to Wayland from X. One of the root cause might be the
CLUTTER_PAINT=disable-clipped-redraws:disable-culling set by yourself for Xorg-based gnome-shell. Just try to remove it from
/etc/environment or other rc files to see if everything goes back to normal.
Cannot open display: :0 with Electron-based applications
Make sure you have not set GDK_BACKEND=wayland. Setting it globally will break Electron apps.
- (20200206) sway) offers a VNC backend via since version 0.10. RDP backend has been removed. . (used by
- (20180401)  and for details. has now remote desktop enabled at compile time, see
- There was a merge of FreeRDP into Weston in 2013, enabled via a compile flag. The package has it enabled since version 6.0.0.
- SSH AUR is a transparent proxy for Wayland applications, with a wrapper command to run over
Input grabbing in games, remote desktop and VM windows
In contrast to Xorg, Wayland does not allow exclusive input device grabbing, also known as active or explicit grab (e.g. keyboard, mouse), instead, it depends on the Wayland compositor to pass keyboard shortcuts and confine the pointer device to the application window.
This change in input grabbing breaks current applications' behavior, meaning:
- Hotkey combinations and modifiers will be caught by the compositor and will not be sent to remote desktop and virtual machine windows.
- The mouse pointer will not be restricted to the application's window which might cause a parallax effect where the location of the mouse pointer inside the window of the virtual machine or remote desktop is displaced from the host's mouse pointer.
Wayland solves this by adding protocol extensions for Wayland and XWayland. Support for these extensions is needed to be added to the Wayland compositors. In the case of native Wayland clients, the used widget toolkits (e.g GTK, Qt) needs to support these extensions or the applications themselves if no widget toolkit is being used. In the case of Xorg applications, no changes in the applications or widget toolkits are needed as the XWayland support is enough.
These extensions are already included in, and supported by .
The related extensions are:
- XWayland keyboard grabbing protocol
- Compositor shortcuts inhibit protocol
- Relative pointer protocol
- Pointer constraints protocol
Supporting Wayland compositors:
- Mutter, GNOME's compositor since release 3.28
- wlroots supports relative-pointer and pointer-constraints
Supporting widget toolkits:
- GTK since release 3.22.18.