this post was submitted on 22 Aug 2026
22 points (89.3% liked)

Linux

18816 readers
319 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 3 years ago
MODERATORS
warmaster@lemmy.world
22
What are the worst distro-specific problems you have faced? (lemmy.world)
submitted 2 days ago by TheTwelveYearOld@lemmy.world to c/linux@lemmy.world
11 comments fedilink hide all child comments
 

More specifically, issues for one distro (or maybe family of distros if applicable) and not other distros.

I'll start: NixOS. I love how I can have my whole operating system configuration defined deterministically with configuration files, but what I believe is a serious flaw, is when you choose the "unstable" channel, the channel for receiving the latest packages rather than ones up to 6 months old: stable. Unstable package often build dependencies on device, and I've often faced build failures, why are new package versions given if they fail to build?!

Why can't Nixpkgs backend ensure that new package versions build successfully before shipping them to end users?! It would take a lot of work to do so, but I can't think of any other distros that have this problem: where installing a new package version that came out a few days or even a week ago, has a chance of failing after its made available in the distro's official package manager.

There are a handful of workarounds for your NixOS configuration in this case, but it happens too often for me and I shouldn't have to edit my config for to work around it.

you are viewing a single comment's thread
view the rest of the comments
[–] turdas@suppo.fi 7 points 2 days ago

I don't think I've ever faced a distro-specific problem when I really think about it. I've had headaches with SELinux on my Fedora Server machine, but those aren't really a Fedora problem.

Packaging might be the only thing that qualifies, so I guess the only thing would be the occasional package conflict I'd get when I used RPMFusion's Mesa builds and they fell behind the main Fedora repo's dependencies.