Manjaro 24.0 Since we released Vulcan in December 2023 we worked hard to get the next release of Manjaro out there. We call it Wynsdey. This is also our first release which comes with Plasma 6. The GNOME edition has received several updates to Gnome 46 series. This includes a lot of fixes and polish when Gnome 46 originally was released in March 2024. You can find the changes made to each point-release here: 46.1. Highlights of 46 release series are: GNOME’s filemanager comes with a new glob...
Endeavour is ok I just did like it that much I like that wallpapers
Garuda gave up on it in the installer like the look those jelly window should never be on by default and my ThinkPad Just Said No when I tried to install it I have a t480 I was testing it on there before I put it on my main pc
Manjaro I never got it to work properly just unstable there package installer is worse then discover (discover is not bad I just can’t get it working when I install it)
I’m fine with people using arch bases distros I just don’t use them and I won’t force backs arch on anyone
Can you elaborate what didn’t work on Manjaro? Just curious, I’ve been using it on my gaming rig for over 5 years without problems.
This is not a comment on you as it is a reasonable question but I have wasted too much time arguing with Manjaro fans and I do not want to go down that road again.
To answer the question partially, there were two classes of problem:
1 - governance - this includes the stuff like not renewing certs and not testing core packages. My system became unbootable more than once and one of those times I was not knowledgeable enough to recover and ended up reinstalling ( mostly a skill issue in retrospect ).
2 - package delays - I found more than once that the delay in releasing packages caused problems with the AUR. First, it sometimes meant I could not use AUR stuff because of missing dependencies ( like when that was the only place you could get dotnet - now in extras ). That was frustrating but not destructive. Worse, delays sometimes caused AUR dependencies to get installed instead of ones from extras or community ( because they were not there yet ). This happened with newish software or with packages that had been renamed or refactored. Once the AUR packages had been installed, they would sometimes stay even after the packages appeared in Manjaro repos. Then sometimes the AUR packages would disappear ( be abandoned as they had been moved into the core repos ) and I would end up with packages that would not update because of dependencies or where I would end up using source packages that took forever to build ( because git versions were the only ones available ). I thought all this was just the nature of the AUR until I switched to Arch it stopped happening. I have installed Manjaro since and had it happen again. I do use the AUR heavily.
Sorry, I ended up saying more than I wanted to. I wanted to answer your question but I do not want to argue. Honestly, if Manjaro works for you, I am very happy. If you think I am wrong, that is ok. I wish you luck.
As an outside reader (and Manjaro fan), this absolutely came off as as opinion that doesn’t call for arguments.
You did a great job sharing your experience. Heavy AUR users should definitely NOT use Manjaro - even Manjaro devs warn against it.
Hope mainline Arch serves you well!
Thank you for explaining and sharing your journey.
Regarding 1: A system not booting anymore really is a major issue. Maybe I was lucky to not have encountered that, maybe didn’t happen because I use a custom kernel. Regarding the certs: Honestly I don’t really care about the Manjaro website. The certs of the package repositories are important to me though.
Regarding 2: I’m using the AUR to install some third-party applications like “gpu-screen-recorder”. If you use it for system packages it will cause problems, because the Manjaro repos are delayed on purpose. One would encounter the same problem when using Debian stable and installing system stuff from a PPA.