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.
Bazzite: You can’t rollback if you replace rpm-ostree binary with a buggy bash script
Wait really? What did they do? Is there a forum announcement about this?
Nothing. That was totally PEBCAK-class problem.
Edit: For questionable maintainers decisions I have seen a few. They changed default wifi manager that didn’t work with enterprise networks/encryption and sometimes nvidia driver versions desynchronise between flatpak and system breaking GPU rendering in blender.
Got it you worried me for a sec there 😅
Yeah they definitely aren’t perfect but it’s good enough for me, I’m too lazy to manage my OS myself