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.
When I was building a new dedicated Linux gaming PC, I opted for Mint as my Distro because of all of the recommendations and the very helpful compatibility database which gave me more confidence in the new components I was picking out. What ultimately killed my interest in Mint with the Cinnamon DE was the use of X11 and I had an issue with screen tearing that no amount of tweaking could fix.
After forcing Mint to use a newer kernel version, so it could actually detect my Radeon 9060XT, and making my system unbootable while trying to edit the X11 config file, I ultimately switched to Fedora Workstation which uses Wayland. This solved my problem and also allowed me to use variable refresh rate and HDR with no issues. I am not using the rolling release version of Fedora; the versions I am getting appear to be stable and only a few weeks/months behind.