@nwcs it is on power outage. That's what I ment with "their configurable parameters might not be fully fleshed out", the default 3% battery in PercentageAction in #UPowerd was typically too low for me for a clean hibernation. And kernel image_size now being too low to hibernate in the first place.
So I was running out of laptop battery quite often this year, resulting in an unclean shutdown, leading to many fsck runs.
Also, #fsck had run a ridiculous amount of times for me this year already... Maybe like 20 times, once or twice a week?
It's pretty cool that we have these very powerful and flexible sleep/suspend systems thanks to the #Linux kernel, #upowerd, #systemd etc. now. But it also feels like their configurable parameters might not be fully fleshed out yet, causing a risk for data integrity.
Now /sys/power/image_size and before it had been the too low percentages in upowerd for me.
@normandc it works at least on the #librem5 with patched #upowerd. If the torch on your device uses the kernels #led interface you should be able to get it to work too.