I just got back from a work trip and conference where, for four days, my laptop couldn't go to sleep and wake back up. Every time my laptop went into my bag, I

I just got back from a work trip and conference where, for four days, my laptop couldn't go to sleep and wake back up. Every time my laptop went into my bag, I had to fully shut down the entire system then when I got where I was going spend a bunch of time starting everything back up, getting all my context back up, etc. Good luck trying to search for sleep issues on Linux... I only managed to hunt anything down due to some incredible luck and a couple educated guesses. Apparently some recent systemd update decided to start freezing user.slice during suspend and either there's something wrong with this or there are bugs in the kernel (I'm not going to try and figure out which) that this fails if you use unusual and esoteric things like "kvm" or "nfs". The only way to recover the machine when this happens is a particular Magic SysRq incantation since even switching to a console TTY doesn't work directly. To resolve this in the meantime, you need to add a drop-in conf for systemd-suspend.service to set the `SYSTEMD_SLEEP_FREEZE_USER_SESSIONS` environment variable to revert the change in behaviour. This isn't even getting into all the esoteric bullshit involved in getting everything to a reasonably usable state in the first place. (Never did get full disk encryption working and partial encryption involved a lot of failed starts and reinstalls; Steam wouldn't show anything but a black screen without setting DRI_PRIME; fingerprint scanner required editing some PAM configs and still doesn't _really_ work right; ...) There is no chance in hell that the hours I've invested in Linux don't completely eclipse the hours it takes to deshittify Windows. I'm not switching off, but I'm not also going to be flippant about suggesting other people switch to Linux. It's a project, and not one everyone is willing or capable to take on.