CriticalPowerAction=Suspend should be supported

Thank you for your bug report, it has been reported upstream as well on
https://gitlab.freedesktop.org/upower/upower/issues/23

Which got that reply

'Suspend still uses significant amounts of power, and if you run out of power and do a hard powerdown when suspended bad things can happen.'

Upstream seems to be ignoring the user's wishes. Would Ubuntu be willing to take the patch?

By the way the actual discussion seems to be this one:

https://gitlab.freedesktop.org/upower/upower/issues/59

And this is the unmerged PR with the simple patch:

https://gitlab.freedesktop.org/upower/upower/merge_requests/11

Please include at least this patch on the package. It allows setting Suspend as the action but does nothing if the user hasn't explicitly done that.

You may also want to consider just having Suspend be a fallback option before PowerOff. These days users are much more likely to have a laptop that suspends properly and prefer that to happen and just quickly grab a charger and continue instead of having their computer do a full poweroff.

The attachment "Patch that keeps the defaults unchanged but allows the setting in the config file" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

I've once again lost my open session because upower has decided a shutdown is a sensible thing to do instead of just suspending and allowing me to just find a charger. Please consider this an actual bug and not just a "Wishlist" item. It's something that deeply frustrates users continuously. Orderly shutdowns are a relic of the past. Suspend or just dieing from lack of battery are both much better options for a laptop. That upstream has decided to force this behavior is unfortunate but the patches are simple enough.

I would like to add my voice here and say that a patch, either to upstream UPower or to Ubuntu's version would be much appreciated. I've lost work several times as neither HybridSleep nor Hibernate work on my laptop so it simply shuts down, and due to a quirk of the batter management the delay between the notification of low % and then the critical threshold and shutdown is often only mere seconds.

I've attached a patch already. I've been running for over a year now with no issues.

I have found a (dirty?) workaround for this. The idea is simple: use a udev rule to suspend the laptop before UPower shuts it down. This can be done by creating a file /etc/udev/rules.d/99-lowbat.rules with the following content:

# Suspend the system when battery level drops to 5% or lower
SUBSYSTEM=="power_supply", ATTR{status}=="Discharging", ATTR{capacity}=="[0-5]", RUN+="/usr/bin/systemctl suspend"

You can of course tune the threshold.

This method seems to work well for me. If you want to use a threshold that's lower than the UPower one, *I think* you could set the PercentageAction parameter to 0% or 1% in /etc/UPower/UPower.conf, although I'm not 100% sure this is a good idea (the disclaimer at the beginning of the file seems to discourage users from directly modifying the file).

Reference: https://wiki.archlinux.org/title/laptop#Hibernate_on_low_battery_level

On a side note, I definitely wish this bug could be addressed. It's not normal that a computer just shuts down and makes you lose your work when there's still battery. Also note that afaik there's currently no way to enable hibernation with full disk encryption, so this limitation of UPower will become increasingly serious as more and more users will make the (right) choice to use FDE.

I've been running patched upower for a year and a half now. It has saved me in a few occasions. By far the most common scenario is that I've forgotten to plugin and it just suspends and I reconnect it and get going again. Shutdown is just useless, you still lose your work so might as well let the power fail completely. Ubuntu should just ship the patch.

I don't know what automation concluded that a fix was released but what happened instead is that upstream has once again refused to address this and just closed the bug reports. I suggest Ubuntu just ship the patch in its packages.