this post was submitted on 18 Mar 2026
617 points (99.0% liked)

Technology

83295 readers
4345 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] zewm@lemmy.world 171 points 1 week ago (1 children)

Honestly the damage is done. Manjaro has been an instant no from me dog for a long time. The name carries a negative connotation. Trust has eroded.

[–] rabber@lemmy.ca 76 points 1 week ago (3 children)
[–] chemical_cutthroat@lemmy.world 111 points 1 week ago (15 children)
[–] ramble81@lemmy.zip 55 points 1 week ago (1 children)

I mean, I think they were looking for a little more detail that that.

[–] dubyakay@lemmy.ca 56 points 1 week ago

Over a hundred thousand years the ocean of distrust has eroded the cliffs of trust in a non-insignificant manner.

load more comments (14 replies)
[–] Addv4@lemmy.world 88 points 1 week ago (4 children)

Plenty of things, but the most obvious being the two separate instances they had issues with renewing their certs.

[–] chronicledmonocle@lemmy.world 68 points 1 week ago (3 children)

It's more than that. Broken updates. Failed hardware ventures. The project has been shambling along for a long time.

[–] nymnympseudonym@piefed.social 51 points 1 week ago (1 children)

and the certs lapsed again after volunteers built tooling to Prevent That

but somebody never set up the cron job to run it

[–] MalReynolds@slrpnk.net 21 points 1 week ago

Well that's confidence inspiring.

[–] vaionko@sopuli.xyz 22 points 1 week ago (2 children)

Don't forget their package manageer DDoSing the AUR multiple times

load more comments (2 replies)
load more comments (1 replies)
[–] victorz@lemmy.world 20 points 1 week ago (6 children)

Could you please explain why not renewing their certs is such a serious betrayal? Like, if they fixed it, isn't that okay? And even if it happened again, and they fixed it again, isn't it human to err? Or why is it such a harsh offense?

Serious question, I don't know the consequences of not renewing these certs. 😊

[–] Addv4@lemmy.world 36 points 1 week ago (1 children)

It's the tls certificate that proves your website is legit. Without which, you can potentially be a malicious actor that can pose as the website, and when you download the iso, you could unknowingly download something malicious. It's pretty hard to forget certificate renewal (most of the time there are plenty of reminders sent and warnings given), so the fact that it happened twice was very impressively bad.

[–] dubyakay@lemmy.ca 20 points 1 week ago (1 children)

It's pretty hard to forget certificate renewal (most of the time there are plenty of reminders sent and warnings given)

Oh boy. Seems to be the opposite in real life. Especially when it comes to managing stored cert of businesses partners. It has gotten somewhat better now of course, but three years ago most of my company's sev1 production issues were due to lapsing or unscheduled cert changes.

[–] arsCynic@piefed.social 12 points 1 week ago

Can confirm it happens often here too indeed.

load more comments (5 replies)
[–] exu@feditown.com 12 points 1 week ago

I think it's actually 3 now. IIRC they did it again last year

load more comments (1 replies)
[–] RipLemmDotEE@lemmy.today 17 points 1 week ago (3 children)

Failing to renew TLS certificates on time multiple times is enough to never touch it again, but there's also been a lot of other problems with Manjaro.

When I used Manjaro, it never made it more than 6 weeks before something would catastrophically break and I'd have to roll back using snapshots.

load more comments (3 replies)
[–] spez@sh.itjust.works 99 points 1 week ago (1 children)

Good for them! A second TLS problem after what happened last time is unacceptable. I hope the 'mutiny' succeeds.

[–] somehacker@lemmy.world 48 points 1 week ago (2 children)

Pretty sure this wasn’t the second

[–] Eldritch@piefed.world 18 points 1 week ago

And even that was only the most visible yet surface level one of their problems.

load more comments (1 replies)
[–] arsCynic@piefed.social 65 points 1 week ago (14 children)

Just fork already. EndeavourOS exists, an awesome distro, so this threat is a triviality.

[–] Samskara@sh.itjust.works 14 points 1 week ago (2 children)

If I were a Manjaro dev, I would just jump ship to EndeavourOS, Cachy, or Garuda.

load more comments (2 replies)
load more comments (13 replies)
[–] mlg@lemmy.world 53 points 1 week ago (2 children)

The fact that CachyOS more or less successfully replaced Manjaro's purpose I guess is evidence of Manjaro's issues.

I forgot but I think Bazzite had similar complaints (due to its use of silverblue) in which case it was just more straightforward to use Fedora or OpenSUSE if you don't want to work with the read only root system.

Downstream distros need to bring additional value to the table to be worth using, otherwise there's really no need if you can make a package group that accomplishes the same thing in one go.

load more comments (2 replies)
[–] org@lemmy.org 41 points 1 week ago (5 children)

Just quit and move to CatchyOS

[–] Joelk111@lemmy.world 29 points 1 week ago

Distros? Gotta catch them all.

load more comments (4 replies)
[–] brucethemoose@lemmy.world 33 points 1 week ago* (last edited 1 week ago) (3 children)

