I realized my VLC was broke some point in the week after updating Arch. I spend time troubleshooting then find a forum post with replies from an Arch moderator saying they knew it would happen and it’s my fault for not wanting to read through pages of changelogs. Another mod post says they won’t announce that on the RSS feed either. I thought I was doing good by following the RSS but I guess that’s not enough.
I’ve been happily using Arch for 5 years but after reading those posts I’ve decided to look for a different distro. Does anyone have recommendations for the closest I can get to Arch but with a different attitude around updating?
I’m running EndeavourOS and waiting for something like this to happen.
So to be clear, you are willing to upend your entire system and potentially your workflow because a single package update was mishandled and because somebody was a little too direct on a forum?
Have you considered Mac OS? Yes, I’m being snarky, but the Linux world isn’t fully user friendly. If you’re unwilling to roll with the punches, it may not actually be for you.
The guy is not saying hello, goodbye, thank you. You think those people are tech support? They’re volonteers. I would be rude too.
Beside, if an dependency issue arise, just fix it. Are you mad because your ego got hurt? There’s a solution in your forum post, idiot.
I got burned by something like this on Manjaro when a rolling update completely borked my graphics card. The devs reacted in a similar way and it made me realise that my priority is stability over bleeding edge and tinkering.
On that day I moved to Fedora. Stable as hell, no fuss. My main OS should just work and not kill itself.
I still love it but jumped over to Bazzite Gnome recently, which is like Fedora with a few bells on top, coupled with having a read-only root-filesystem (stability, man!). It also comes with distrobox, which will let you run arch natively in a container if you need the AUR.
yeah i had that happen to me too, didn’t look in the update screen because updates before went with a breeze but i took another look after VLC wouldn’t play anything, it was something with the VLC plugins and i needed to reinstall those, just had to do
sudo pacamn -S vlc-plugins-allto get VLC to play video files back, but man, that should have been in the news imo.I had the same issue, hadn’t found the solution yet (also didn’t looked too hard) and while I sort of agree that it should have been in the news I also understand why it’s not (it only affects people with VLC, and not everyone uses VLC, if every time a package gets split it was in the news the news would be all about that). That being said I think that there were other solutions that would have been much better, namely split the package with a mandatory dependency on vlc-plugins-all and convert that to optional dependency in a month or two, that way everything keeps working as is for people during the transition, but after a short while it can be modularized.
People are not gonna like this at all but I’ve been using manjaro for years and it’s been pretty solid for me.
I was going to say that Manjaro will have the same issue in a short while because they delay the updates a little bit but follow them, so VLC will get split in Manjaro too, but someone already commented that it has already happened
Yup, it happened to me, installing necessary vlc plugins fixed the issue.
I encountered this same VLC issue on Manjaro this week, so YMMV.
Manjaro has been pretty quiet for a long time. There’s gotta be a point where we forgive and forget. I like Manjaro and used it as my entry point to Arch. It sets a lot more up for you out of the box and has manjaro-specific package bundles that just work on install.
According to Manjarno, its been just under three years since their last mistake, and that was just forgetting to renew the SSL cert for their archived forums. Probably about time we let it back into the Arch family.
If we all can love steamOS then there’s zero reason to hate on Manjaro. They basically do the same thing.
They are both arch at the end of the day.
Least till Manjaro fucks up again. lol
How about NixOS unstable?
Yeesss come to the dark side
I’ve been an Arch user for more than a decade and I’ll usually be first in line to defend it from dodgy claims about unreliability.
But that forum response is bizarre. Literally the last two RSS items right now are about how splitting packages will require intervention for some users (plasma and Linux firmware). VLC is an officially supported package, and surely this change would impact almost every VLC user?
New opt-depends is a nice pacman feature, but it hardly implies that things have been removed from the base package.
Literally the last two RSS items right now are about how splitting packages will require intervention for some users (plasma and Linux firmware).
Maybe a nitpick, but the linux-firmware situation is different, it’s not about needing to install extra packages (they turned the existing package into a meta package or whatever it’s called), but about that coinciding with some changes that can break the upgrade process and require you to force uninstall a package before proceeding.
But yeah, good point about plasma, the only differences I can even think of are that plasma is probably more popular, and definitely more important to have working.
If you don’t want to get into the rabbit hole that is NixOS (which is a distro i also like), then i would say void linux, if you still want that arch minimalism. Void is a rolling release, but it’s more like a slow roll if that makes sense and focuses on stability. It’s package manager is also rock solid, fast, and can update even when the system hasn’t been updated in ages. If you’ve done a manual install of arch before, you’ll probably breeze through the install process as well, since it is a guided ncurses installer.
I second that, void is a solid and stable rolling distro.
After having a similar feeling as yours I went for NixOS.
My thoughts then : if it breaks I can rollback, and the unstable channel is quite comparable to what arch offers.
Now : I’ve moved to stable channel, because it’s updated enough and allows me to only deal with breaking changes twice a year. Moving to NixOS was time consuming (but fun) because it required to rewrite all my dotfiles and learn something new.
What issues did you have? One of the many awesome things about NixOS is that you can write overrides for any particular package if you need an older version, or even to change some options.
Based on what you describe, I would strongly recommend going with OpenSUSE Tumbleweed. It’s just as bleeding-edge as Arch, but all packages go through automatic testing to ensure they won’t break anything, and if some manual actions are required, it will offer options right before update. Moreover, snapper in enabled by default on btrfs partitions, and it makes snapshots automatically before updates, so even if something breaks somehow, reverting takes a few seconds.
One small footnote is that you’ll need to add separate VLC repo or Packman for VLC to have full functionality - proprietary codecs are one of the rare things official repos don’t feature for legal reasons.
On Arch rant: I’ve always been weirded out by this “Arch is actually stable, you just have to watch every news post for manual interventions before every update, oh, and you better update very often” attitude.
Like, no, this is not called stable or even usable for general audience. Updating your system and praying for it not to break while studying everything you need to know is antithetical to stability and makes for an awful daily driver.
The VLC thing can be solved relatively easily by installing
opiwith zypper, and then runningopi codecs, which will add all the necessary repos and install everything. After that VLC (and h.264 etc) will work like a charm.I upvoted you, I am a fellow openSUSE fan and contributor.
But I need to point out that if you install VLC from a repository outside of Factory, then it’s not auto-tested.
Moreover, Packman is external to the openSUSE project altogether. If you use it, you are supposed to “just trust” that everything will be fine.
You are better off installing VLC through Flatpak.
Fair point! Honestly, that’s exactly what I ultimately went for, I just know there are people around who strongly prefer native packages.
Flatpak contains all codecs etc., and works flawlessly.
In the last three years there’s been a single time I can recall pacman telling me I needed to do a thing.
I copy pasted that warning into google it took me right to the news post. I threw in the commands that the news post said I needed to do.
Nothing broke. So this isn’t like it’s a weekly problem.
Nice to know!
I’m running Arch for a very long time. I agree this is not a distro for general audience. I disagree, however, that it is not stable. When I’m doing work I don’t update my system. I enjoy my stable configuration and when I have time, I do update, I curiously watch which amazing foss software had an update. And I try them. I check my new firefox. I check gimp’s new features. etc… or if I have to do something I easily fix it, like in no time because I know my OS. Then I enjoy my stable system again.
Do you want to know what’s unstable? When I had my new AMD GPU that I built my own kernel for, because the driver wasn’t in mainline. And it randomly crashed the system. That’s unstable.
Or when I installed my 3rd DE in ubuntu and apt couldn’t deal with it, it somehow removed X.org. And I couldn’t fix it. That’s also something I don’t want. Arch updates are much better than this.
Guess we simply apply different meaning to the word “stable”. (you do you, though, and if it’s alright with your workflow, yay!)
To me, stable means reliably working without any special maintenance. Arch requires you to update once in a while (otherwise your next update might get borked), and when you update, you may have to resolve conflicts and do manual interventions.
Right now, I run OpenSUSE Slowroll (beta, not released yet) on one of my machines and EndeavourOS on the other. The former recently had to update 1460 elements, and one intervention was required - package manager asked me if I want to hold one package for a while to avoid potential dependency issues. Later, it was fixed, and otherwise it went without a hitch. This is the worst behavior I’ve seen on this distribution, and so to me it renders “acceptably unstable” for general use (although I wouldn’t give that to my grandma).
you just have to watch every news post for manual interventions before every update, oh, and you better update very often
You have to watch the factory mailing list and make any manual interventions for Tumbleweed, and frankly, you should be watching the news and taking any action required no matter the os.
Well… not really. My current installation of Tumbleweed is three and a half years old, and back in 2022 the only reason I re-installed it was changing the NVMe drive. I’ve never read factory mailing list and don’t ever recall having made manual interventions. I’ve just booted it, updated (zypper ref; zypper dup), rebooted and continued working.
You can do this on Arch too and it will work great until it doesn’t. Manual interventions are rare and usually don’t affect everyone.
A decent daily driver distro for regular user should not break on blind update - at most, it should warn the user automatically before applying updates. If user is expected to check news every time they want to update their system - it is not a good fit for anyone but enthusiasts.
Where did you get the idea that Arch is a daily driver for regular user? The very distro that tells in big letters: stuff can break, you better watch out on updates? The very distro that has command-line install process with chroot-like commands as official one?
There are distros based on Arch that are proclaimed to be user friendly and ready for general desktop/gaming use. Plus plenty of people online tell others to use Arch as a daily driver.
Regardless I don’t think an update should happen if it’s going to break something, unless you manually over ride the warnings it should be showing.
Well, Arch wiki explicitly tells you are expected to read the page before doing an update. Those distros which claim to be user-friendly as in “we treat you with kids gloves” definitely should take care of this, no questions here
Plenty of people seriously propose it as such.
It is not - at least if you’re not an enthusiast happy to tinker with your system all the time.
Yup, it really is not. Those plenty of people are doing a big disservice to others with such proposing. I am sad to hear it
Anyone who is not curious enough to type
yay -Pwbefore typingyayshould probably stick with something like Windows. And even then, you should watch out for the rare manual intervention.Edit: Tone.
I have been using Arch, EndouvourOS, and Chimera Linux now for years.
I never do this.
As I have been a Linux user since the early 90’s, I don’t think Windows is really the right fall-back for me.
I don’t think it makes sense to gatekeep Linux only to those who has time, energy, and dedication to continuously check for necessary interventions and to familiarize themselves with all the terminal utilities in the first place.
That is a sort of elitism we need to carefully avoid - one, because otherwise it would halven the desktop Linux community, and two, because there’s a huge group of people out there who need what Linux offers, but cannot dedicate themselves to it in the way enthusiasts do.
For them, there must be an option to push the button and get a smooth update, with everything resolved automatically or prompted in a user-friendly way. Arch is not that.
You feel comfy doing this - alright, no one stops you, Arch is great and has a purpose. But we should never put blame on users for not using their system The Arch Way™, because it’s too technical, too engaged, and is just a poor fit for most. People will not and should not accommodate for this just to use their system. There’s no need to.
If someone chose Arch and complains that it breaks things, it could be useful to point out Arch doesn’t have required guardrails to make it operable in a way they expect, and direct the user to other distributions that have them and potentially least painful ways to migrate.
Having tried Arch and its derivatives, and recognizing their strong points, I can absolutely tell the person needs another distribution, and that’s alright! Whatever fits anybody is up to them. And for stable rolling release experience without the need for manual checking (but also without some of the power features of Arch mainly geared toward enthusiasts) there’s OpenSUSE Tumbleweed.
Edit: Tone.
I don’t use Arch, I use Endeavour because they took Arch and made it better. As to why I used yay as my example, there are two reasons:
- It’s what I use
- It’s nice to show how easy and simple it is when it’s done properly and it normally takes 5 seconds, more when you have to do something. No wading through busy mailing lists hoping to spot an issue. I’m looking at you Debian and Tumbleweed!
I see!
I do, in fact, use Endeavour on my desktop as well, simply because I like snappiness and choice of Arch and similarly don’t wanna bother with the pure one (and also EndeavourOS forums are more friendly in my experience). I run OpenSUSE Slowroll (an experimental Tumbleweed build, same idea as Manjaro, but actually done right) on my other laptop, so can speak from the experience on both ends.
With Slowroll (and my gf’s Tumbleweed) I’ve only once faced the need for manual intervention, and it was simply to resolve a dependency change by choosing which package to leave - literally enter one number, and then it went on peacefully and correctly installing 1460 updates (yeah, they pushed a big Tumbleweed dump, 3.5 gigs total). On Arch and EndeavourOS, the last intervention was just recently, that’s the one OP talks about, and they do happen more often and are more complicated than I’d like.
I used Tumbleweed for eight or so years before switching to Endeavour and it only really bit me hard once. Update, reboot, and sudo no longer worked! If I had spent a bit more time going through the mailing list, I could have made a simple configuration change before rebooting and saved a lot of stress! It affected nearly everybody who installed that particular image.
FFS dude. It’s not lazy want updates to be as simple and pain free as possible. The entire point of these universal machines is to automate shit so we don’t have to think about it so much. We have different distros to run them because people prefer different ways of doing things. The one you pick doesn’t make you better or worse in any way. OP found out Arch is more work than they want to put up with for their daily driver and the benefits aren’t worth the cost. That’s a pretty big fucking club to be calling everyone in it lazy.
This kind of elitism is the most unnecessary, useless, vacuous, tedious horseshit and hurts Linux by pushing people away for nothing. Stop it.
taking any action required no matter the os
This is not really true for fixed release distros. I can’t remember when was the last time I had to read through the release note before Ubuntu version upgrade, or upgrading any package.
Ubuntu was by far the worst experience I have had in terms of updates destroying things. The number of times my post update reboot brought me back to a GRUB prompt, I’ll never go back.
Wayland or X11?
I used to think that, then I learnt the truth. Now-a-days, I say that you may as well use a rolling release because it’s not really any more work that a fixed release and you have up to date software.
Just to reiterate the same point - in fixed release, a package version is not released until all known issues are resolved.
At no point, it is end user responsibility to bother checking anything before installing a new version.
in fixed release, a package version is not released until all known issues are resolved.
That’s not really true. It’s more important that the issues are known. Sometimes they actually wait longer to fix issues since it would introduce changes
My bad, I meant “known major issues”. If minor issues are not fixed, they document it on release note. But, at no point any fixed release distro ever released breaking changes “knowingly”.
Oh yes, the most mythical of software. Bug free.
Bugs are of two types - known (found during testing by Distro maintainer) and unknown.
Fixed release fixes known bugs before pushing packages.
It is following the standard development life cycle.
Fixed release fixes known bugs before pushing packages.
So do rolling releases. What’s your point?
The same thing happened to me. The package was split into separate packages. Install the package vlc-plugins-all.
sudo pacman -S vlc-plugins-allProblem solved
I’m curious as to why the package manager doesn’t fix this automatically?
They will probably get to there. It’s just not that important for the developers rn. They are working on a pacman rust rewrite and hopefully we can see more contributions to the project. I already considered contributing but C deterred me.
You can see the milestones here: https://gitlab.archlinux.org/archlinux/alpm/alpm/-/milestones
I don’t want to fault people for avoiding Arch’s instability in general but this is a very minor issue.
VLC is not a system critical package. I absolutely understand the mods choice to not put it in the RSS. At most they could put a notice in the pacman logs when it updates.
I like Arch because of the AUR and Pacman. Debian and Ubuntu had me adding a bunch of PPA’s which I found way more annoying. Debian probably would be my second choice though. As for the VLC thing, it took me less than 5 minutes from noticing there was a problem, to finding the solution online. Then I was watching The Whitest Kids U’ Know in VLC.
Thanks for this. My VLC broke similarly, but I use it rarely enough that I hadn’t looked into it yet.
Happy to help!
https://endeavouros.com/ https://garudalinux.org/ both arch based maybe you will like the forum style better and they will probably also give you this information.
+1 for Garuda. It’s nice that they have their own way of updating (garuda-update), which also handles situations like this one. It was very satisfying to not have to do anything when the linux-firmware change happened a couple of weeks back.
Oh, also snapshots by default are a chef’s kiss
I doubt the forum style is really the issue.
EndeacourOS, one of my favourite distros, uses the same packages (the real Arch ones). So everything he says here applies.
I like Garuda community.
I’d recommend opensuse tumbleweed. It’s still a rolling distribution, it still has more bleeding edge software, but its package manager, zypper, does atomic updates, so if something doesn’t install right it rolls it back.
That’s the real thing for me: how painless is it to live with long term? After I’ve installed a couple of weird things, and configured some stuff custom - is this a distro that keeps rolling into the future, or is it one that makes me wish I had the time to re-install from scratch every 6 months?
I’ve run tumbleweed for quite a while with no issues. I’ve never had to reinstall it.
I also noticed vlc has broken (installed last week apparently)
Using the pacman syntax:
pacman -Q -i -d vlc
showed a conflict with the vlc-plugin (which appeared to be uninstalled already) and no vlc-plugin-#### installed.
The dependencies were fully explained in the list, including the vlc-plugins-all dependency. I’m lazy so that’s the dependency I installed on my EndeavourOS.
