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)
post
That's why I go for boring distros like Fedora
Hello from Mint :)
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.
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.
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.
What the other person wrote isn't quite true: there is a current version of Linux Mint based on Ubuntu (which is itself based on Debian) and another current version based directly on Debian for those who want to avoid Ubuntu.
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.
Indeed. or fed. the only drama i want in my life is the stuff going on IN the game. not some OS cockblocking me.
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.
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.
Hm... btw, I hate fedora.
Lemmy always seems downvote heavy. Why don’t you like fedora?
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.
What specifically happened? Can you share the news item?
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.
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.
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.
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.
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.
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.
Why are you trying to get rid of systemd on your servers?
Cuz it's annoying to work with (it usually breaks stuff because it's purposefully incompatible, and they have to force their way), it's slower than alternatives, it is a mess, and I don't like its philosophy.
SystemD is the Windows of Linux, and it has already brought enough problems. Sadly, all the major distros went all in on it, so a lot of software is developed with increasing dependency on SystemD's non standard systems.
Also I don't trust Poettering at all. This guy is antithetical to free, open and standard software, and he himself has said it.
And on top of all that, they went and folded so quickly to implement stuff like age verification when Linux wasn't even tied by those laws. Their excuse was that they were doing it to set a good precedent and a safe standard for it on Linux, but their implementation was unsafe and flawed. When pointed out, Poettering himself said that why bother with security, because that data is "not important".
TL;DR: I have many concerns with SystemD's management and philosophy, and their software often breaks, causes issues, isn't compliant with standards, has security holes and is slow.
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.
I mean, I've been running exclusively rolling release Linux distros (Gentoo and Arch) as my daily driver for the last 20 years and I don't think I've ever had the thought that reinstalling from scratch would be simpler than just... fixing the issue. I've never backed up my OS files either. Only data files; the sort of files that aren't put there by the install process or package manager. I've never used BTRFS or anything with snapshotting abilities either.
I have booted into a live system, chrooted, and fixed something. (Because my kernel or bootloader or something was borked.) But it's been quite a long time since I've had to do that, and I've never reinstalled from scratch because I couldn't fix something.
(The only times I've used non-rolling releases were pretty limited cases. A server here running Debian here, a Raspberry Pi running Raspian (though even Raspberry Pi's, I've mostly used Arch Linux ARM) there. Also my work machine, though I've even installed rolling release distros on my work machine on a forgiveness-rather-than-permission basis at times. Lol.)
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
AUR is not the official distro. Complaining about arch because of the AUR is like complaining about Debian because you npm install some malware
Except the last arch news post is a month ago about virtualbox. I've blindly run pacman -Syu for years without issue
"No way to prevent this" says only distro where this regularly happens
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.
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.
Iptables change actually fucked me because I'd tweaked something stupid 12 years ago and forgot. Took lime 45-60 mins to fix
Active AUR malicious packages incident (the AUR is locked)
🤭 heh
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.
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: if you also read my other post about iptables, this is a completely different thing. I had two issues.
If you're running Virtualbox on Arch you deserve everything you get.
What's wrong with it?
Let me put it like this: Imagine you've won this beautiful pristine house full of potential and it cost you absolutely nothing. You can rennovate and decorate and do anything you want with it. Endless possibilities.
Instead, the first thing you decide to do is call up Larry Ellison and invite him to personally come and shit on your kitchen floor. And one day you forgot his shit was still on the floor and you stepped in it and now Larry's shit is all through your house. And then the phone rings and it's Larry because he's been monitoring your house and now his lawyers are suing you for stepping in his shit.
In addition to VirtualBox being a fucking awful piece of software, Oracle is the absolute antithesis of Linux - anti-user, anti-freedom. Why would you put that closed-source, privacy-trampling, proprietary bullshit on your pristine Linux install? . Use KVM virtualization instead, or even a more modern docker-ish like solution.
Arch explicitly says "never do this"
Well yeah and cigarettes tell you not to smoke them
Lol. Care to explain how your analogy stands?
Arch will give you cancer
Hasn’t yet. Ubuntu, on the other hand, managed to piss me off completely
I have been using arch linux. And I havent gotten cancer yet. How do i have to be using arch linux to get it?
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.
You need to be wearing striped thigh-highs I think
Hasn't yet. Ubuntu, on the other hand, managed to piss me off completely
Edit: sorry, wrong thread
Damn I thought you were about to say Ubuntu gave you cancer
I was :) But then decided it wasn't that serious
Lol. Care to explain how your analogy stands?
It stands as written.
To 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.
Why, what news? What I need to be careful this time?
What happened with Arch?
Wait, let me update real quick and reboot, brb
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.
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.
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.

top 92 comments