If you run a lightweight Linux distribution and have reservations about the industry-wide shift toward Wayland as a default display server, PeppermintOS has some significant news regarding its roadmap. The lightweight Linux project has announced that it is switching its display server from the soon-to-be-retired Xorg to XLibre for its next round of ISO refreshes.
On the surface, this may look like a sensible call that keeps the traditional X11 window system alive while bypassing Wayland, at least for the foreseeable future. However, the decision brings PeppermintOS into a complex and deeply divisive corner of the contemporary Linux ecosystem. Choosing XLibre is a move that is unlikely to sit well with every user and developer within the open-source community, given the turbulent history and political baggage surrounding the project.
Moving away from Wayland and Xorg
In a recent blog post detailing its development updates, PeppermintOS announced that it is shifting its display server architecture from the traditional xorg-server to XLibre across all of its upcoming builds. The motivation behind this transition is straightforward: active development on the original Xorg codebase has largely stalled, and the vast majority of mainstream Linux distributions have already migrated or are in the process of migrating to Wayland.
XLibre was created to fill a specific niche by keeping the X11 ecosystem alive, aiming to maintain, modernize, and clean up the legacy codebase for users, developers, and administrators who still prefer traditional X environments. Built as a direct, drop-in replacement for Xorg, XLibre is designed not to break standard desktop environments, window managers, or older hardware drivers. According to PeppermintOS development updates, internal testing of the replacement has proceeded smoothly, functioning as expected without major hiccups.
PeppermintOS has explicitly stated that it has no immediate plans to transition to Wayland. The distribution points to the official roadmap of XFCE, the default desktop environment offering for PeppermintOS, which continues to support both Xorg and Wayland natively. By adopting XLibre, the distribution aims to preserve the familiar XFCE desktop experience while insulating its users from the immediate pressures of the Wayland transition.

Under the hood, this upcoming release cycle also marks a notable technical shift for the distribution. It represents the project’s first Debian-based ISO built without relying on Debian’s traditional live-build tooling. Instead, the team has transitioned to utilizing mmdebstrap, a modern bootstrapping tool that mirrors the methodology PeppermintOS previously adopted for its Devuan-based editions.
That Devuan build has similarly been updated to incorporate XLibre and is currently nearing the stage of public community testing. Meanwhile, a 64-bit Debian flagship nightly build featuring the new display server setup is already up for testing, though developers acknowledge that users should expect a few initial rough edges in the build and deployment processes. For existing PeppermintOS users, the practical takeaway is that the desktop interface and overall user experience will remain identical to the current stable release, with the fundamental changes residing strictly under the hood.
Choosing XLibre will get some eyerolls
Despite the technical viability of the software during initial testing, adopting XLibre is bound to draw skepticism and criticism from various segments of the Linux community. Critics and industry observers have frequently argued that XLibre functions more as a political fork than a purely technical one, and the project has found itself making headlines for a series of contentious developments.
XLibre emerged as a fork of the X.Org server in mid-2025. It was initiated by Enrico Weigelt, who notably served as the top commit contributor to the original Xorg project throughout 2024. However, the launch of the fork coincided with Weigelt being permanently banned from freedesktop.org’s GitLab infrastructure, setting a confrontational tone for the project’s public existence.
The controversy surrounding the fork has spilled over into major Linux distributions and community resources. Earlier this year, Arch Linux removed the XLibre documentation page from its official wiki, citing violations of its Code of Conduct rules against maligning or disparaging other Free and Open Source Software (FOSS) projects, though the software package itself remained accessible via the Arch User Repository (AUR).

Other distributions have experienced even more volatile engagements with the software. Artix Linux briefly adopted XLibre as its default X server in April 2026 before abruptly reversing course. Following an unusually high volume of bug reports and technical friction directly tied to XLibre, Artix announced in its August 2026 release that it would switch back to standard Xorg as the default.
Artix’s experience went further than a simple software rollback. The project publicly disclosed that the decision to drop XLibre drew intense backlash from the fork’s maintainers. The hostility reached a point where a veteran Artix developer, known within the community by the pseudonym "Artist," was targeted and harassed to the extent that they ultimately resigned from the project. In the wake of this friction, Artix initiated steps to completely stop packaging XLibre and migrate existing users back to corresponding Xorg packages.
What next?
The intense controversy surrounding XLibre’s governance, community relations, and political backdrop does not inherently mean that the software is technically broken or incapable of rendering windows. The core of the debate centers squarely on project conduct, community standards, and interpersonal politics within open-source development rather than its ability to function as a display server.
For its part, PeppermintOS has tested the software and found that it works well within their specific distribution framework. As the landscape shifts and major players commit fully to Wayland, projects like PeppermintOS continue to carve out alternative paths for users who rely on legacy display stacks. Whether these choices can remain stable and isolated from upstream community conflicts remains to be seen, but for now, the distribution is pressing forward, ensuring that users who prefer traditional X environments retain a viable option.
Leave a Reply