As others suggest, why stay attached to Manjaro at all? Instead of forking, what about expending that energy on a rising distro without such reputational damage?

CachyOS is very close “in spirit” if they want to develop modified/custom packages, but there are plenty Arch downstream distros with less toxic communities.

They could even fork some other project and make the changes they like. It’d be a saner base than Manjaro at this point.

[–] JackbyDev@programming.dev 9 points 1 week ago

EndeavorOS too, which is even closer to "vanilla" Arch than CachyOS.

load more comments (2 replies)
[–] Adderbox76@lemmy.ca 30 points 1 week ago (4 children)

I started using Manjaro long before all this crap started going down, and I've been holding on hoping this all gets sorted because I hate distto hopping.

But sadly I don't think its going to happen. I've got a new PSU coming to fix a burnt out one that has left my desktop turned off and unupdated for two months. Might be time for an install of something new rather than updating afterwards.

[–] taiyang@lemmy.world 21 points 1 week ago

It's indeed the time. I found Cachy was a good pivot, similar feel but seems to work better overall. Manjaro is still based on Arch after all, technically.

load more comments (3 replies)
[–] 1984@lemmy.today 29 points 1 week ago* (last edited 1 week ago)

Aragorn writes that Philip Müller (the project lead) has been running Manjaro as his own personal venture rather than a community effort, keeping a tight hold on access to both the codebase and the infrastructure.

These weasels never care about the actual thing that is being built, its just a way to make money for them.

Hope they kick that Philip guy out and get back to making this a passion project.

The core members with passion for the actual thing should restart under a new name.

[–] sem@piefed.blahaj.zone 24 points 1 week ago (5 children)

A significant portion of the Manjaro team has signed a manifesto demanding the project split from its parent company and restructure as a non-profit.

Sourav Rudra 18 Mar 2026

Manjaro has long been one of the more popular Arch-based Linux distributions, known for making Arch Linux more accessible to everyday users. But it has been losing ground for years, both in terms of user trust and active contributors, and the complaints about its direction have only gotten louder.

Now, things have hit a breaking point, with calls for a fork if the current leadership does not budge.

A Manjaro team member going by the handle "Aragorn" has published the "Manjaro 2.0 Manifesto" on the official Manjaro forum. The post lays out a detailed restructuring plan for the project that has been signed by 19 team members, including developers, community managers, moderators, and the company's technical lead.

Is there any weight behind this?

Manjaro 2.0 Synopsis This document covers the organizational, technical, management, and other changes we (the Manjaro Team, et al) like to see applied to the Manjaro Project. The goal of this document is to serve as a point of discussion, and ultimately, once a consensus on its contents and written goals has been reached, as a guide for the organizational restructuring of the Manjaro Project.  Motivation The Manjaro Project has been declining over the past decade. It managed to sustain a sizable user base, yet it stagnated, lost trust, lost almost all of its contributors, and even became a laughingstock for repeatedly making the same mistakes and never even attempting to address these known issues.The manifesto opens by stating that the Manjaro Project has been declining over the past decade, losing trust and contributors while repeating the same mistakes without ever addressing them.

One example cited is the repeated failure to keep TLS certificates current, something volunteers had reportedly already built tooling to fix, only to be ignored.

From there, it goes after the core issue directly. Aragorn writes that Philip Müller (the project lead) has been running Manjaro as his own personal venture rather than a community effort, keeping a tight hold on access to both the codebase and the infrastructure.

Aragorn goes on to say that:

The priorities of the Project leadership do not align with those of the developers and community. The current leadership’s goal is to turn Manjaro into a successful business, and thus far, these attempts have mostly failed.

The money situation makes it worse. The manifesto says the company, Manjaro GmbH & Co KG, has not been funneling any of its funds back into the project and has not pursued outside funding either. **What the team wants is a clean separation, where the Manjaro Project is spun off from Manjaro GmbH & Co. KG and restructured as a registered nonprofit association under German law (e.V.).

The new structure would distribute ownership equally among members, use transparent voting for major decisions, and assign "arbiter" roles to experienced contributors for specific domains.

Under the proposal, the nonprofit would get full use of the Manjaro trademark through 2029. The company keeps the right to use it too, as long as the two don't step on each other's toes. After that initial period, the manifesto nudges the company to declare that it is willing to hand over full trademark ownership to the nonprofit for €1.

Key assets like the GitHub organizations, the self-hosted GitLab instance, forum, CDN, and the manjaro.org domain would all move over to the non-profit as well. **The team has also laid out what would happen if they were ignored. The "Our Resolve" section of the manifesto says that there are three stages (from 0-2): waiting for a reply, striking and going public, and finally forking or leaving. Within Stage 1, there are three phases that control how public the document gets.

They skipped Phase 2 and jumped straight to Phase 3 a few days ago, moving the manifesto to the public Announcements section of the forum and archiving the thread on archive.org. If things don't improve, then a forum lockdown is on the table. **Don't think that this is some kind of witch hunt. One of the Manjaro team members, Dennis ten Hoove, has clarified that the goal of this initiative is not to kick people off the project but to change the leadership and help foster Manjaro as a healthy community-driven project.

