So I’ve been iso live testing Manjaro KDE Plasma lately and it looks very polished.

On the other hand, there is a negative vibe towards it.

Why the hate?

  • M. Orange@beehaw.org
    link
    fedilink
    arrow-up
    54
    arrow-down
    2
    ·
    1 year ago

    In short, the maintainers have made questionable decisions over the years, and the Arch Linux packages are held back by two weeks on Manjaro for… basically no reason.

    If you want an out-of-the-box solution to Arch Linux, just use EndeavourOS.

    • Kongar@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      1 year ago

      This. Manjaro isn’t trash, but there are better options. This coming from a guy who used manjaro and loved it for years.

    • Merlin@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      So. I’m a happy Manjaro user. I don’t install a lot of things and have had AUR updates break stuff likely due to the 2 weeks delay Manjaro adds to their packages.

      I’m still using it on multiple devices and I’m really happy. I considered moving to endeavour but I wasn’t sure how it would handle hardware updates. I mean, my understanding is that Manjaro is more “noob” friendly and I don’t consider myself an expert. I used the Manjaro hardware helper to fix my video drive several times and I like the simplicity of the command. Does endeavour require a more advanced user? Does it have the “easy to use” troubleshooting things that Manjaro has?

      Ah. What about the Kernel uploader? I think the Manjaro one is unique to Manjaro right? Is there another one for regular arch/endeavour?

      • M. Orange@beehaw.org
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Endeavour has plenty of “beginner” tools, including a kernel manager (literally called A Kernel Manager) and a friendly GUI Welcome app that helps you update your system and your mirrors.

  • HeyLow 🏳️‍⚧️@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    39
    arrow-down
    1
    ·
    1 year ago

    I used Manjaro for about 3 years

    Its great but packages tend to break over time with it being a “stable” arch build

    Over that 3 year period updates managed to break my install at least 30 times

    Switched to Endeavour over a year ago and haven’t had an update break my install yet

    • Salix@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      Wow. 30 times in 3 years? I wonder if that’s specific packages or hardware you had. I had 5 computers (2 desktops, 3 laptops) running Manjaro for so many years, and still haven’t had a single system break. Including using a lot of AUR packages.

      Though last year, I’ve moved all of my computers to Arch, Debian, and Proxmox. Arch mainly because I wanted to fully configure my systems more.

  • NoisyFlake@lemm.ee
    link
    fedilink
    arrow-up
    20
    arrow-down
    2
    ·
    1 year ago

    There’s not really any benefit of running Manjaro over Arch, it will only introduce problems over time. If you want a “pre-configured” Arch with a nice installer, go for EndeavourOS, it’s great!

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      Manjaro has graphical tools that make it super easy to manage packages, drivers and kernel versions.

        • lemmyvore@feddit.nl
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          You can but there isn’t a lot of choice, Octopi is pretty much the only other pacman GUI besides Pamac that’s sufficiently fleshed out. All the others are either just package searchers or CLI-only.

          And Manjaro also has the Manjaro Settings Manager, which includes the kernel management module and the hardware drivers management module.

    • interceder270@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      1 year ago

      I just wanna point out, people were using this exact same rhetoric when Antergos was a thing.

      Antergos is no longer a thing. Just saying. Manjaro still is though! I believe it’s older than endeavor OS.

      • NoisyFlake@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Even if Endeavour stopped development tomorrow, I could still use and update my system normally because it’s using the regular Arch repos.

  • drwankingstein@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    4
    ·
    1 year ago

    Manjaro for some reason can’t stop breaking crap, and when they do break crap, they aren’t exactly elegant about it

      • drwankingstein@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I wish I was that lucky, the final straw for me was the grub-customizer shenanigans, manjaro pushed an update that broke grub customizer boot entries, then when users were trying to figure it out, they removed grub customizer, and then they even went so far as to make grub conflict with grub-customizer which was really asinine. IIRC they even wound up locking the forum thread on it

  • linuxgator@lemmy.world
    link
    fedilink
    arrow-up
    14
    ·
    1 year ago

    Most of the hate is because of the maintainers not maintaining their security certificates. Another similar distro is EndeavourOS, which I personally prefer. But either way, find what works for you.

    • woelkchen@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      Just out of curiosity I’ve looked for that a couple of months ago and I found that it’s relatively easy to transform a Manjaro installation to Arch and Endeavor. IIRC it was just adding new repo keys and changing the repos. People attempting that would have to look the guide up for details.

  • terminhell@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    1 year ago

    Just give it a go. I used it for years, and had relatively little issues tbh. Most of them I think are hardware related as I’ll have similar issues in other distros and even windows.

    The devs have done some goofs yes. Things like letting certs expire, and as mentioned already, potential issues with aur. But, I remember having aur issues even with vanilla arch in the past.

    Using fedora currently though, and I don’t think I’ll switch anytime soon.

  • plasticcheese@lemmy.one
    link
    fedilink
    arrow-up
    8
    ·
    1 year ago

    I’ll keep it short and sweet.

    I’ve been using Manjaro for about 6 years now.

    When I had an Nvidia GPU, it would break after quite a few updates and need a rollback.

    Then I moved to an AMD card, and I haven’t had any issues at all.

    Like…at all.

    The End.

  • GreyFalcon@iusearchlinux.fyi
    link
    fedilink
    arrow-up
    12
    arrow-down
    4
    ·
    1 year ago

    I have manjaro running on six machines. No problems that were not Just part of learning. Two of those computers were for testing different distros… All ended up with Manjaro.

    Hate is for people that don’t create, or improve their own world.

    • kylian0087@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      1 year ago

      While on one hand Manjaro is very polished. Some things they do is questionable. Like the time they suggested to change your date and time because they let their repo keys expire. Or accidentally DDOS the AUR. Just to name some. The Manjaro team has a rather bad track record of these things.

      • interceder270@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        That stuff is negligible compared to Mint getting hacked and hosting a malicious ISO.

        But for some reason you never hear people mention that about Mint 🤷

  • highduc@lemmy.ml
    link
    fedilink
    arrow-up
    11
    arrow-down
    3
    ·
    edit-2
    1 year ago

    It’s not all “purists” and “tribalism”, Manjaro actually has issues. Besides the well known certificate issues and older packages, I have the following anecdote which made me really dislike it.

    A friend has Manjaro and one day his nvidia drivers stopped working after an update. I helped troubleshoot over the phone, while looking over the wiki. For nvidia drivers they have their own wrapper around pacman.

    Turns out there’s a different nvidia driver for each kernel version. Already a stupid design. So unlike arch where there’s 1 kernel package (the latest the distro offers) and 1 matching nvidia driver, Manjaro has dozens…

    The wiki never mentions how to install or update the drivers manually with pacman or anything like that. It pushes their own tool, a stupid wrapper around pacman, which is supposed to manage this for you.

    In my friend’s case, the tool failed. It was trying to run pacman but there was a conflict issue. But the tool didn’t show the pacman output, so we couldn’t figure out what the tool is trying to do, and why it doesn’t work. We tried removing the tool and re-installing, and all kinds of messing around with it. It failed to install the drivers, it failed to remove the drivers, it kept failing whatever we tried.

    Eventually we figured out the naming convention they used for the packages (again not mentioned in the wiki), and manage to install the correct kernel - driver pair manually, using pacman.

    Tl;dr: poor design, bad documentation, and they push their own crappy tools which hinder instead of helping

    • Atemu@lemmy.ml
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      1 year ago

      there’s a different nvidia driver for each kernel version. Already a stupid design

      That’s not a stupid design at all. A nvidia kernel module artifact is only compatible with exactly one kernel ABI. Thus you need one binary nvidia package for each kernel you ship.

      Arch also has one package for every kernel ABI they ship: nvidia and nvidia-lts.
      Though it should be noted that their design assumes that these two ABIs are the only possible ABIs which isn’t strictly the case as the zen, hardened or RT variants may sometimes lag behind their regular counterpart. That’s a stupid design if anything as it increases the friction of kernel ABI upgrades as a kernel package maintainer.

      We at NixOS also ship the nvidia module for each of our ~50 kernel variants; all major versions of the Nvidia module compatible with that kernel in fact.
      The only possible way to access these nvidia kernel modules is via a certain kernel’s linuxPackages attribute set that contains all packages that rely on a kernel ABI such as kernel modules or packages like perf. That’s good design if you ask me but I’m obviously biased ;)

      • highduc@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        I know you need a new nvidia driver every time the kernel updates, but why keep 50 kernel versions? My beef was them offering so many (outdated) versions instead of keeping the latest one which would make things very simple for users (imo).

        • Atemu@lemmy.ml
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          These aren’t all versions per se but mostly variants, versions and versions of variants. For example, we have packaged the xanmod kernel which is a modified kernel optimised for desktop use but it has two variants: Main and LTS. We have packaged both.

          Here are the names of all of our kernels currently to give you an idea (as a JSON list):

          [
            "linuxPackages",
            "linuxPackages-libre",
            "linuxPackages-rt",
            "linuxPackages-rt_latest",
            "linuxPackages_4_14",
            "linuxPackages_4_19",
            "linuxPackages_4_19_hardened",
            "linuxPackages_4_9",
            "linuxPackages_5_10",
            "linuxPackages_5_10_hardened",
            "linuxPackages_5_15",
            "linuxPackages_5_15_hardened",
            "linuxPackages_5_18",
            "linuxPackages_5_19",
            "linuxPackages_5_4",
            "linuxPackages_5_4_hardened",
            "linuxPackages_6_0",
            "linuxPackages_6_1",
            "linuxPackages_6_1_hardened",
            "linuxPackages_6_2",
            "linuxPackages_6_3",
            "linuxPackages_6_4",
            "linuxPackages_6_5",
            "linuxPackages_6_5_hardened",
            "linuxPackages_6_6",
            "linuxPackages_custom",
            "linuxPackages_custom_tinyconfig_kernel",
            "linuxPackages_hardened",
            "linuxPackages_latest",
            "linuxPackages_latest-libre",
            "linuxPackages_latest_hardened",
            "linuxPackages_latest_xen_dom0",
            "linuxPackages_latest_xen_dom0_hardened",
            "linuxPackages_lqx",
            "linuxPackages_rpi0",
            "linuxPackages_rpi02w",
            "linuxPackages_rpi1",
            "linuxPackages_rpi2",
            "linuxPackages_rpi3",
            "linuxPackages_rpi4",
            "linuxPackages_rt_5_10",
            "linuxPackages_rt_5_15",
            "linuxPackages_rt_5_4",
            "linuxPackages_rt_6_1",
            "linuxPackages_testing",
            "linuxPackages_testing_bcachefs",
            "linuxPackages_xanmod",
            "linuxPackages_xanmod_latest",
            "linuxPackages_xanmod_stable",
            "linuxPackages_xen_dom0",
            "linuxPackages_xen_dom0_hardened",
            "linuxPackages_zen"
          ]
          

          (Note that some of these are aliases; linuxPackages_latest is currently linuxPackages_6_6 for example.)

          Each of these has the following nvidiaPackages (modulo incompatibilities):

          [
            "beta",
            "dc",
            "dc_520",
            "latest",
            "legacy_340",
            "legacy_390",
            "legacy_470",
            "production",
            "stable",
            "vulkan_beta"
          ]
          

          (Again, some of these are aliases.)

          This is useful to have because users might have hardware constraints. It’s not hard to imagine a scenario where a user might have a WiFi chip that only works with kernel ABIs < 5.4 and require the 470 nvidia driver for their old GPU. Packaging just the latest kernel and just the latest Nvidia driver would make this user unable to use their system.

    • ikidd@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Turns out there’s a different nvidia driver for each kernel version

      That is literally every version of Linux out there. IDK what you think was different about Manjaro in that respect. Nvidia hates linux and it’s a tough thing to keep it running, especially on a rolling release. Use the DKMS driver if you’re going to update kernels a lot. At least manjaro seperates the kernel installs from the general updates to minimize this disruption.

      • highduc@lemmy.ml
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        1 year ago

        I know that these packages are “linked”, and for every kernel update you need a new nvidia driver, I don’t understand though why they keep so many kernel versions in the repo (and their respective nvidia drivers ofc). Just makes things confusing, I assume people generally want the latest kernel the distro has to offer, or if they want something else it’s a different kernel “flavor” like lts, zen, rt, etc.

  • CrypticCoffee@lemmy.ml
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    1 year ago

    I’ve had it break many times during update. Don’t get me wrong, I liked it at first, but if you want a system that works after update, you’re probably better checking elsewhere. Linux Mint, and Kubuntu are far better simplicity wise. Open Suse or Arch if you want rolling updates.

  • the16bitgamer@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    I am currently using Manjaro as my main Laptop OS.

    Most of the hate is philosophical based in small often overlookable facts. And how Manjaro uses/is compatible with the AUR. There’s a whole github dedicated to the communities complaints here: https://github.com/arindas/manjarno

    While I can see why many don’t like manjaro, I personally see these complaints as a way to evaluate the company to see if they improve.

    My experience with Manjaro is about 1-2 years now. And the OS is very stable, honestly more stable than my brief time with Fedora.

    But I did break a lot during that time including my DE. However as long as you are careful on where you install from, the distro will be stable.

    Install order

    1. Official Repo - this is delayed by a few weeks to “validate stability”, one of the sticking points for the community

    2. Flatpak

    3. AUR - due to the delayed official packages some AUR packages won’t update immediately, or will cause conflict when they are.

    AUR support is honestly the only valid issue with Manjaro. Due to the delay AUR packages will break as older dependencies aren’t being updated causing a large string of removals which can cause stability issued in Manjaro.

    My recommendation is to avoid the AUR unless the package isn’t found elsewhere. Which is a problem if you installed Arch for AUR. Thus EndeavorOS is preferred.

    But for my usage I prefer the graphical interfaces for all setting. With the exception of GRUB, there is a GUI for everything and you won’t need to touch a terminal.

    With that said, you may want to look into OpenSUSE or Fedora/CentOS, and they are similar in terms of GUI settings. And are a little safer since OS level packages are behind another package manager.

    But at the cost of less software. For me I’m stuck with Manjaro for now, and as soon as Slimbook battery is officially on Fedora trying that out again.

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      edit-2
      1 year ago

      I have something like 70 AUR packages on Manjaro and doing fine. Yes, they break every once in a while. They break on Arch too.

      The thing is, you have to update AUR packages. They’re compiled against a certain system state and they will break eventually as the system updates. This will happen with source packages on any distro. It has nothing to do with Manjaro.