Mir (display server)

Mir (display server)
Name	Mir
Developer	Canonical Ltd.
Released	2013
Programming language	C++
Operating system	Ubuntu (operating system)
Platform	Linux (kernel)
Genre	Display server
License	GNU Lesser General Public License

Mir (display server) is a display server protocol and reference implementation originally developed by Canonical Ltd. for Ubuntu (operating system) and related Ubuntu Touch projects. It was announced as part of Canonical's effort to unify display handling across desktop and mobile products and to provide an alternative to X Window System and the emerging Wayland (display server protocol). Mir evolved from a platform-specific initiative into a more general-purpose compositor with support for a variety of Linux (kernel) distributions, mobile devices, and embedded platforms.

Overview

Mir implements a compositor and protocol that mediates between kernel mode setting and graphics drivers and client Wayland (display server protocol)-style surfaces, providing APIs for OpenGL and Vulkan rendering. The project was positioned alongside other display technologies such as X.Org Server, Weston, GNOME Shell, KDE Plasma, and Android (operating system) compositor components. Canonical framed Mir as enabling convergence across desktop, tablet, and smartphone form factors similar to initiatives from Microsoft and Apple Inc. while interfacing with graphics stacks like Mesa (computer graphics), NVIDIA, and Intel Corporation drivers.

History and Development

Mir's announcement in 2013 followed Canonical's earlier work on Ubuntu Touch and integration efforts with Unity (user interface). The move prompted public discussion among contributors to X.Org Foundation, Freedesktop.org, and the Wayland community, as well as responses from distributions such as Debian, Fedora, and openSUSE. Development involved engineers from Canonical and collaborators with backgrounds at Red Hat, Intel Corporation, and Collabora Ltd.. Over time Mir's roadmap shifted from a Canonical-centric deployment to a community-oriented project, accepting contributions via Launchpad (software), GitHub, and mailings used by Kernel.org and Freedesktop.org projects. Key milestones included support for Wayland protocol compatibility layers, adoption by projects such as MATE (software), and removal of the Unity 8 dependency after Canonical reprioritized desktop strategy.

Architecture and Components

Mir's architecture comprises a core compositor, input abstraction, and backends for multiple graphics stacks. Components include a display server daemon, client APIs, and backend modules for Direct Rendering Manager, Wayland (display server protocol)-style clients, and legacy X.Org Server clients via compatibility layers. The codebase, written mainly in C++, uses libraries and toolkits like Qt (software), GTK, GLX, and EGL for graphics context management, and integrates with systemd on modern Ubuntu (operating system) releases. Mir also provides platform-specific backends for devices from vendors such as NVIDIA, AMD, and ARM Holdings-based SoC vendors, and can interoperate with window managers used by KDE Plasma and GNOME Shell.

Wayland and X11 Compatibility

Mir offers protocol translation and bridging to support clients targeting Wayland (display server protocol) and the legacy X Window System/X.Org Server. Compatibility layers include implementations of the Wayland protocol and XWayland-like functionality enabling X11 (protocol) applications to run atop Mir. This interoperability was important for desktop environments and toolkits such as Qt (software), GTK, Electron (software framework), Firefox, and LibreOffice during transition phases. The project worked with Wayland compositor implementers and standards maintained at Freedesktop.org to ensure consistent behavior across compositors like Weston and alternatives such as sway (software).

Adoption and Implementations

Initial targets for Mir included Ubuntu Touch, Ubuntu Desktop, and Canonical-backed OEM initiatives. After strategic shifts at Canonical, community adoption diversified: embedded vendors, appliance makers, and independent distributions explored Mir for kiosk systems, automotive HMI projects, and IoT devices. Implementations and ports emerged for distributions including Ubuntu (operating system), Debian, Arch Linux, and openSUSE, and Mir was used in projects integrating toolkits like Qt for Embedded and commercial stacks from Collabora Ltd. and SUSE. Partners in the ecosystem included hardware vendors such as Intel Corporation, NVIDIA, ARM Holdings, and companies building automotive infotainment systems.

Criticism and Controversy

Mir's introduction generated debate among stakeholders in the X.Org Foundation and Wayland communities, with critics pointing to fragmentation, duplicate effort, and potential disruption to established projects like GNOME Shell and KDE Plasma. Discussions referenced governance norms followed by Freedesktop.org, community reactions from distributions such as Debian and Fedora, and commentary in technical media that compared Mir's roadmap to Canonical's previous strategic shifts involving Unity (user interface). The licensing model and decision-making process at Canonical were scrutinized by contributors from Red Hat and independent developers, leading to public discourse across forums, bug trackers, and mailing lists associated with Launchpad (software) and GitHub.

Security and Performance

Mir emphasizes security features such as client isolation, access control for GPU resources mediated via Direct Rendering Manager and Linux (kernel) primitives, and sandboxing approaches used alongside AppArmor and containerization technologies championed by Docker (software) and LXC (software). Performance considerations in Mir include low-latency input handling, efficient buffer management leveraging EGL and Vulkan (API), and optimizations to reduce compositor overhead compared with X.Org Server and some Wayland compositors. Benchmarking and profiling efforts involved toolchains and projects like Perf (Linux), Valgrind, and graphics drivers maintained by Mesa (computer graphics) contributors.

Category:Display servers