Expect a bumpy transition

@dennis1248 had sent me a draft proposal for a possible restructuring of Manjaro project in advance via a DM and told me, that it might be formally submitted by the community to me at a later state.  With this post here on the internal hub, it now seems that the community has serious intentions to actually found a non-profit association (German Verein/e.V) and push ahead with a split from the company.  Before the company was founded, there had already been suggestions and discussions to establish an association or other forms of legal entity to make the Manjaro project more sustainable. Ultimately, the current corporate structure was chosen as the only legal entity, known as the Manjaro GmbH & Co. KG company. The company has already provided significant financial support to the project in the past and has also employed various Manjaro developers on a freelance basis since 2019 using company funds.  I have no personal objections on the subject of founding an association to separate the project from the company. However, at this time, I will not be personally involved in any founding processes of this new legal entity. In this regard, association members should not be involved in the company in any way.  Any transfers of company assets or infrastructure require close consultation with the company and yet to be established new legal entity, in order to ensure that the interests of both parties are safeguarded as amicably and smoothly as possible. Any actions that could damage the business must be ruled out. To ensure the smooth operation of the company, assets relevant to the company will remain within the company.  Finally, I would like to note that any actions or comments that could damage the business or reputation of myself or the company should be refrained from in order to ensure a mutually agreeable process and avoid legal actions.Philip did break his silence on the matter, saying that he is fine with an association being formed but wants no part in setting one up himself. He also made clear that handing over any assets would need to happen on the company's terms and closed with a warning that public statements damaging to either himself or the business could have legal consequences.

The protesting team's response was measured, where Aragorn pushed back, pointing out that the manifesto already lets the company continue using the infrastructure for as long as it needs to move its operations elsewhere.

Roman Gilg, who signed the manifesto despite being the company's CTO, put a direct question to Philip, asking whether he had any specific objection to the list of assets outlined in the document. Philip went quiet again.

After days of silence on that question, Aragorn declared that Philip was stalling and announced the team was skipping Phase 2 and moving straight to Phase 3 (where things stand as of now).

What can you do?

There's an active community discussion thread with over 200 replies, started specifically to accommodate talks surrounding the manifesto. If you have thoughts on what's going wrong with the Manjaro project and what could be done better, you can head over and weigh in.

One of the Manjaro old timers, Stefano Capitani, has recently posted there, sharing his view of the situation:

I have to apologize to all of you. It seems I’ve missed some of the events here. I believe, without fear of contradiction, that I, along with @guinux , @oberon , and of course @philm, am one of the “old timers” still active, if not as much as before, but still active in Manjaro.

I have to be honest, I feel like I’m having flashbacks because we’ve already had these discussions or “storms” in the past. We’ve always come out stronger, and we’ll come out stronger this time too.

PS: You need to be logged in to the Manjaro forum to view user profiles.

[–] sem@piefed.blahaj.zone 18 points 1 week ago

The new structure would distribute ownership equally among members, use transparent voting for major decisions, and assign "arbiter" roles to experienced contributors for specific domains

load more comments (4 replies)
[–] MehBlah@lemmy.world 21 points 1 week ago (4 children)

They need to cast out the person who can't renew the ssl certificate.

load more comments (4 replies)
[–] texture@lemmy.world 20 points 1 week ago (1 children)

gaurda is what manjaro should have been. its perfect for noobs with snapper in grub ootb.

i also like envdeavor anc cachy too

load more comments (1 replies)
[–] BigTrout75@lemmy.world 18 points 1 week ago (1 children)

Huh, that's too bad. I used it for years to get comfortable with an rolling release arch distro. I thought it was good, but it would break from time to time. Thankfully, Arch is easy to install and maintain these days.

[–] filister@lemmy.world 13 points 1 week ago

Manjaro was quite messy last time I tried it a couple of years ago.

[–] cyberpunk007@lemmy.ca 14 points 1 week ago (6 children)

Switching distros was not on my agenda. 🙃

[–] Adderbox76@lemmy.ca 26 points 1 week ago (9 children)

Me neither. The more I dwell on it, the grumpier I'm getting. Distro hopping is a young man's sport. I've got work to do.

Thankfully, I learned the hard way a long time ago that my files are almost entirely on a secondary drive and my home folders are all simply symlinks to folders there, so I won't lose any data since that drive won't be wiped. But it's just such a pain in the butt to set up everything the way I like it.

load more comments (9 replies)
load more comments (5 replies)
[–] Shanmugha@lemmy.world 12 points 1 week ago (3 children)

Did I just find next distro to try? :) Kudos to them anyway (yay, that's the kind of news I want to hear)

load more comments (3 replies)
[–] BlackLaZoR@lemmy.world 11 points 1 week ago

Looks like a decent plan. I'll have no problem with supporting non-profit

load more comments
view more: next ›