• Shanmugha@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 hours ago

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

  • brucethemoose@lemmy.world
    link
    fedilink
    English
    arrow-up
    21
    ·
    edit-2
    5 hours ago

    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.

    • Hemingways_Shotgun@lemmy.ca
      link
      fedilink
      English
      arrow-up
      18
      ·
      5 hours ago

      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.

      • FG_3479@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 hours ago

        Gnome has a Save Desktop app which backs up your desktop config, list of Flatpak apps, and the folders you choose. I use Bazzite but I’m not locked in.

      • ranzispa@mander.xyz
        link
        fedilink
        English
        arrow-up
        4
        ·
        5 hours ago

        I like to have a separate partition for /home Whatever happens I can wipe root safely and install something else.

        • Hemingways_Shotgun@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 hours ago

          I used to bother doing all of that too. I just found symlinking achieved the same results without a bunch of manually configuring of mount points.

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    46
    ·
    11 hours ago

    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.

    • Burninator05@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 hours ago

      I had been using Pop-os for about a year but wasn’t completely happy with it. A friend suggested Bazzite and, to me, it was a lot better in some ways and worse in others. I’ve since switched to Fedora and don’t really have any complaints. I don’t plan on switching again baring something I don’t see coming.

  • 1984@lemmy.today
    link
    fedilink
    English
    arrow-up
    32
    ·
    edit-2
    13 hours 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.

  • BigTrout75@lemmy.world
    link
    fedilink
    English
    arrow-up
    20
    ·
    15 hours ago

    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.

  • Hemingways_Shotgun@lemmy.ca
    link
    fedilink
    English
    arrow-up
    31
    ·
    17 hours ago

    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
      link
      fedilink
      English
      arrow-up
      20
      ·
      17 hours 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.

    • RipLemmDotEE@lemmy.today
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      16 hours ago

      I also started with Manjaro, but it’s broken mess. I moved to Garuda and it has been completely solid and stable for over a year.

  • sem@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    27
    ·
    17 hours ago

    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.

    • ChunkMcHorkle@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      11 hours ago

      Thank you for writing this up, as someone not familiar with what’s going on over there I really appreciate you taking the time.

      • sem@piefed.blahaj.zone
        link
        fedilink
        English
        arrow-up
        4
        ·
        6 hours ago

        Thanks, but I didn’t write anything – I just copy pasted the linked article – maybe it is not what the website would want, but I much prefer reading the article in the comments vs having to click the link to read the article.

        Raises an interesting philosophical and operational point about how content online should be paid for.

    • sem@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      17
      ·
      17 hours 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

  • zewm@lemmy.world
    link
    fedilink
    English
    arrow-up
    150
    ·
    22 hours ago

    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.

      • RipLemmDotEE@lemmy.today
        link
        fedilink
        English
        arrow-up
        9
        ·
        5 hours ago

        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.

        • Buddahriffic@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          4 hours ago

          The manifesto mentions this and that tooling had been made by volunteers but leadership ignored or rejected it (wasn’t clear which). So it seems that they are firing their leadership for the same reasons you want to stay away, which is a good sign, at least. Like promising that they are willing to mutiny to stop the enshitification.

        • rabber@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 hours ago

          Yeah the last time I tried manjaro years ago it kept breaking but I thought that was just the linux experience at the time haha

      • Addv4@lemmy.world
        link
        fedilink
        English
        arrow-up
        78
        ·
        21 hours ago

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

        • Victor@lemmy.world
          link
          fedilink
          English
          arrow-up
          19
          ·
          19 hours ago

          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
            link
            fedilink
            English
            arrow-up
            34
            ·
            18 hours ago

            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
              link
              fedilink
              English
              arrow-up
              16
              ·
              18 hours ago

              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.

          • rhubarbe@tarte.nuage-libre.fr
            link
            fedilink
            Français
            arrow-up
            5
            ·
            15 hours ago

            People are very harsh with Manjaro. There’s more than just a list of objective facts unfortunately. I suppose there were some bruised egos at some point.

            The certs issue wasn’t a big deal, it didn’t change anything for me as a user. It just paints a bad image.

            • daggermoon@piefed.world
              link
              fedilink
              English
              arrow-up
              4
              ·
              11 hours ago

              As a former Manjaro user, it has some issues. It has weird bugs that aren’t present in any other Arch-based distro. Pamac ddosing the AUR is pretty bad as well. I’m thankful I used it as long as I did though. It got me hooked on Arch based distros. Everything else feels antiquated now. Actually, Void Linux is kinda cool

          • underisk@lemmy.ml
            link
            fedilink
            English
            arrow-up
            6
            ·
            18 hours ago

            it’s the main way for software to verify the identity of a source. without it you let nefarious actors do something like hijack a DNS server and impersonate your servers to your users, which is a pretty big problem if you’re running a software distribution network! it is literally a breach of trust and massive security vulnerability. and it probably broke a ton of shit when software that uses the certificate found an expired one and suddenly (and correctly) refused to work.

  • spez@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    92
    ·
    22 hours ago

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

    • redsand@infosec.pub
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 hours ago

      No. Let Manjaro die. It has no reason to exist in any form. Go contribute to something useful.

    • rhubarbe@tarte.nuage-libre.fr
      link
      fedilink
      Français
      arrow-up
      5
      ·
      15 hours ago

      Except that I want the same release cycle as Manjaro. The only equivalent I have found so far seems to be OpenSuse Slowroll, in beta for the past 2 years.

      • atomicStan@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 hour ago

        If I may, would you seriously consider switching to openSUSE Slowroll if Manjaro’s situation doesn’t improve? Or, are there reasons beyond its beta status that hold you back?

        • rhubarbe@tarte.nuage-libre.fr
          link
          fedilink
          Français
          arrow-up
          1
          ·
          1 hour ago

          I used to hop distributions in my youth, between 2000 and 2019. I have settled on Manjaro and never looked back. As of today, my desktop works perfectly and I have not seen any stability issues.

          I am considering testing openSUSE Slowroll in the coming months but not on my main computer. What’s holding me back is that I can’t see any momentum behind Slowroll. I have no clue if the solution will be supported for a long period. I’d like to have more guarantees than what is on openSUSE website.

        • rhubarbe@tarte.nuage-libre.fr
          link
          fedilink
          Français
          arrow-up
          2
          ·
          5 hours ago

          I’ve never regretted it for the past 7 years on my daily drivers. That’s why I don’t get the constant criticism around this distribution.

          • redsand@infosec.pub
            link
            fedilink
            English
            arrow-up
            2
            ·
            5 hours ago

            Philip can’t operate letsencrypt. And he’s kinda just a shitty neckbeard. Try debian.