Earlier quoted context omitted.
That reminds me of another one... (Ubuntu htpc) I can "shut-down" and the remote startup works, but if it actually goes into suspend, I have to hit the actual power button in the cabinet. And more often than not the audio is broken on resume from suspend and I have to completely shut down to fix it (reboot doesn't work)... this is with a core i3-5010u, which is a relatively common intel audio chipset. I agree there a…
Remote startup and wakeup is actually handled by firmware of your mainboard. (or Intel ME) Ubuntu cannot fix hardware problems most of the time. Drivers still breaking in S3 is often a result of lack of Windows driver workarounds for this case. And Ubuntu using slightly outdated kernel versions.
I keep running it, my point was that it's not exactly rosey with Linux all of the time either.