It’s bluca, yo.
As a random example, here is bluca breaking suspend-then-hibernate, then being a complete asshole about it, while other systemd devs are trying to put the fire out. Do read his code reviews on the latter. yuwata and keszybz have nerves of steel.
The current behaviour is fully expected and documented
bluca is cancer.
Yo, setup hibernation and use hybrid sleep as your default sleep.
ln -s /etc/systemd/system/suspend.target ../../../usr/lib/systemd/system/suspend-then-hibernate.target
Now any sleep is hybrid. The machine suspends, then wakes up after a timeout, and enters hibernation. The timeout is configurable in systemd-sleep.conf(5).
With this combo I find that I prefer S0 to S3. S0 drains the battery about twice as fast, sure, but it resumes instantaneously, while S3 takes about 30 seconds (!) to resume on this machine. And the thing hibernates and powers off if I leave it for an hour anyway.
I have a fist-gen Framework 13 (Intel 11). If I want to upgrade to fully match the new gear, what needs upgrading…?
Off the top of my head:
I should probably get a new keyboard as well, as I’m one of the people with the DEL key randomly going dead.
I already replaced:
I can hold on to the £10 wireless card, the PCIe3 SSD that I bought after WD just died one day, and the compressed alufoil that is the main body.
Well fuck me.
Yall understand that what actually changed is a symlink? That systemd-run is now linked from run0, and that’s enough to make a SUID-less sudo?
You silly goose. Sweden, a major arms exporter and one of the world’s top 3 arms exporters per capita is, in fact, the western military-industrial complex.