Arch is different…
You must log in or register to comment.
- 1 day
the fact that they wrote “be right back” 5 hours ago and then never came back is telling
- 6 hours
almost 30h now, the arch update has to have bricked their hardware or something O.o
Every hero has a journey.
Yours has just begun.
I warn you, this is not the easy path.
But I urge you to heed the call.
For though there will be trials and tribulations,
soon, my friend, you will own new socks.
“No way to prevent this” says only distro where this regularly happens
1 dayTo be honest, I’m a firm believer that if it’s considered required to read the news file for updating then the update tool should be printing that information for you. I used to have a hook that did it, but it was flaky. Also, I saw the creator mention that due to the design of the hooks, it happens too late in the process for some manual intervention to be done properly. But because everyone in Arch has such an obsession with “no bloat” I doubt we’ll ever see pacman have that feature.
- 3 days
News from this year:
- virtualbox-ext-vnc >= 7.2.12-2 requires manual intervention (package won’t install)
- Active AUR malicious packages incident (the AUR is locked)
- Arch Linux 2026 Leader Election Results
- Breaking changes for all users of
varnish, which is renamed tovinyl-cache(it’s a proxy, only affects servers) - kea >= 1:3.0.3-6 update requires manual intervention (dhcp server, affects routers)
- iptables now defaults to the nft backend (affects pretty much nothing)
Repost.
Also, my Mint install broke, uh, shit I don’t remember, 5 times? Arch broke zero times. Zero times not my own fault for forgetting I was installing something and shutting off the computer, of course. Except for the times I tried the fucking installer python script, but since I never even booted the install it doesn’t count.
- hirihit640@sh.itjust.worksEnglish2 days
Mint broke for you? That’s the first I’ve heard of it.
Also if you have a habit of shutting down the PC during updates, check out atomic/immutable distros. They are almost impossible to break. You can pull the power during an update and it’ll be fine.
Mint breaks weirdly often but also it’s inconsistent in my experience. It’s a great example of it explodes for some people and others it’s a god like entity of perfection. Never in-between. Lol
Iptables change actually fucked me because I’d tweaked something stupid 12 years ago and forgot. Took lime 45-60 mins to fix
To be fair, adoption as a concept is the problem not the actual aur.
The fundamentals of the aur was fine though that entire ordeal. It’s just one optional choice layered on top that wasn’t
Blaming the aur fundamentally for that choice is like blaming the city planner for when a idiot turns down the wrong way on a one way street.
We kinda just accepted the risk because the upsides were worth it. But some people are assholes and gotta ruin it for everyone.
- lemmyvore@feddit.nlEnglish1 day
This isn’t the first type of problem that the AUR has had. A few years ago it had problems staying up, because it had no scalability to speak of.
“Best hopes and wishes” is not an accepted engineering design strategy. If something can be abused, it will be. Not planning for it is just that, poor planning.
The AUR has been poorly put together and this wave of malware is just another symptom of a deeper problem.
this year
And one post earlier (2025-12-20) that the image likely could be about:
NVIDIA 590 driver drops Pascal and lower support
Install nvidia-580xx-dkms from the AUR
Impact: Updating the NVIDIA packages [without manually changing to AUR packages] on systems with Pascal, Maxwell, or older cards will fail to load the driver, which may result in a broken graphical environment.
- 1 day
If Nvidia deprecates your driver you’ll be up shits creek on just about every distro unless you already used nouveau.
- 2 days
Yes, that was a while ago, so it’s a repost. Also, NoVideo deprecations affect all distributions.
- 2 days
I dont get the bad press arch got. I use arch (btw) and can’t remember last time it wont boot after an update. It maybe happened to me twice in 20 years and at least once was my fault and the other was because i didn’t read the pacman post warning me
Once it happened to me because 6 years prior I’d made a change thinking ‘hah. That makes more sense’ and then things changed under me and I had to read journalctl in a tty. Low key enjoyed dealing with it. But here’s the thing: most ppl are dead at that point. No idea what to do. Arch is for nerds.
Edit: this is a completely different thing. I had two issues.
- 2 days
Ubuntu pissed me off back when Shuttleworth said, “This is not a democracy!”
- 2 days
Hasn’t yet. Ubuntu, on the other hand, managed to piss me off completely
Edit: sorry, wrong thread
- 2 days
I have been using arch linux. And I havent gotten cancer yet. How do i have to be using arch linux to get it?
- 2 days
I smoke since 20 years and I haven’t gotten cancer yet too. How do I smoke to get cancer? /s
Cigarettes work for me perfectly well, other users must be doing something wrong.
Reminds me of my try of Nobara. I do clean install, it installs and starts updating itself for a long while. Afterwards it tells me to reboot, and that the update has failed. I am??? Since I am a noob, so I reboot. And the whole system fully breaks, and no trouble-shooting helps, so I have to re-install. No biggie, just mildly annoying, it was a clean install after all. Then I do some searching to figure out, what went wrong, and find out, that updates failing and the system fully breaking, and having to re-install it if you reboot, is apparently normal behavior for Nobara.
- 2 days
I’ve had Nobara on my PC for several years and not had a problem, though I know others have
Having said that, if I could be bothered I would probably just return to regular Fedora again so that I could have a decent package manager and updater…
Yeah i had this happen with devices that originally came with Windows sometimes, mainly laptops. It must be a combo of BIOS, firmware and hardware that increases the chances of update instability. Its just not feasible for every distro to have the same kind of hardware config testing support that Microsoft has for Windows.
Windows spying on you is not just for marketing, they grab your current environment and sanitize the result so they can get a nice list of hardware and application configurations for when they need to test.
That’s why I completely eliminated Windows from my life and switched to Linux.
- 21 hours
I don’t (and will never) use Arch, but I’ve heard nothing but how user-unfriendly it is. I don’t look for posts about Arch; they just seem to find me – like this one. I don’t hear anything about other distros. Why do people use Arch? Does it offer some outlandish advantage that other distros don’t? Is it for bragging rights? Seriously? I haven’t heard a single good thing about it.
- 19 hours
Arch is mainly for people who prefer instant updates on every software. Like developers, some hardcore gamers want to tweak their system too deep and have too much time to fix if it breaks.
Snapshots are a big relief, as they allow you to directly boot into the previous working version. But if the bootloader itself failed, you might need a live USB to fix it.
Arch is not bad or unfriendly at all. It allows users to deeply customize their system how they want it, and that’s what causes an unstable system at the end. Also, the use of too many AUR softwares at the system level is another reason. It is not official. So by using AUR heavily, we can’t guarantee it will work with other system software.
If you use Arch with snapshots and only install a minimal amount of AUR system-level software, then it’s completely fine for daily use.
Other serious struggles.
-
Very new releases bring a lot of bugs. Recently I saw my screen was flashing when I opened settings. Also, crashes can occur constantly. You have to report it to get an immediate fix from developers.
-
Snapshots can take a fair amount of your storage. But you can control it in Snap.
-
AUR packages are not tested for their authenticity or security at all.
-
A breakage or failure to boot can terrify newbies. Unlike Fedora or Debian, there are no built-in recovery tools out of the box. Everything is the user’s responsibility.
Arch is all about user freedom. All those crashes and failures are not too hard to fix, but you have to spend much time on them. If you have pre-cations like a live USB and snapshots, then there is nothing to worry about at all.
Unlike Windows, Linux demands users know it more and read long wiki pages, which is good in a sense.
Many people in the Linux community want their system built from scratch. So Arch stands in between, distributions like VoidLinux and Gentoo.
-
- 20 hours
i use arch because i find it much easier to start from a system with just a tty and install software i need than to have a full distro and to find and remove packages that i don’t want/need and replace them with the ones i need - makes maintenance easy and i know what’s running on my system. it’s also in my experience one of the few rare distros that package a non-broken fcitx5 which i rely on (but that’s specific to my setup). and the build system is awesome. the community might be a bit harsh on people who post error messages to forums without any attempts at basic troubleshooting.
i expect that people who make these memes installed arch because they heard that it’s a bleeding edge distro that all the kool kidz use, downloaded a bunch of packages from the AUR which messed up their dependencies after the update and now their system isn’t booting right. if you don’t skip updates for a long time and don’t do weird tricks with system packages, arch might be genuinely one of the easiest distros once you get past the installation which can be tedious if you’re used to automated installers.
I think it’s like driving a manual transmission car in the US. You have more control and are more in tune with your car, but when you’re stuck in bumper to bumper stop and go traffic it sucks ass. Similarly some people make it their identity and that’s where the memes come from.
- katharta@piefed.socialEnglish2 days
Idk, I’ve had installs of Kinoite, Bazzite, and NixOS bork themselves unrecoverably. Arch, if something goofs, more often than not I can work my way back to a working system without wiping.
Nothing’s perfect. NixOS has worked it self for me more then once. Just like every distro ever has.
- 2 days
Except the last arch news post is a month ago about virtualbox. I’ve blindly run pacman -Syu for years without issue
- 2 days
It’s difficult to take people shitting on arch in here seriously. I’ll take 1h per year fixing whatever broke over a whole weekend upgrading Debian.
Oh and god forbid you need to compile yourself a package and maybe a few of its dependencies from scratch because that 6 years old bug didn’t make it through the freeze last release.
Whole weekend upgrading debian? I am confused. That’s not how debian works?
Yes? Same thing… aptitude upgrade, aptitude dist-upgrade, edit /etc/apt/sources.lst to point to the new major version (s/bookworm/trixie), aptitude upgrade, aptitude dist-upgrade Done. Typically takes 1 hourish at most.
- 2 days
Debian can take a week to upgrade? Apparently I’m yolo’ing it and just the upgrade. However I have just done one major update, so u might just be lucky
- 2 days
i have often found myself needing to manually update packages on distros like fedora or debian because i need a newer version that hasn’t landed in dnf/apt yet. arch doesn’t have that problem. ymmv, obviously, it’s not going to be an issue for everyone.
- 1 day
I probably don’t mess around my system too much and don’t install too many things outside Debian repositories to make issues with the upgrades.
- 1 day
As someone who gave up on linux years ago, this sounds like one person driving a broken old alfa romeo shitting on someone else driving a broken old fiat. Whilst I watch on from a modern EV.
Hah, here come the downvotes.
It’s absolutely true. And that my outdated Arch system is likely still more fresh than Debian.
That said yeah I would like something that can update itself whenever without breaking*, certainly if it expects me to update frequently. And manual interventions (ideally used for things that actually have a choice/fix, not just what ends up being a pasted command or two) should be a warn-step/update-blocker (depending on situation).
Though what the image is probably about (2025-12-20, nVidia 10-series turned legacy, legacy driver put onto AUR) is a bad situation in its own right particularly later when the AUR issues started happening. And it is really an update-or-don’t (or get an AMD card somehow) issue.
Other distros likely do solve the issue of updating, though from what I can see aren’t as good with packaging (dependency handling, lacking optional dependencies) and package availability. Which can be worked around somewhat too, but still needs more trial/input.
Annoyances are also multiplied for me by having non-fiber internet (also shared).
* TBC I also mean the act of updating itself (outdated keys etc), not just the outcome
https://archlinux.org/news/virtualbox-ext-vnc-7212-2-requires-manual-intervention/ dont worry you only need to shit your pants if you are using virtual box and dont read (sorry OP)
- 3 days
Who uses virtualbox on Linux having KVM, QEMU and virsh/virt-manager?
It’s gonna be slower, proprietary, and it’s not even as easy to install
- lemmyvore@feddit.nlEnglish2 days
It’s not slower.
proprietary
Only the extension pack, the app itself is GPL.
not even as easy to install
How do you mean? You simply install virtualbox (and virtual-guest-iso if you want). All the relevant packages are available from official repos, at least on Manjaro, including a linux-virtualbox-host-modules-meta package that maintains the required linux*-virtualbox-host-modules as needed automatically.
Also, I prefer virtualbox because it makes a lot of stuff easy to do.
File sharing with the host for example, it’s a matter of simply pointing at a dir in settings, as opposed to having to set up Samba on the host (which I don’t have and don’t want) and deal with wierd networking issues, or deal with virtiofs.
Don’t even get me started on selecting locations for the vm files. Whatever you think it should work like, virt-manager’s way ain’t it.
- 3 days
So, I use it on my workstation because I have to also use windows and virtualbox’s cross system integration is far more mature. I really only use it as necessary and it isn’t running all the time.
I would prefer to use qemu, but I’m not doing anything serious with it. I’m just sometimes running a windows instance that I need to be able to easily share files with, and copy/paste across. Once virt-viewer gets there, I’ll switch.
Though, to be honest, it actually uses kvm as its backend so it really isn’t any less performant than qemu for this.
- 2 days
Mint based on Ubuntu or Debian? Debian mint is probably the most boring … and stable and great for anyone who just wants a computer to work.
- grandel@lemmy.mlEnglish2 days
Isn’t it based on Ubuntu which is based on Debian? It’s my first time using Linux and I switched a couple of weeks ago so I’m not sure to be honest but the website[1] states:
Based on Debian and Ubuntu, […]
Which leaves me just as confused.
- Elting@piefed.socialEnglish1 day
LMDE is the version of linux mint based on Debian rather than Ubuntu. It is missing a few features over the main version but it wont randomly shit the bed because of a bad ubuntu package.
- 2 days
Originally it was based on Ubuntu, which is itself based on Debian. But recently they based directly on Debian. There are some differences. Debian based is more stable with older packages and kernel.
Just wanted to add a clarification that both editions are offered currently.
- 2 days
What? No, there are two versions: the main one, based on Ubuntu, and an alternative one based directly on Debian (Linux Mint Debian Edition)
- Smoogs@lemmy.worldEnglish3 days
Indeed. or fed. the only drama i want in my life is the stuff going on IN the game. not some OS cockblocking me.
- OwOarchist@pawb.socialEnglish3 days
Yeah, lol. Arch people keep telling me that this never happens, and yet here it is.
Nah. Debian is fine for me.
- 3 days
I’m definitely lucky that I’m pushing 3 years on my desktop arch install and have never had any updates break it. Had some issues with Nvidia and Wayland over 2 years, but that wasn’t really an arch thing, more an Nvidia thing.
My laptop is the same, but I use it far less, so really a fair of a comparison, although I do update every time I use it, which is every couple of days.
You just need to keep an eye on the news and it won’t happen 99% of the time. Ive got it set up so news updates go to my email in a specific folder. That means i get the notification on my phone as well. Or just get into the habit of checking the page before updating
- 3 days
I don’t need more shit to remember to do. I need a computer that works without me micromanaging it
Thats fine, then arch just isnt for you. Use what you want, but if someone installs arch then complains that it broke because they didnt check the news (something that the maintainers recommend you do) then the blame/fault shifts to the user, not the system.
- 3 days
but if someone installs arch then complains that it broke because they didnt check the news (something that the maintainers recommend you do) then the blame/fault shifts to the user, not the system.
The question is though why pacman does not display these news during the update. Gentoo has been doing this for decades.
Thats a separate issue, but i do agree with you that it would be extremely helpful if it did
- OwOarchist@pawb.socialEnglish3 days
then the blame/fault shifts to the user, not the system
Nah, lol. Not when lots of other systems manage to not break userspace on random updates.
You can claim that blame shifts to the user, but I’m still blaming the shitty system.
In a good system, you can trust that updates are well-vetted already before they’re pushed to average users, and you don’t need to check the news or anything else before updating. You can even set updates to be automatic with a high degree of confidence that it won’t mess anything up for you. (Imagine that, the computer automatically updating itself, saving you the trouble of doing it manually… What a thought!)
Literally every distro ever even Debian. Has broken user space on updates. It just happens. It’s a fact of life. If your distro hasnt done it to you at least once you are either very new to Linux or you are lying though your teeth.
Youre right for most systems that are advertised as stable. Arch however is rolling release, so this doesnt apply. You get package updates as soon as theyre available pretty much. So no, the fault lies with the user when it comes to arch 99% of the time
Edit: i also said the blame shifts to the user if they don’t do something the maintainers specifically say you should do before every update. If you check the arch news, update, and it breaks then yes, the fault is with the maintainer. However this rarely happens nowadays. Ive been on arch for almost 6 years and have not had to do a reinstall ever.
- Jerkface (any/all)@lemmy.caEnglish2 days
“Good” means different things in different contexts. Here you mean it as something like “user friendly”. Of course, there are other priorities that someone else could call “good”. It’s not a helpful word for honest debate, but it’s very convenient for hiding a bunch of semantic puns and confused reasoning behind.
- 3 days
That is why I am using Tumbleweed, rolling release without the expectation of reading news before hitting zypper dup and stuff still being fine. The price for that is a few days of delay for testing, so that major stuff does not break.
- lemmyvore@feddit.nlEnglish3 days
Manjaro has also shown how an Arch distro can achieve this as well, by releasing tested sets of updates slower.
But OP is correct in that’s not the point of vanilla Arch and people who use vanilla should assume the risks.
What’s annoying is people who use vanilla and tell everybody “oh don’t worry nothing ever breaks”. Something always breaks. You have a couple thousand packages installed on the average desktop system, dozens are updated to bleeding edge every day, something will break.
Manjaro maintains a crowd-sourced list of the most egregious defects (+ their fixes) that crop up in popular packages, suffice to say it’s never empty.
Many of them are not system-breaking and may not impact everyone, which is where I’m guessing the “nothing ever breaks” dissonance is coming from.
- 2 days
Fair enough. I am all for choosing a distro that aligns with the own reqirements. It is strange to use a misaligned distro and then complain about it.
- Smoogs@lemmy.worldEnglish3 days
That seems like a pain in the ass. like the sort of shit why i left windows behind. noted: will not touch arch. thanks for the heads up.
It comes from a very different place than Windows, and the data here is very transparent, unlike your average Microsoft KB.
- Smoogs@lemmy.worldEnglish3 days
dont care. It’s still going into my “places i will never go.” box. dont need an OS cockblocking me from my games. that shit can fuck right off.
Besides, some of is use our OS for work. cant afford telling a job “wahh im too stupid to use a reliable OS” just doesnt fly.
- 3 days
Ya then you need an application and you need to jump hoops or have certain versions of packages not available in your package manager, and on arch, here we go.
- 2 days
Gnome or KDE ? I like gnome over KDE in general but the top bar in gnome seems to create a blank bar in games at top of screen.
Haven’t figured out how to fix it.
You fix that by not using gnome. Or butchering gnome with enough extensions to functionally be a reverse lobotomy.
Since gnomes entirely shitck is that you don’t get to decide how gnome works. It’s out of the box or fuck off.
It’s why it needs a billion extension and mods to be remotely functional
Back when I started Linux, poking at the system was fun and exciting (also you had to poke at the system anyway if you wanted to run anything). Now, I just want it out of the way and convenient.
I understand that newcomers might feel that they want to touch everything because it’s all new and shiny, but I think the OS ought to be a creature of the shadows.
- 2 days
The upvotes mean some other people too don’t like Fedora like me. Nothing more than that.
A distro can be perfect for some and, at the same time, hated by some others. That’s normal.
Why it’s not for me. Reasons:
Maintained by a corporation. Probably it’s their testing ground.
Too much bloatware is preinstalled.
Too many updates, just like Arch. But arch feels more cleaner and faster anyway.
Require rpm fusion.
Crashes often.
There is always a connectivity issue on RPM Fusion servers.
Heavily depended upon flatpak.
Many applications don’t have native Fedora packages or repos.
- 3 days
That’s why I use archdebian gives me all the latest software 5 years later.
- corsicanguppy@lemmy.caEnglish3 days
Really? It happens this often?
In 26 years, I’ve seen this happen in two occasions with enterprise Linux. One of them was my own damned fault for using a marginal config. The other was an update that added a new dependency in the code but not the package.
That’s it. Twice.
Never had an unbootable system after an update, all not checking news has ever done to me is having a package fail to install (and then I check the news to see how to fix it), I’ve seen plenty of kernel regressions or other software, but that’s a thing with upstream and getting not-as-tested software, not with arch itself
It’s happened twice to me in seven years of using arch (not black screen, just something being broken after an update) and both times would’ve been avoided if I’d just read the fucking blog like you’re meant to, but yolo lmao. Still on the same install, everything still fine after just switching one package for another or whatever.
with enterprise Linux
I think you already know the difference, but we’re talking about relatively bleeding edge systems here.
I think no rolling releases has gotten their act right. All eventually break with an update, and if you skipped several, the likelihood of reinstalling is high.
At least they teach you good backup practices.
- 3 days
My record with Arch is longer than 6 months without updates, and it completed the updates fine.
My oldest install is 4 years old, and it’s true, it became unbootable once. But it was my fault, for generating an initramfs without free space in /tmp, which caused it to fail. It was a quick fix once I figured it out.
All of this isn’t to say rolling is as stable as Debian, of course. Rolling is inherently gonna be more unstable, and that’s by design.
But if you take some care, you can actually make these rolling distros pretty stable. Hell, my servers run Arch (I’m working on migrating them to Gentoo to get rid of systemd, but I haven’t yet commited to it). And I haven’t had any serious breakages, even on Arch Linux ARM.
- lemmyvore@feddit.nlEnglish2 days
But it was my fault, for generating an initramfs without free space in /tmp, which caused it to fail.
I really don’t think that was your fault. A critical build process that’s not checking for resources and not failing gracefully and leaving the machine unbootable is not the user’s fault.
A build+install can fail for many reasons. It’s actually annoying how many critical system updates on Linux don’t use a staging process and a sudden power-off at the wrong time can leave the machine completely crippled.
Some distros have taken to doing a BTRFS snapshot before they start the upgrade but (a) they’re far and few in between and (b) that still doesn’t fix the upgrade process, it’s just sweeping the problem under the carpet.
- 2 days
I manually triggered it, and didn’t read the logs when it said it failed. That was my fault. If it fails, it will tell you. You still have the machine working until you reboot, so if you read the logs, you can clear /tmp and retry again, and the machine should be bootable again.
Linux lets you do anything, including stupid things. I’d say doing stupid things is the fastest way to learn about it, though.
The same issue would have happened even on Ubuntu, as it uses the same tools as Arch for generating the initramfs. I don’t consider it an Arch or Linux issue, just a user mistake. It won’t happen normally, unless you manually trigger it.
- hirihit640@sh.itjust.worksEnglish2 days
I’m starting to sound like a broken record but since nobody else has mentioned it yet: atomic/immutable distros often use something called rpm-ostree, which stages updates for the next boot. Updates are “atomic”, so you can’t end up with a corrupt partial update, even if you pull the power mid-update (in which case it will just stay on the current version). Everybody gets the same base image, so your OS won’t diverge over time and end up like some frankenstein mess that. It’s all super cool tech.
Wouldn’t say that. OpenSuse Tumbleweed might got some tech debt with their backend and doesn’t come with fancy stuff such as Kernel modifications like Cachy, but their rolling distro is rock solid. And for the few cases where something really breaks the bootable btrfs Snapshots come by default.
It still is for Intermediate users for sure (the installer expects you to know what you want - yet is a GUI). But in terms of stability they really nailed it, I’d absolutely use it for work horses that require newest software. Or Leap if I require binary compatibility to SLED/SLES.
the likelihood of reinstalling is high.
At least with Arch, I don’t imagine needing to reinstall, worst case I should be able to reinstall all packages from a live image.
My system creates automatic snapshots and that’s usually enough. Restoring a snapshots takes me literally 1 minute.
Last one I remember was related to the keychain update, you had to re-acknowledge all of the maintainers in the arch-keyring.
It was a lot of work to visit them all and get them to recite their key signatures while I held their hand to make sure they were really there. The blood tests took a while to come back and affirm their identities, but it was worth it for the piece of mind.
- 3 days
I don’t mean it happened right now. I mean it often happens. Probably when i tweak too much or more installs from AUR.
Manual intervention announcements happen far from “often” though, tinkering with your system is a different thing
