Except it doesn't work well, at least with the intel driver.
A few months ago it actually worked for a short time, even with OpenGL, but it was very crashy and X clients would often just lose the connection.
A few weeks ago it just segfaulted the xserver when starting any X client in weston on a tty and when starting an X client using opengl in weston in X. A few weeks past that it still did the same.
Now there were a few commits to xwayland and the intel driver so I tested it again. I used the wayland/weston versions from archlinux repos and xwayland/xf86-video-intel from git. First, I had to google a weston 1.0.5 tarball since
http://freedesktop.org/ is 503.
Again. What's with that website, that it's unavailable so often?
Positive: xwayland in weston as an X client works well now, even with opengl.
Negative: In a tty, xwayland still segfaults when starting any x client (I tried xterm):
Code:
[ 3326.427] (WW) intel(0): drmSetMaster failed: Permission denied
[ 3326.427]
[ 3326.427] Backtrace:
[ 3326.428] 0: /opt/xwayland/bin/Xorg (xorg_backtrace+0x36) [0x55dbf6]
[ 3326.428] 1: /opt/xwayland/bin/Xorg (0x400000+0x161b19) [0x561b19]
[ 3326.428] 2: /usr/lib/libpthread.so.0 (0x7f6eea488000+0xf1e0) [0x7f6eea4971e0]
[ 3326.428] 3: /opt/xwayland/lib/xorg/modules/drivers/intel_drv.so (0x7f6ee6c21000+0x147b8) [0x7f6ee6c357b8]
[ 3326.428] 4: /opt/xwayland/lib/xorg/modules/drivers/intel_drv.so (0x7f6ee6c21000+0x1575e) [0x7f6ee6c3675e]
[ 3326.428] 5: /opt/xwayland/lib/xorg/modules/drivers/intel_drv.so (0x7f6ee6c21000+0x15cb8) [0x7f6ee6c36cb8]
[ 3326.428] 6: /opt/xwayland/bin/Xorg (AddScreen+0x189) [0x434979]
[ 3326.428] 7: /opt/xwayland/bin/Xorg (InitOutput+0x28e) [0x4726ae]
[ 3326.428] 8: /opt/xwayland/bin/Xorg (0x400000+0x23646) [0x423646]
[ 3326.428] 9: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f6ee9520a15]
[ 3326.428] 10: /opt/xwayland/bin/Xorg (0x400000+0x23abd) [0x423abd]
[ 3326.428]
[ 3326.428] Segmentation fault at address (nil))
I don't see where exactly the permission problem is, so I don't really know how to workaround it. weston-launch at least has +s.
So if they have an accelerated X client in MIR, they are de facto already better than wayland/weston.
(Not to forget, it crashed my intel driver, lots of:
Code:
[ 3374.657397] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 3374.657402] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D46E (len 62, WS 0, PS 0) @ 0xD48A
[ 3379.665858] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
)