I’ve been on Manjaro for about 10 years now, and these days (last few years) nvidia-dependency-conflicts-caused-by-eol-kernel is the only real issue you can run into unprompted. Even that kind of requires you to have at least a couple year old installation (for the kernel to go EOL), which means newbie shouldn’t ever be running into it. Not sure what Arch is doing these days, but when I was running it there was certain expectation of vigilance (reading Arch Linux News before updating) and readiness to fix issues caused by updates yourself. On Manjaro such major breaking updates are never sent to users on the stock stable branch, meaning you can practically run “pacman -Syu --noconfirm” willynilly.
I still wouldn’t recommend it as the first distro as it doesn’t hide the underlying complexity as well as something super mainstream like Ubuntu, but Arch/EndeavourOS is obviously much worse in that regard.
It’s been nearly 4 years since I last used Manjaro and I had that error quite often around ever ½-¼ a year in my 2 years of Manjaro. iirc to resolve it I had to uninstall the current nvidia driver > restart without driver > install supported kernel > install driver. Don’t know what I did wrong tho.
Manjaro did otherwise a good job to keep the sys together.
What bugged me a bit was the painfully long retention of the big KDE updates. At that time KDE was making big QOL leaps and quite a few distros had those updates already. But I could also live with that.
In the last month of my time with Manjaro a few Proton games dropped frames heavily and that’s the end of the story. Made the switch to Arch and never had probs with nvidia again, apart from when new Steam UI came out.
I’ve been on Manjaro for about 10 years now, and these days (last few years) nvidia-dependency-conflicts-caused-by-eol-kernel is the only real issue you can run into unprompted. Even that kind of requires you to have at least a couple year old installation (for the kernel to go EOL), which means newbie shouldn’t ever be running into it. Not sure what Arch is doing these days, but when I was running it there was certain expectation of vigilance (reading Arch Linux News before updating) and readiness to fix issues caused by updates yourself. On Manjaro such major breaking updates are never sent to users on the stock stable branch, meaning you can practically run “pacman -Syu --noconfirm” willynilly.
I still wouldn’t recommend it as the first distro as it doesn’t hide the underlying complexity as well as something super mainstream like Ubuntu, but Arch/EndeavourOS is obviously much worse in that regard.
It’s been nearly 4 years since I last used Manjaro and I had that error quite often around ever ½-¼ a year in my 2 years of Manjaro. iirc to resolve it I had to uninstall the current nvidia driver > restart without driver > install supported kernel > install driver. Don’t know what I did wrong tho.
Manjaro did otherwise a good job to keep the sys together.
What bugged me a bit was the painfully long retention of the big KDE updates. At that time KDE was making big QOL leaps and quite a few distros had those updates already. But I could also live with that.
In the last month of my time with Manjaro a few Proton games dropped frames heavily and that’s the end of the story. Made the switch to Arch and never had probs with nvidia again, apart from when new Steam UI came out.