State of Wayland, 2012-04-08
darxus at chaosreigns.com
darxus at chaosreigns.com
Sun Apr 8 11:08:29 PDT 2012
This is far from official. If you have better information, please provide
it. HTML version: http://www.chaosreigns.com/wayland/state/
The reference compositor works with Intel, Radeon, and Nvidia
(Nouveau) open source drivers. Nouveau + OpenGL clients hangs.
XWayland, the ability to run X clients within Wayland, is
currently broken, in the middle of transitioning to using a
special X window manager. Tiago did some work on it, which has
not been committed. Other than that, DDX support for Intel video
exists, a software implementation exists but may need updating,
and someone has done some work on Radeon but not released source.
Nvidia / Nouveau support hasn't been touched.
Wayland usability is mostly down to applications migrating to GTK3
GTK+ 3.4.1 and QT5 appear to have complete Wayland support except
for client side decorations. EFL and Clutter appear to have
So any application should work with Wayland as long as it uses one
of these four toolkits, and it doesn't call any Xlib functions.
Unfortunately a number of GTK+ applications do call Xlib, through
gdk_x11_* functions, and they need to be wrapped in build-time
and run-time backend checks.
And while GTK3 was released over a year ago, QT5 only had
its first alpha release last week. While many GTK+ applications
haven't made the conversion yet, presumably Qt applications, for
the most part, haven't started.
GTK+ 3.4.0 has a bug causing it to break when the X11 and
Wayland backends are both built. The workaround has been applied
in master and will be included in the 3.4.1 release on April
The GTK graphics glitch was a cairo-gl bug, easy enough to
Rob Bradford has a branch of gtk that doesn't require
cairo-gl, which will be merged with master once 3.4 is branched
off. I've tested it. This should allow Ubuntu to enable the
Wayland backend in GTK in the October 2012 (12.10) release.
The only web browser I've tested that works is qtwebkit, which is
included with the QT5 source. Weston occasionally crashes when
running it. It seems likely that the snowshoe browser works,
The webkitgtk browser doesn't work. As expected, the
midori browser based on webkitgtk doesn't work.
Firefox has a long way to go.
Chrome / chromium might work, but I haven't seen how.
weston-terminal is actually pretty decent.
vte, based on gtk, works fine.
gnome-terminal seems likely to work, I just haven't tried
quite the right incantation yet.
Surprisingly, there don't seem to be any terminal applications
written in Qt or EFL. I haven't tried clutterm, which uses
Clutter, mostly because it says "This is a work in progress and
it's far from ready for every day use."
Of the 22 gtk applications I tried from the default Ubuntu
Precise menu (html5 video), 9 worked, and 13 didn't due to using
Xlib calls. 41% worked as packaged by Ubuntu (after I rebuilt GTK
* GTK+: Wayland and x11 backends simultaneously enabled is
* Ubuntu: Enable wayland backend in GTK+
* Totem: Add wayland support (remove Xlib calls).
* WebKitGTK+: Enable wayland support (remove Xlib calls).
The Nvidia proprietary + cairo-gl mess:
* Cairo: Dynamically load libGL in cairo-gl
* GTK+: Remove cairo-gl dependency from wayland backend,
fall back to software as weston does.
* Debian packaging: Add support for versioned provides. This
is 15 years old.
"It is better to die on your feet than to live on your knees."
- Emiliano Zapata, Mexican Revolution Leader
More information about the wayland-devel