Comment 13 for bug 993440

I can confirm the significance of the problem as long as hibernate cannot be guaranteed to work reliably on all hardware platforms.

It seems Suspend works more often and can help to keep the system long enough available when the battery is at a critical level.

The user should have the option to use either Suspend or / and Hibernate independently of whatever the battery level is.

An option, in case the hardware does allow to hibernate reliably, can be made available in which case the user can select Hibernate or Suspend at a critical battery level.

Right now on my system ( Kernel: 3.16.0-38-generic x86_64 (64 bit) Desktop: Cinnamon 2.8.8 Distro: Linux Mint 17.3 Rosa) Hibernate fails, and Suspend is not allowed if the battery is critically low.
It may also have to do with the inaccurate battery status that does not exactly show how much power is left, meaning the system keeps running still until I find a mains plug, and I would have even more time with Suspend state.

I can understand the logic, that in theory at very low battery level the Suspend state does not protect the system to fail when the last battery energy is really (accurately measured) gone.
But even then, the user should have the freedom to overwrite the behavior for his own purpose, i.e. in my case, I would loose less data with Suspend and battery level critically low.

I would really look forward to have the option to Suspend at a battery level critically low.