If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

So you can savely install this without destabilizing your system. The maintainer of the xwayland-git package will merge this so that you can use your AUR wrapper. For now just run makepkg -si in the directory containing my PKGBUILD.

After that XWayland works just out of the box with compositors that use the new XWayland apporach like the development version of weston so install weston-git or wait for weston 1.15 to be released in the next days. You can use any open source driver.

The mutter-wayland 3.12 package in Arch Linux doesn't have the XWayland DDX patch, but it would be interesting to try and just backport these patches to the 3.12 version and rebuild the package with it.

So you can savely install this without destabilizing your system. The maintainer of the xwayland-git package will merge this so that you can use your AUR wrapper. For now just run makepkg -si in the directory containing my PKGBUILD.

Ah, that's good to read. I tried to build XWayland before, however it failed somehow.

Comment

What advantage does XWayland have? Its a additional Layer at best its not slower than native X-server or am I wrong here?

So the question is when does the real thing come, without Xserver?

XWayland is it's own tiny binary server (just 1.8 MB) to provide a fallback for applications that can't speak natively to the Wayland compositor. Most GTK3 apps like Gnome Applications run native on Wayland. Qt4 and apps that make direct calls to X without a toolkit would not work otherwise on a Wayland desktop. It's rootless so the legacy X application is an isolated Window using XWayland while everything else runs on the Wayland compositor like Mutter for Gnome. It works great already. Gnome 3.12 on Wayland is already the real thing.

I built the mutter-wayland package to use a snapshot after the 3.12 release and after support for the new XWayland DDX was added. After that selecting Gnome on Wayland from GDM launches the Wayland desktop and everything works aslong as you use the open source drivers.

Comment

Thanks a lot blackout23 for the pkgbuilds, I finally managed to run GNOME on Wayland and I can only say that I'm really stunned by how things are really close to the fully-working state. I was even wondering if it failed and just fell back to traditional X11 as almost every application including KDE ones ran flawlessly and looked integrated :

There's some issues like no pointer acceleration, very bare touchpad support and windows sometimes refusing to move or resize (but can do it via context menus), and I managed to crash mutter with gwenview, but otherwise most of the stuff surprisingly just works.

Well on my Mobility HD3650, Gnome Shell isn't smooth on Wayland (nothing unbeareable tho) but it's not even on X11, while Kwin on X11 and Weston are butter smooth.
So the performance is comparable I would say. I believe Mutter (regardless of X11/Wayland) needs some optimisation yet.