Difference between revisions of "Wayland"

From ArchWiki
Jump to: navigation, search
m (Installation: Grammar fix)
(See also: add link to great article about Wayland debugging from Fedora Wiki)
 
(313 intermediate revisions by 100 users not shown)
Line 1: Line 1:
[[Category:X Server]]
+
[[Category:X server]]
[[zh-CN:Wayland]]
+
[[es:Wayland]]
{{Article summary start}}
+
[[fr:Wayland]]
{{Article summary text|A guide to installing and running the Wayland display server.}}
+
[[ja:Wayland]]
{{Article summary heading|Related}}
+
[[ru:Wayland]]
{{Article summary wiki|KMS}}
+
[[zh-hans:Wayland]]
{{Article summary wiki|Xorg}}
+
{{Related articles start}}
{{Article summary end}}
+
{{Related|KMS}}
 +
{{Related|Xorg}}
 +
{{Related|Mir}}
 +
{{Related articles end}}
  
'''Wayland''' is a new windowing protocol for Linux. Utilization of Wayland requires changes to and re-installation of parts of your system's software. For more information on Wayland see its [http://wayland.freedesktop.org/ homepage].
+
[http://wayland.freedesktop.org/ Wayland] is a protocol for a [[wikipedia:Compositing window manager|compositor]] to talk to its clients, as well as a library implementing this protocol. All major Linux desktop systems like Gnome, KDE do support Wayland, and there is also a reference implementation for a compositor called "Weston". [https://wayland.freedesktop.org/xserver.html XWayland] implements a compatibility layer to seamlessly run legacy X11 applications on Wayland.
  
{{Warning|Wayland is under heavy development.  Support can not be guaranteed and it may not function as you expect.}}
+
== Requirements ==
  
== Requirements ==
+
Wayland only works on systems using [[KMS]]. As Wayland is only a library, it is useless on its own: to replace the X Server you need a compositor such as [[#Weston]].
Currently Wayland will only work with on a system that is utilizing [[KMS]].
+
 
 +
=== Buffer API support ===
  
== Installation ==
+
For the GPU driver and Wayland composer to be compatible they must support the same buffer API. There are two main APIs: [[Wikipedia:Generic Buffer Management|GBM]] and [http://www.phoronix.com/scan.php?page=news_item&px=XDC2016-Device-Memory-API EGLStreams].
You need to build and install {{AUR|wayland-git}} and {{AUR|mesa-full-wayland}} from the [[AUR]]. Replacement of the Mesa stack is required because the stock one does not support Wayland.
 
  
== Usage ==
+
{| class="wikitable"
As Wayland is only a library, it is useless on its own. To use it, you need a compositor (like Weston), Weston demo applications, Qt5 (or Qt4 with QPA enabled) with Wayland plugin, and/or GTK+ with Wayland support.
+
|-
 +
! Buffer API !! GPU driver support !! Wayland compositor support
 +
|-
 +
| GBM || All except [[NVIDIA]] || All
 +
|-
 +
| EGLStreams || [[NVIDIA]] || [[GNOME]], [[Sway]] (from [http://phoronix.com/scan.php?page=news_item&px=Sway-Compositor-April 0.13])
 +
|-
 +
|}
  
 
== Weston ==
 
== Weston ==
 +
 +
Weston is the reference implementation of a Wayland compositor.
 +
 
=== Installation ===
 
=== Installation ===
You need to build and install {{AUR|weston-git}} from the [[AUR]].
+
 
 +
Install the {{Pkg|weston}} package.
  
 
=== Usage ===
 
=== Usage ===
Now that Wayland and its requirements are installed you should be ready to test it out. Try switching to a terminal and running:
 
$ weston-launch
 
Note I was having trouble with keyboard & mouse not working unless this was run as root
 
  
You can also try:  
+
{| class="wikitable" style="float: right; width: 40%; margin-left: 1em"
$ export EGL_DRIVER=/usr/lib/egl/egl_gallium.so
+
|+ '''''Keyboard Shortcuts''' (super = windows key - can be changed, see weston.ini)'' {{Ic|Ctrl-b}}
if you have troubles with your hardware's driver.
+
!Cmd
 +
!Action
 +
|-
 +
|{{ic|Ctrl+Alt+Backspace}}
 +
|Quit Weston
 +
|-
 +
|{{ic|Super+Scroll}} (or {{ic|PageUp}}/{{ic|PageDown}})
 +
|Zoom in/out of desktop
 +
|-
 +
|{{ic|Super+Tab}}
 +
|Switch windows
 +
|-
 +
|{{ic|Super+LMB}}
 +
|Move Window
 +
|-
 +
|{{ic|Super+MMB}}
 +
|Rotate Window !
 +
|-
 +
|{{ic|Super+RMB}}
 +
|Resize Window
 +
|-
 +
|{{ic|Super+Alt+Scroll}}
 +
|Change window opacity
 +
|-
 +
|{{ic|Super+K}}
 +
|Force Kill Active Window
 +
|-
 +
|{{ic|Super+KeyUp/KeyDown}}
 +
|Switch Prev/Next Workspace
 +
|-
 +
|{{ic|Super+Shift+KeyUp/KeyDown}}
 +
|Grab Current Window and Switch Workspace
 +
|-
 +
|{{ic|Super+F'''''n'''''}}
 +
|Switch to Workspace '''''n'''''
 +
|-
 +
|{{ic|Super+S}}
 +
|Take a screenshot
 +
|-
 +
|{{ic|Super+R}}
 +
|Record a screencast.
 +
|}
 +
 
 +
Now that Wayland and its requirements are installed you should be ready to test it out.  
 +
 
 +
It is possible to run Weston inside a running X session:
 +
$ weston
  
Then at a TTY you can run the demos:
+
Alternatively, to try to launch Weston natively, switch to a terminal and run:
 +
$ weston-launch
  
 +
Then at a TTY within Weston, you can run the demos. To launch a terminal emulator:
 
  $ weston-terminal
 
  $ weston-terminal
Should launch a terminal emulator.
 
  
 +
To move flowers around the screen:
 
  $ weston-flower  
 
  $ weston-flower  
Moves a flower around the screen.  This tests the frame protocol.
 
  
  $ weston-gears
+
To display images:
Runs glxgears on Wayland.
+
  $ weston-image image1.jpg image2.jpg...
  
  $ weston-image image1.jpg image2.jpg...
+
=== Configuration ===
Displays images.
+
Example configuration file for keyboard layout, module selection and UI modifications. See {{man|5|weston.ini|url=}} for full details. The Weston outputs differ slightly from {{ic|xorg.conf}}'s Monitors:
 +
 
 +
  $ ls /sys/class/drm
 +
card0
 +
card0-VGA-1
 +
card1
 +
card1-DVI-I-1
 +
card1-HDMI-A-1
 +
card1-VGA-2
 +
 
 +
{{ic|card0}} is the unused built-in video adapter. The add-on adapter {{ic|card1}} is cabled to one HDMI and one DVI monitor, so the output names are {{ic|HDMI-A-1}} and {{ic|DVI-I-1}}.
 +
 
 +
{{hc|~/.config/weston.ini|<nowiki>
 +
[core]
 +
# xwayland support
 +
modules=xwayland.so
 +
 
 +
[libinput]
 +
enable_tap=true
 +
 
 +
[shell]
 +
background-image=/usr/share/backgrounds/gnome/Aqua.jpg
 +
background-color=0xff002244
 +
panel-color=0x90ff0000
 +
locking=true
 +
animation=zoom
 +
close-animation=fade
 +
focus-animation=dim-layer
 +
#binding-modifier=ctrl
 +
#num-workspaces=6
 +
### for cursor themes install xcursor-themes pkg from Extra. ###
 +
#cursor-theme=whiteglass
 +
#cursor-size=24
 +
 
 +
### tablet options ###
 +
#lockscreen-icon=/usr/share/icons/gnome/256x256/actions/lock.png
 +
#lockscreen=/usr/share/backgrounds/gnome/Garden.jpg
 +
#homescreen=/usr/share/backgrounds/gnome/Blinds.jpg
 +
#animation=fade
 +
 
 +
###  for Laptop displays  ###
 +
#[output]
 +
#name=LVDS1
 +
#mode=1680x1050
 +
#transform=90
 +
 
 +
#[output]
 +
#name=VGA1
 +
# The following sets the mode with a modeline, you can get modelines for your preffered resolutions using the cvt utility
 +
#mode=173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync
 +
#transform=flipped
 +
 
 +
#[output]
 +
#name=X1
 +
#mode=1024x768
 +
#transform=flipped-270
 +
 
 +
[input-method]
 +
#path=/usr/lib/weston/weston-keyboard
 +
 
 +
[keyboard]
 +
keymap_rules=evdev
 +
#keymap_layout=gb,de
 +
#keymap_options=caps:ctrl_modifier,shift:both_capslock_cancel
 +
### keymap_options from /usr/share/X11/xkb/rules/base.lst ###
 +
numlock-on=true
 +
 
 +
[terminal]
 +
#font=DroidSansMono
 +
#font-size=14
 +
 
 +
[launcher]
 +
icon=/usr/share/icons/gnome/24x24/apps/utilities-terminal.png
 +
path=/usr/bin/weston-terminal
 +
 
 +
[launcher]
 +
icon=/usr/share/icons/gnome/24x24/apps/utilities-terminal.png
 +
path=/usr/bin/gnome-terminal
 +
 
 +
[launcher]
 +
icon=/usr/share/icons/hicolor/24x24/apps/firefox.png
 +
path=/usr/bin/firefox
 +
 
 +
[launcher]
 +
icon=/usr/share/weston/icon_flower.png
 +
path=/usr/bin/weston-flower
 +
 
 +
[screensaver]
 +
# Uncomment path to disable screensaver
 +
path=/usr/libexec/weston-screensaver
 +
duration=600
 +
</nowiki>
 +
}}
 +
 
 +
Minimal {{ic|weston.ini}} :
 +
{{hc|~/.config/weston.ini|<nowiki>
 +
[core]
 +
modules=xwayland.so
 +
 
 +
[keyboard]
 +
keymap_layout=gb
 +
 
 +
[output]
 +
name=LVDS1
 +
mode=1680x1050
 +
transform=90
 +
 
 +
[launcher]
 +
icon=/usr/share/icons/gnome/24x24/apps/utilities-terminal.png
 +
path=/usr/bin/weston-terminal
 +
 
 +
[launcher]
 +
icon=/usr/share/icons/hicolor/24x24/apps/firefox.png
 +
path=/usr/bin/firefox
 +
 
 +
</nowiki>
 +
}}
 +
 
 +
==== XWayland ====
 +
[[Install]] the {{Pkg|xorg-server-xwayland}} package.
 +
 
 +
When you want to run an X application from within Weston, it spins up Xwayland to service the request. The following configuration is shown above:
 +
 
 +
{{hc|~/.config/weston.ini|
 +
<nowiki>[core]
 +
modules=xwayland.so</nowiki>
 +
}}
 +
 
 +
==== Screencast recording ====
 +
Weston has build-in screencast recording which can be started and stopped by pressing the {{ic|Super+r}} key combination. Screencasts are saved to the file {{ic|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:
 +
 
 +
$ wcap-decode capture.wcap --yuv4mpeg2 > capture.y4m
 +
 
 +
The YUV file can then be transcoded to other formats using [[FFmpeg]].
 +
 
 +
==== High DPI displays ====
 +
 
 +
For [[wikipedia:Retina_Display|Retina]] or [[HiDPI]] displays, use:
 +
 
 +
{{hc|~/.config/weston.ini|
 +
<nowiki>[output]
 +
name=...
 +
scale=2</nowiki>
 +
}}
 +
 
 +
==== Shell font ====
 +
 
 +
Weston uses the default sans-serif font for window title bars, clocks, etc. See [[Font configuration#Replace or set default fonts]] for instructions on how to change this font.
 +
 
 +
== GUI libraries ==
 +
 
 +
See details on the [http://wayland.freedesktop.org/toolkits.html official website].
 +
 
 +
=== GTK+ 3 ===
 +
 
 +
The {{Pkg|gtk3}} package has the Wayland backend enabled. GTK+ will default to the X11 backend, but this can be overridden by modifying an environment variable: {{ic|GDK_BACKEND&#61;wayland}}.
 +
 
 +
=== Qt 5 ===
 +
The {{Grp|qt5}} package from the repositories has the Wayland support if {{Pkg|qt5-wayland}} is installed.
 +
To run a Qt 5 app with the Wayland plugin, set the {{ic|1=QT_QPA_PLATFORM=wayland-egl}} [[environment variable]]. For Arch, most QT applications do not work because of [https://bugreports.qt.io/browse/QTBUG-58423 QTBUG-58423], will be fixed with qt-5.9: https://codereview.qt-project.org/#/c/184278/ .
 +
 
 +
=== Clutter ===
 +
 
 +
The Clutter toolkit has a Wayland backend that allows it to run as a Wayland client. The backend is enabled in the official package in extra.
 +
 
 +
To run a Clutter app on Wayland, set {{ic|CLUTTER_BACKEND&#61;wayland}}.
 +
 
 +
=== SDL ===
 +
 
 +
Experimental wayland support is now in SDL 2.0.2 and enabled by default on Arch Linux.
 +
 
 +
To run a SDL application on Wayland, set {{ic|SDL_VIDEODRIVER&#61;wayland}}.
 +
 
 +
=== GLFW ===
 +
 
 +
Experimental wayland support is now in GLFW 3.1 and can be enabled with the {{ic|-DGLFW_USE_WAYLAND&#61;ON}} CMake option at compile time. You can also install the package {{AUR|glfw-wayland-git}} from the AUR.
 +
 
 +
=== EFL ===
 +
 
 +
EFL has complete Wayland support.
 +
To run a EFL application on Wayland, see Wayland [http://wayland.freedesktop.org/efl.html project page].
 +
 
 +
== Window managers and desktop shells ==
 +
 
 +
{| class="wikitable sortable"
 +
! Name
 +
! Type
 +
! Description
 +
|-
 +
| GNOME
 +
| Stacking
 +
| See [[GNOME#Starting GNOME]].
 +
|-
 +
| sway
 +
| Tiling
 +
| [[Sway]] is an i3-compatible window manager for Wayland. [https://github.com/SirCmpwn/sway Github]
 +
|-
 +
| Enlightenment
 +
| Stacking
 +
| [https://www.enlightenment.org/about-wayland More Info]
 +
|-
 +
| KDE Plasma
 +
| Stacking
 +
| See [[KDE#Starting Plasma]]
 +
|-
 +
| Orbment
 +
| Tiling
 +
| [https://github.com/Cloudef/orbment orbment] (previously loliwm) is a tiling WM for Wayland.
 +
|-
 +
| Velox
 +
| Tiling
 +
| [[Velox]] is a simple window manager based on swc. It is inspired by [[dwm]] and [[xmonad]].
 +
|-
 +
| Orbital
 +
| Stacking
 +
| [https://github.com/giucam/orbital 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
 +
| [https://github.com/lirios/shell Liri Shell] is the desktop shell for [[Liri]], built using QtQuick and QtCompositor as a compositor for Wayland.
 +
|-
 +
| Maynard
 +
| ''(Unclear)''
 +
| [https://github.com/raspberrypi/maynard 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)''
 +
| [https://github.com/evil0sheep/motorcar Motorcar] is a wayland compositor to explore 3D windowing using Virtual Reality.
 +
|-
 +
| Way Cooler
 +
| Tiling
 +
|  {{AUR|way-cooler}} is a customizeable (lua config files) Wayland compositor written in Rust. Inspired by i3 and awesome.
 +
|-
 +
| Maze Compositor
 +
| Floating 3D
 +
| [https://github.com/capisce/mazecompositor Maze Compositor] is a 3D Qt based wayland compositor
 +
|-
 +
| Grefsen
 +
| Floating
 +
| [https://github.com/ec1oud/grefsen Grefsen] is a Qt/Wayland compositor providing a minimal desktop environment.
 +
|}
 +
 
 +
Some of installed wayland desktop clients might store information in {{ic|/usr/share/wayland-sessions/*.desktop}} files about how to start them in wayland.
  
$ weston-view doc1.pdf doc2.pdf...
+
==Troubleshooting==
Displays PDF files.
 
  
== Qt ==
 
  
=== Installation ===
+
=== Running graphical applications as root ===
You need to build and install {{AUR|qt-qpa}} from [[AUR]]. It contains a development version of Qt 4.8 compiled with QPA (Lighthouse) support. It installs into /opt/qt-qpa because it's binary incompatible with non-QPA versions of Qt (like the stock one).
 
  
=== Usage ===
+
Trying to run a graphical application as root via [[su]], [[sudo]] or [[polkit|pkexec]] in a Wayland session (''e.g.'' [[GParted]] or [[Gedit]]), be it in a terminal emulator or from a graphical component, will fail with an error similar to this:
At first, you need a working Wayland compositor, like the one from demo applications, or an experimental version of KWin.
 
  
Then compile any qmake-based Qt project:
+
{{bc|$ sudo gedit
$ export PATH=/opt/qt-qpa/bin:$PATH
+
No protocol specified
$ export LD_LIBRARY_PATH=/opt/qt-qpa/lib
+
Unable to init server: Could not connect: Connection refused
$ qmake
 
$ make
 
  
And run it by executing the compiled binary:
+
(gedit:2349): Gtk-WARNING **: cannot open display: :0
$ export LD_LIBRARY_PATH=/opt/qt-qpa/lib
+
}}
$ export QT_QPA_PLATFORM=waylandgl
 
$ ./binaryname
 
  
=== Qt Compositor ===
+
Before Wayland, running GUI applications with elevated privileges could be properly implemented by creating a [[Polkit]] policy, or more dangerously done by running the command in a terminal by prepending the command with {{ic|sudo}}; but under (X)Wayland this does not work anymore as the default has been made to only allow the user who started the X server to connect clients to it (see the [https://bugzilla.redhat.com/show_bug.cgi?id=1266771 bug report] and [https://cgit.freedesktop.org/xorg/xserver/commit/?id=c4534a3 the] [https://cgit.freedesktop.org/xorg/xserver/commit/?id=4b4b908 upstream] [https://cgit.freedesktop.org/xorg/xserver/commit/?id=76636ac commits] it refers to).
There is ongoing work to make [http://labs.qt.nokia.com/2011/03/18/multi-process-lighthouse/ Qt-Compositor], a base layer to make custom Qt compositors on top of Wayland.
 
  
== Other GUI libraries ==
+
The most straightforward workaround is to use [[xhost]] to temporarily allow the root user to access the local user's X session. To do so, execute the following command as the current (unprivileged) user[https://bugzilla.redhat.com/show_bug.cgi?id=1274451#c64]:
([http://wayland.freedesktop.org/toolkits.html page from official website])
+
  xhost si:localuser:root
  
===GTK+===
+
To remove this access after the application has been closed:
 +
  xhost -si:localuser:root
  
With GTK+ 3.0, GTK+ gained support for multiple backends at runtime and can switch between backends in the same way Qt can with lighthouse. The Wayland support is on the upstream GTK+ master branch but disabled by default. To try GTK+ on Wayland, check out gtk+ and pass <code>--enable-wayland</code> to configure:
+
{{Note|1=This [https://bugzilla.gnome.org//show_bug.cgi?id=772875 GNOME bug report] suggests two other workarounds, with one specific to editing text files.}}
  
$ git clone git://git.gnome.org/gtk+
+
{{Style|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.}}
$ cd gtk+
 
$ ./configure --prefix=/usr --enable-x11-backend --enable-wayland-backend --enable-debug=yes
 
$ make
 
  
When both Wayland and X backends are enabled, GTK+ will default to the X11 backend, but this can be overridden by setting the <code>GDK_BACKEND</code> environment variable to <code>wayland</code>.
+
=== LLVM assertion failure ===
 +
If you get an LLVM assertion failure, you need to rebuild {{Pkg|mesa}} without Gallium LLVM until this problem is fixed.  
  
{{Note|Alternatively, you can install {{AUR|gtk3-git}} from the [[AUR]].}}
+
This may imply disabling some drivers which require LLVM.
 +
You may also try exporting the following, if having problems with hardware drivers:
  
===Clutter===
+
$ export EGL_DRIVER=/usr/lib/egl/egl_gallium.so
  
The Clutter toolkit has a Wayland backend that allows it to run as a Wayland client. The backend is in the master branch of the [http://git.gnome.org/browse/clutter main repo] and can be activated by passing <code>--with-flavour=wayland</code> to the configure script.
+
=== 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 {{ic|1=CLUTTER_PAINT=disable-clipped-redraws:disable-culling}} set by yourself for Xorg-based gnome-shell. Just try to remove it from {{ic|/etc/environment}} or other rc files to see if everything goes back to normal.
  
===SDL===
+
=== nemo ===
 +
(20161229) prevent that the desktop is created <ref>[https://github.com/linuxmint/nemo/issues/1343 nemo issue 1343]</ref>
 +
gsettings set org.nemo.desktop show-desktop-icons false
  
Benjamin Franzke is working on a port of SDL to Wayland, it's available in his [http://cgit.freedesktop.org/~bnf/sdl-wayland/ sdl-wayland repo] on freedesktop.org. Further development upon Benjamins work was done by Andre Heider in his [https://github.com/dhewg/libsdl/tree/wl wayland branch] of libsdl.
+
=== X11 on tty1, wayland on tty2 ===
 +
(20161209) windows of gnome applications end up on tty2 no matter where started ([https://bugzilla.gnome.org/show_bug.cgi?id=774775 gnome issue 774775)]
  
===EFL===
+
=== gnome wayland on tty1, weston on tty2 ===
 +
(20170106) apps started on gnome with WAYLAND_DISPLAY set to westen make it not respond any more ([https://bugs.freedesktop.org/show_bug.cgi?id=99489 wayland issue 99489])
  
EFL has complete Wayland support. Please see [http://trac.enlightenment.org/e/wiki/Wayland here] for details.
+
=== weston-terminal ===
 +
(20161229) core dump when started on gnome
  
==Window managers and desktop shells==
+
=== liteide ===
 +
(20161229) [https://github.com/visualfc/liteide/issues/734 core dump]] on gnome and weston.
  
===KDE===
+
=== screen recording ===
 +
(20161229) As of November 2016 there is an ongoing discussion how to implement screen recording. Currently the compositors implement at least basic functionality.
  
The KDE Wayland support is expected to come in three phases, with the first two phases expected to be completed this year during the KDE SC 4.8 and 4.9 development cycles. Please see [http://community.kde.org/KWin/Wayland here] for details.
+
=== remote display ===
 +
(20161229) there was a merge of FreeRDP into weston in 2013, enabled via compile time switch. The arch linux weston package currently has it not enabled.
  
Also, there is [http://blog.martin-graesslin.com/blog/2011/03/kwin-at-gsoc-2011/ early work] to make it possible to run KWin (KDE's window manager) on Wayland.
+
=== Input grabbing in games, remote desktop and VM windows  ===
  
===GNOME===
+
In contrast to Xorg, Wayland does not allow exclusive input device grabbing (e.g. [https://tronche.com/gui/x/xlib/input/XGrabKeyboard.html keyboard], [https://tronche.com/gui/x/xlib/input/XGrabPointer.html mouse]), instead, it depends on the Wayland compositor to pass keyboard shortcuts (extensions in development) and confine the pointer device to the application window.
  
GNOME will be ported to Wayland in a future version.
+
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.
  
===Unity===
+
Wayland protocol extensions for keyboard handling were [https://lists.freedesktop.org/archives/wayland-devel/2017-May/034130.html proposed for both] [https://lists.freedesktop.org/archives/wayland-devel/2017-May/034131.html XWayland] and [https://lists.freedesktop.org/archives/wayland-devel/2017-May/034132.html native Wayland clients], there are already extensions for handling of pointer devices ([https://cgit.freedesktop.org/wayland/wayland-protocols/tree/unstable/relative-pointer/relative-pointer-unstable-v1.xml relative pointer motion events] and [https://cgit.freedesktop.org/wayland/wayland-protocols/tree/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml constraining pointer motions]) and similar support [https://lists.x.org/archives/xorg-devel/2016-September/050975.html already been added to XWayland].
Ubuntu desktop shell Unity, using Compiz window manager, was [http://www.markshuttleworth.com/archives/551 announced] to be ported to Wayland.
 
  
==See also==
+
Support for these extensions need to be added to the Wayland compositor, and in the case of native Wayland clients probably also to the widget toolkit (e.g. GTK, QT) and the application itself. Currently, there are no known compositors supporting all these extensions.
* [[Cursor Themes]]
 
  
==External links==
+
== See also ==
 +
* [https://fedoraproject.org/wiki/How_to_debug_Wayland_problems Article about Wayland debugging on Fedora Wiki]
 +
* [[Cursor themes]]
 
* [https://bbs.archlinux.org/viewtopic.php?id=107499 Arch Linux forum discussion]
 
* [https://bbs.archlinux.org/viewtopic.php?id=107499 Arch Linux forum discussion]
 
* [http://wayland.freedesktop.org/docs/html/ Wayland documentation online]
 
* [http://wayland.freedesktop.org/docs/html/ Wayland documentation online]

Latest revision as of 15:04, 26 May 2017

Related articles

Wayland is a protocol for a compositor to talk to its clients, as well as a library implementing this protocol. All major Linux desktop systems like Gnome, KDE do support Wayland, and there is also a reference implementation for a compositor called "Weston". XWayland implements a compatibility layer to seamlessly run legacy X11 applications on Wayland.

Requirements

Wayland only works on systems using KMS. As Wayland is only a library, it is useless on its own: to replace the X Server you need a compositor such as #Weston.

Buffer API support

For the GPU driver and Wayland composer to be compatible they must support the same buffer API. There are two main APIs: GBM and EGLStreams.

Buffer API GPU driver support Wayland compositor support
GBM All except NVIDIA All
EGLStreams NVIDIA GNOME, Sway (from 0.13)

Weston

Weston is the reference implementation of a Wayland compositor.

Installation

Install the weston package.

Usage

Keyboard Shortcuts (super = windows key - can be changed, see weston.ini) Ctrl-b
Cmd Action
Ctrl+Alt+Backspace Quit Weston
Super+Scroll (or PageUp/PageDown) Zoom in/out of desktop
Super+Tab Switch windows
Super+LMB Move Window
Super+MMB Rotate Window !
Super+RMB Resize Window
Super+Alt+Scroll Change window opacity
Super+K Force Kill Active Window
Super+KeyUp/KeyDown Switch Prev/Next Workspace
Super+Shift+KeyUp/KeyDown Grab Current Window and Switch Workspace
Super+Fn Switch to Workspace n
Super+S Take a screenshot
Super+R Record a screencast.

Now that Wayland and its requirements are installed you should be ready to test it out.

It is possible to run Weston inside a running X session:

$ weston

Alternatively, to try to launch Weston natively, switch to a terminal and run:

$ weston-launch

Then at a TTY within Weston, you can run the demos. To launch a terminal emulator:

$ weston-terminal

To move flowers around the screen:

$ weston-flower 

To display images:

$ weston-image image1.jpg image2.jpg...

Configuration

Example configuration file for keyboard layout, module selection and UI modifications. See weston.ini(5) for full details. The Weston outputs differ slightly from xorg.conf's Monitors:

$ ls /sys/class/drm
card0
card0-VGA-1
card1
card1-DVI-I-1
card1-HDMI-A-1
card1-VGA-2

card0 is the unused built-in video adapter. The add-on adapter card1 is cabled to one HDMI and one DVI monitor, so the output names are HDMI-A-1 and DVI-I-1.

~/.config/weston.ini
[core]
# xwayland support
modules=xwayland.so

[libinput]
enable_tap=true

[shell]
background-image=/usr/share/backgrounds/gnome/Aqua.jpg
background-color=0xff002244
panel-color=0x90ff0000
locking=true
animation=zoom
close-animation=fade
focus-animation=dim-layer
#binding-modifier=ctrl
#num-workspaces=6
### for cursor themes install xcursor-themes pkg from Extra. ###
#cursor-theme=whiteglass
#cursor-size=24

### tablet options ###
#lockscreen-icon=/usr/share/icons/gnome/256x256/actions/lock.png
#lockscreen=/usr/share/backgrounds/gnome/Garden.jpg
#homescreen=/usr/share/backgrounds/gnome/Blinds.jpg
#animation=fade

###  for Laptop displays  ###
#[output]
#name=LVDS1
#mode=1680x1050
#transform=90

#[output]
#name=VGA1
# The following sets the mode with a modeline, you can get modelines for your preffered resolutions using the cvt utility
#mode=173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync
#transform=flipped

#[output]
#name=X1
#mode=1024x768
#transform=flipped-270

[input-method]
#path=/usr/lib/weston/weston-keyboard

[keyboard]
keymap_rules=evdev
#keymap_layout=gb,de
#keymap_options=caps:ctrl_modifier,shift:both_capslock_cancel
### keymap_options from /usr/share/X11/xkb/rules/base.lst ###
numlock-on=true

[terminal]
#font=DroidSansMono
#font-size=14

[launcher]
icon=/usr/share/icons/gnome/24x24/apps/utilities-terminal.png
path=/usr/bin/weston-terminal

[launcher]
icon=/usr/share/icons/gnome/24x24/apps/utilities-terminal.png
path=/usr/bin/gnome-terminal

[launcher]
icon=/usr/share/icons/hicolor/24x24/apps/firefox.png
path=/usr/bin/firefox

[launcher]
icon=/usr/share/weston/icon_flower.png
path=/usr/bin/weston-flower

[screensaver]
# Uncomment path to disable screensaver
path=/usr/libexec/weston-screensaver
duration=600

Minimal weston.ini :

~/.config/weston.ini
[core]
modules=xwayland.so

[keyboard]
keymap_layout=gb

[output]
name=LVDS1
mode=1680x1050
transform=90

[launcher]
icon=/usr/share/icons/gnome/24x24/apps/utilities-terminal.png
path=/usr/bin/weston-terminal

[launcher]
icon=/usr/share/icons/hicolor/24x24/apps/firefox.png
path=/usr/bin/firefox


XWayland

Install the xorg-server-xwayland package.

When you want to run an X application from within Weston, it spins up Xwayland to service the request. The following configuration is shown above:

~/.config/weston.ini
[core]
modules=xwayland.so

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:

$ wcap-decode capture.wcap --yuv4mpeg2 > capture.y4m

The YUV file can then be transcoded to other formats using FFmpeg.

High DPI displays

For Retina or HiDPI displays, use:

~/.config/weston.ini
[output]
name=...
scale=2

Shell font

Weston uses the default sans-serif font for window title bars, clocks, etc. See Font configuration#Replace or set default fonts for instructions on how to change this font.

GUI libraries

See details on the official website.

GTK+ 3

The gtk3 package has the Wayland backend enabled. GTK+ will default to the X11 backend, but this can be overridden by modifying an environment variable: GDK_BACKEND=wayland.

Qt 5

The qt5 package from the repositories has the Wayland support if qt5-wayland is installed. To run a Qt 5 app with the Wayland plugin, set the QT_QPA_PLATFORM=wayland-egl environment variable. For Arch, most QT applications do not work because of QTBUG-58423, will be fixed with qt-5.9: https://codereview.qt-project.org/#/c/184278/ .

Clutter

The Clutter toolkit has a Wayland backend that allows it to run as a Wayland client. The backend is enabled in the official package in extra.

To run a Clutter app on Wayland, set CLUTTER_BACKEND=wayland.

SDL

Experimental wayland support is now in SDL 2.0.2 and enabled by default on Arch Linux.

To run a SDL application on Wayland, set SDL_VIDEODRIVER=wayland.

GLFW

Experimental wayland support is now in GLFW 3.1 and can be enabled with the -DGLFW_USE_WAYLAND=ON CMake option at compile time. You can also install the package glfw-wayland-gitAUR from the AUR.

EFL

EFL has complete Wayland support. To run a EFL application on Wayland, see Wayland project page.

Window managers and desktop shells

Name Type Description
GNOME Stacking See GNOME#Starting GNOME.
sway Tiling Sway is an i3-compatible window manager for Wayland. Github
Enlightenment Stacking More Info
KDE Plasma Stacking See KDE#Starting Plasma
Orbment Tiling orbment (previously loliwm) is a tiling WM for Wayland.
Velox Tiling 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 customizeable (lua config files) Wayland compositor written in Rust. Inspired by i3 and awesome.
Maze Compositor Floating 3D Maze Compositor is a 3D Qt based wayland compositor
Grefsen Floating Grefsen is a Qt/Wayland compositor providing a minimal desktop environment.

Some of installed wayland desktop clients might store information in /usr/share/wayland-sessions/*.desktop files about how to start them in wayland.

Troubleshooting

Running graphical applications as root

Trying to run a graphical application as root via su, sudo or pkexec in a Wayland session (e.g. GParted or Gedit), be it in a terminal emulator or from a graphical component, will fail with an error similar to this:

$ sudo gedit
No protocol specified
Unable to init server: Could not connect: Connection refused

(gedit:2349): Gtk-WARNING **: cannot open display: :0

Before Wayland, running GUI applications with elevated privileges could be properly implemented by creating a Polkit policy, or more dangerously done by running the command in a terminal by prepending the command with sudo; but under (X)Wayland this does not work anymore as the default has been made to only allow the user who started the X server to connect clients to it (see the bug report and the upstream commits it refers to).

The most straightforward workaround is to use xhost to temporarily allow the root user to access the local user's X session. To do so, execute the following command as the current (unprivileged) user[1]:

 xhost si:localuser:root

To remove this access after the application has been closed:

 xhost -si:localuser:root
Note: This GNOME bug report suggests two other workarounds, with one specific to editing text files.

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements.Tango-edit-clear.png

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.

nemo

(20161229) prevent that the desktop is created <ref>nemo issue 1343</ref>

gsettings set org.nemo.desktop show-desktop-icons false

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 westen make it not respond any more (wayland issue 99489)

weston-terminal

(20161229) core dump when started on gnome

liteide

(20161229) core dump] on gnome and weston.

screen recording

(20161229) As of November 2016 there is an ongoing discussion how to implement screen recording. Currently the compositors implement at least basic functionality.

remote display

(20161229) there was a merge of FreeRDP into weston in 2013, enabled via compile time switch. The arch linux weston package currently has it not enabled.

Input grabbing in games, remote desktop and VM windows

In contrast to Xorg, Wayland does not allow exclusive input device grabbing (e.g. keyboard, mouse), instead, it depends on the Wayland compositor to pass keyboard shortcuts (extensions in development) 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 protocol extensions for keyboard handling were proposed for both XWayland and native Wayland clients, there are already extensions for handling of pointer devices (relative pointer motion events and constraining pointer motions) and similar support already been added to XWayland.

Support for these extensions need to be added to the Wayland compositor, and in the case of native Wayland clients probably also to the widget toolkit (e.g. GTK, QT) and the application itself. Currently, there are no known compositors supporting all these extensions.

See also