Why Popular Manjaro Linux Distribution Is Facing a Crisis?

For much of the past decade, Manjaro Linux occupied a rare and valuable niche: the friendly face of Arch Linux. While Arch itself demanded patience, expertise, and a willingness to configure everything from scratch, Manjaro offered a polished installer, sensible defaults, and graphical tools — all built atop the same rolling-release foundation. At its peak, it held the No. 2 spot on DistroWatch’s Page Hit Ranking. It was, for many users, the gateway drug to the Arch ecosystem.

That reputation is now under existential pressure. On March 9, 2026, a document titled “Manjaro 2.0 Manifesto” was published on the official Manjaro forum, and it reads less like a roadmap than a reckoning. Signed by 19 team members — including developers, community managers, moderators, and the company’s own Chief Technical Officer — the manifesto represents the most serious internal rupture in the project’s history.

The Manifesto: A Decade of Decline, Laid Bare

The document, posted under the forum handle “Aragorn” — a senior team member — opens without diplomatic cushioning. It accuses Manjaro of having spent the past decade stagnating, losing community trust, shedding contributors, and accumulating a reputation for repeating the same embarrassing mistakes without ever addressing them.

Chief among those repeated mistakes: the project’s chronic failure to keep TLS (SSL) certificates current. These certificates are fundamental to secure internet connections, and letting them expire causes browsers and system tools to refuse connections to Manjaro’s servers entirely. What makes this especially damning is that, according to the manifesto, volunteers had already built automated tooling to prevent this from happening — and were ignored.

But the TLS debacle is a symptom, not the disease. The manifesto’s real accusation runs deeper: that Manjaro has, over the years, been transformed from a community project into a single person’s personal fiefdom.

One Man at the Center of Everything

That person is Philip Müller, Manjaro’s co-founder, project lead, and CEO of the incorporated entity Manjaro GmbH & Co. KG. The manifesto is blunt: the project has become “one individual’s personal project, and everything is centralized around this single individual.” Access to the codebase, infrastructure, and key decision-making all flow through Müller, the signatories allege, leaving the actual contributors with little real authority over the project they maintain.

This is not merely an organizational complaint. According to the manifesto, Müller’s overriding goal has been to convert Manjaro into a commercially successful business — and those attempts have, by the team’s assessment, largely failed. More troublingly, the document alleges that Manjaro GmbH has not been reinvesting its revenue back into the project, nor has it pursued external funding that could support development.

What the Team Is Demanding

Rather than simply airing grievances, the manifesto lays out a concrete restructuring plan. The core demand is a clean organizational separation between “Manjaro the project” and “Manjaro the company.” Specifically, the signatories are calling for:

• The company to formally acknowledge the problems and commit to fixing them.
• Creation of a new nonprofit legal entity — an eingetragener Verein (e.V.), the German equivalent of a registered nonprofit association — to represent the project and community, distinct from the for-profit GmbH.
• Transfer of key project assets to the nonprofit: GitHub organizations, the self-hosted GitLab instance, the forum, CDN infrastructure, the manjaro.org domain, and community funds.
• The new organization to use democratic voting and distribute ownership equally among members, with “arbiter” roles assigned to experienced contributors in specific technical domains.
• The company to retain use of the Manjaro trademark until 2029, after which it would be expected to transfer full trademark ownership to the nonprofit for a symbolic €1.

The proposal is structured to be fair to the company as well: Manjaro GmbH would continue using its own infrastructure for as long as needed to migrate its commercial operations elsewhere. The goal is orderly separation, not overnight disruption.

An Escalating Standoff

The manifesto was not designed to go immediately public. Its authors had planned a staged escalation process with three phases of increasing visibility. But after failing to get a satisfactory response in private, they skipped Phase 2 entirely and moved the document to the public Announcements section of the forum, simultaneously archiving it on archive.org to ensure it couldn’t be quietly removed.

The CTO’s Uncomfortable Position

One of the most remarkable aspects of this conflict is the position of Roman Gilg, who holds the title of CTO at Manjaro GmbH while simultaneously being a signatory to a manifesto calling for the company to relinquish control of the project. Gilg reportedly co-owns 50% of the company, making him not just an employee but a stakeholder with real leverage — and yet he has sided publicly with the developers over the founder.

His decision to put a direct, written question to Müller — asking whether the founder had specific objections to the asset transfer list — and then to watch that question go unanswered for days, was widely interpreted as confirmation that Müller was not engaging in good faith. The silence spoke louder than any response could have.

If Negotiations Fail: Fork or Leave

The manifesto is explicit about what happens if the leadership does not engage. Stage 2 of the team’s “Our Resolve” escalation plan involves going on strike and making the conflict as publicly visible as possible. Stage 3, the final option, is either a fork of the entire project or a mass departure of contributors — effectively hollowing out whatever remains of the Manjaro community team.

The fork threat is credible because the people making it are the same people doing the work. Without active developers, package maintainers, moderators, and community managers, the technical continuity of Manjaro becomes highly uncertain — regardless of who legally controls the brand.

The Broader Context: Years of Accumulated Grievances

This crisis did not emerge from nowhere. Manjaro’s reputation within the Linux community has been eroding for years, with the expired TLS certificates being just the most visible recurring embarrassment. Former users point to poor handling of the community during the opt-out telemetry controversy, inadequate support for legacy hardware, and what many describe as a dismissive attitude from management toward user and developer concerns.

The DistroWatch numbers tell a quiet story. In 2020, Manjaro held the coveted No. 2 position on the page hit rankings — an indicator of strong community interest. As of today, it sits at No. 8, a drop that reflects not just shifting tastes but eroding confidence. Distributions like EndeavourOS, Garuda Linux, and CachyOS have grown partly by positioning themselves as healthier, more transparent alternatives within the Arch ecosystem.

Where Things Stand Today

As of March 21, 2026, the situation is unresolved but has moved slightly off its most adversarial footing. Müller’s March 19 statement — expressing openness to “serious discussions” once a nonprofit is established — was described by LWN.net as a possible truce signal. But critics note it is conditional: he is not offering to help create the nonprofit, not committing to transfer assets, and not addressing Gilg’s unanswered question. The manifesto team has yet to stand down.

Development has not completely halted; Manjaro’s rolling-release pipeline continues to function. But the organizational paralysis is real, and the uncertainty is visible to users who follow the project closely.

Analysis: A Governance Crisis Decades in the Making

What is unfolding at Manjaro is a story that repeats throughout the history of open-source software: a project born from community passion gradually captured by commercial logic, until the tension becomes irreconcilable. The specific form it takes — a founder treating a community project as personal property, while contributors who built the project’s value find themselves without meaningful control — is a well-worn pattern.

What makes Manjaro’s case notable is the orderliness of the challenge. The manifesto is not a rage-quit or an anonymous accusation. It is a structured, legally-informed proposal with a clear ask, a fair timeline, and a genuine off-ramp for the company. The signatories are not trying to destroy Manjaro GmbH; they are trying to save the Manjaro project from it.

Whether that distinction can survive the coming months depends on one variable: whether Philip Müller decides that a smaller role in a healthy project is better than full ownership of a dying one. The Linux community is watching closely. The next few months will be decisive.

Sources: Manjaro Forum (forum.manjaro.org) · It’s FOSS News · GamingOnLinux · FOSS Force · LWN.net · DistroWatch