GNOME's Mutter Loses Some Of Its X11 Dependence
Written by Michael Larabel in GNOME on 10 September 2017 at 07:31 AM EDT. 34 Comments
GNOME --
One of the interesting Google Summer of Code projects this year associated with the GNOME project was on reworking the Mutter compositor from requiring X11/XWayland code-paths for starting the Wayland compositor.

Student developer Armin Krezović worked to address the issue that even when Mutter is acting as a Wayland compostior rather than just an X window manager, the X11 support is still present and there's a hard dependency on XWayland being present, even if it goes unused. Armin was partially successful in his summer work in allowing Mutter to act as a Wayland-only compositor, free from any XWayland support if so desired.

Armin was able to make Mutter work on Wayland without any X bits present or XWayland needing to be started. He also had a goal of making Wayland clients start without X11 support being present, but he didn't have time to accomplish that goal.

Those interested in this GNOME Mutter GSoC work can find a recap via this blog post. The patches are currently staged via GitHub. With them, Mutter can be started with a --no-x11 switch if you wish to run Mutter on Wayland without any legacy support.
About The Author
Author picture

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter or contacted via MichaelLarabel.com.

Related GNOME News
Popular News