Revision as of 16:29, 13 June 2018

Wayland is a protocol for a compositing window manager to talk to its clients, as well as a library implementing the protocol. Many major Linux desktop environments, like GNOME and KDE, support Wayland. There is also a compositor reference implementation called Weston. XWayland implements a compatibility layer to seamlessly run legacy X11 applications on Wayland.

Screencast recording

Weston has build-in screencast recording which can be started and stopped by pressing the Super+r key combination. Screencasts are saved to the file capture.wcap in the current working directory of Weston.

The WCAP format is a lossless video format specific to Weston, which only records the difference in frames. To be able to play the recorded screencast, the WCAP file will need to be converted to a format which a media player can understand. First, convert the capture to the YUV pixel format:

Velox is a simple window manager based on swc. It is inspired by dwm and xmonad.

Orbital

Stacking

Orbital is a Wayland compositor and shell, using Qt5 and Weston. The goal of the project is to build a simple yet flexible and good looking Wayland desktop. It is not a full fledged DE but rather the analogue of a WM in the X11 world, such as Awesome or Fluxbox.

Liri Shell

Stacking

Liri Shell is the desktop shell for Liri, built using QtQuick and QtCompositor as a compositor for Wayland.

Maynard

(Unclear)

Maynard is a desktop shell client for Weston based on GTK. It was based on weston-gtk-shell, a project by Tiago Vignatti.

Motorcar

(Unclear)

Motorcar is a Wayland compositor to explore 3D windowing using virtual reality.

Way Cooler

Tiling

way-coolerAUR is a customizable (Lua config files) Wayland compositor written in Rust. Inspired by i3 and awesome.

Troubleshooting

Running graphical applications as root

This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.

Reason: Many of these subsections should go into a "Known issues" section (i.e., there is no solution currently). Additionally prepending a date is not needed. (Discuss in Talk:Wayland#)

LLVM assertion failure

If you get an LLVM assertion failure, you need to rebuild mesa without Gallium LLVM until this problem is fixed.

This may imply disabling some drivers which require LLVM.
You may also try exporting the following, if having problems with hardware drivers:

$ export EGL_DRIVER=/usr/lib/egl/egl_gallium.so

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.

X11 on tty1, Wayland on tty2

(20161209) windows of GNOME applications end up on tty2 no matter where started (GNOME issue 774775)

GNOME Wayland on tty1, Weston on tty2

(20170106) apps started on GNOME with WAYLAND_DISPLAY set to weston make it not respond any more (Wayland issue 99489)

remote display

(20161229) there was a merge of FreeRDP into Weston in 2013, enabled via a compile flag. The weston package does not have it enabled.

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 won't 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.