Play stupid games, win stupid prizes.
memes
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
"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.
Foot-guns are my PROTECTED SECOND AMENDMENT RIGHT.
Arch explicitly says "never do this"
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.
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)
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
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.
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.
That's why I go for boring distros like Fedora
If you want really boring, go for Debian.
Yeah, lol. Arch people keep telling me that this never happens, and yet here it is.
Nah. Debian is fine for me.
Except the last arch news post is a month ago about virtualbox. I've blindly run pacman -Syu for years without issue
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.
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
That's why I use archdebian gives me all the latest software 5 years later.
archdebian? arch+debian dual boot?
What specifically happened? Can you share the news item?
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.
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.
Why, what news? What I need to be careful this time?
Nothing. OP is imagining an idiot for imaginary internet points.
i use arch btw
this happened to me once in 6 years. it was my own fault.
I love me my arch, but yes. This is a reality.
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.
Why would anyone want to use a distro that can break at any update unexpectedly or have to read articles first to see if it's safe is beyond me.
It's too much of a hassle.
yeah windows do be like that
I've yet to have one of my windows systems brick itself. Several of my Linux systems have.
Any distro can break at any update. If you've ever done a major upgrade on any fixed-release distro, you have very likely experienced some sort of issue.
And the solution is very simple (and the same for all distros): Enable Snapshots, roll back if important stuff breaks.