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.

  • MyNameIsRichard@lemmy.ml
    7·
    23 days ago

    Fedora Core (so it’s quite a while ago) had dependency hell on a completely fresh install. In fact it was the first update. I’m still salty about it!

  • CrypticCoffee@lemmy.ml
    4·
    23 days ago

    OpenSuse TW. Network seems to be permission based. If I’m connected to the Internet on one user and someone logs in, they cannot connect without my pass. Quite ridiculous.

    Oh, and I used to hibernate. Then it stopped working. Now I try to sleep and that sporadically fails requiring restart.

    • GunnarGrop@lemmy.ml
      4·
      23 days ago

      Used Tumbleweed as my main OS for years and this was always a pain point. Why do you need root privileges to connect to a network on a fresh install?? I can’t be bothered to find a link, but Linus Torvalds himself complained about this and said it was the reason he didn’t want his kids to use SUSE/openSUSE on their computers, since he didn’t want them to have root privileges, lol.

  • Ludrol@szmer.info
    3·
    23 days ago

    Bazzite: You can’t rollback if you replace rpm-ostree binary with a buggy bash script

  • stuner@lemmy.world
    2·
    23 days ago

    Mostly, I’ve only had minor issues: Old packages on Linux Mint, missing packages on Debian and Arch, system instability after updating without a reboot on many distros (NixOS, Fedora, Alma, …). But I’ve had two major issues that caused me to abandon a distro:

    1. On Fedora KDE, I felt that my system was overall not as stable as other distros. Then they decided to ship (as a rolling update to a “stable” version) an experimental KDE patch that broke the lock screen for a week. The breakage itself was not so bad, but shipping a patch before upstream merged it to their nightly builds irked me quite a bit.

    2. On NixOS, I was not able to get development stuff to work (I’m probably just too dumb for Nix/NixOS). First, I tried to set up a dev workflow that has quite a few external constraints (glibc version, Python version, running on other distros, …). I failed on multiple fronts and gave up on this. Then I tried to build my own KDE/Kirigami app on NixOS and also struggled a lot with it. I struggled for quite a while but gave up on it in the end. I moved to CachyOS afterwards and it worked flawlessly 🤷

  • Samsy@lemmy.ml
    2·
    23 days ago

    Fedora Selinux, I mean, yes security is important. But how often is it in the way. In docker my mounts always need a :z and other stuff. Switched back to Debian. Apparmor doesn’t need this finetuning and just works.

  • JackbyDev@programming.devEnglish
    1·
    22 days ago

    Arch and derivatives expect you to check the news file before upgrading, but do not integrate this into the upgrade tool. I have not personally ran into a problem this way, but it’s frustrating that pacman doesn’t have any capability to do this if you’re expected to.

  • Infernal_pizza@lemmy.dbzer0.comEnglish
    0·
    23 days ago

    This is a fairly minor issue since it’s quite an easy fix, but it really annoys me that Debian doesn’t include the sbin folders in the default user path. Meaning that if you try to run a command that needs sudo, instead of telling you it needs sudo it just says the command doesn’t exist