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.
Debian - the very slight value hassle of having to install the web blobs for glances manually. This is really minor, because it only comes up occasionally, but it’s rare enough that I can’t remember what the path is each time.
That said, I totally agree with Debian’s stance on the issue, and I think glances should change their process. Debian’s way makes me acknowledge the risk of installing the blob. It’d be nice if there was a package I could install after going, yep, I know this is potentially dangerous.
Honestly I thought I’d be disappointed with Debian on my gaming machine, but it works fine. I updated Wine to the newer version on their site (instead of using Debian’s packages), and it works great.