Seriously. I used Manjaro for a short period about 5 or 6 years ago but ran into so many issues with it. Vanilla Arch on the other hand is very forgiving in my experience. I have a second desktop PC with Arch installed and I only update that machine once every couple of months when I actually need to use it. In my four years of doing that I never had an update break my system.
I’ve used and come back to Arch for nearly 8 years now and Manjaro has always been a broken distribution and genuinely gives Arch a bad rep.
Arch has always been a very stable daily driver for me, never breaking and never having issues with it. I’m always confused on what people are doing when they have issues with their entire distro breaking, especially since you pick all your packages and such anyways.
I’ve had a few breaking changes in 10 years of dailying Arch across multiple devices.
Most egregiously one time a PAM update included a new PAM config… which got applied as .pacnew, but the new PAM config was critical and I could not login with a cryptic error message.
That probably took me a solid hour to figure out, because config file conflicts is probably pacman’s weakest point. At least apt starts conflict resolution by default.
manjaro
fixed the problem by deleting mime cache and rebuilding it
“manjaro” explains the problem very well actually
Seriously. I used Manjaro for a short period about 5 or 6 years ago but ran into so many issues with it. Vanilla Arch on the other hand is very forgiving in my experience. I have a second desktop PC with Arch installed and I only update that machine once every couple of months when I actually need to use it. In my four years of doing that I never had an update break my system.
I’ve used and come back to Arch for nearly 8 years now and Manjaro has always been a broken distribution and genuinely gives Arch a bad rep.
Arch has always been a very stable daily driver for me, never breaking and never having issues with it. I’m always confused on what people are doing when they have issues with their entire distro breaking, especially since you pick all your packages and such anyways.
I’ve had a few breaking changes in 10 years of dailying Arch across multiple devices.
Most egregiously one time a PAM update included a new PAM config… which got applied as
.pacnew, but the new PAM config was critical and I could not login with a cryptic error message.That probably took me a solid hour to figure out, because config file conflicts is probably pacman’s weakest point. At least apt starts conflict resolution by default.