On Tue, 17 Apr 2018 10:53:09 -0700
Samuel Sieb <samuel(a)sieb.net> wrote:
On 04/17/2018 04:55 AM, Wolfgang Pfeiffer wrote:
> Trying 'upower -d' here results in the display of current power
> settings ...
So that's why mine works. The output includes this line:
critical-action: HybridSleep
I do wonder what starts it up. The service is disabled although the
default is enabled and I didn't manually start it.
I'm getting curious about your settings, if that's not too intrusive:
mine are, with comments removed:
----------------------------------------------------->
% grep -v '^#' /etc/UPower/UPower.conf
[UPower]
EnableWattsUpPro=false
NoPollBatteries=false
IgnoreLid=false
UsePercentageForPolicy=true
PercentageLow=10
PercentageCritical=3
PercentageAction=2
TimeLow=1200
TimeCritical=300
TimeAction=120
CriticalPowerAction=HybridSleep
<------------------------------------------
IIRC when the battery was 0 a few days ago, the battery LED (here: the
Power On/Off button) started blinking fast, but no sleep was started.
Weird ...
The documentation for upower seems technichally to be missing on F26 -
so I have to guess whether Time{Low,Critical,Action} values actually
mean minutes or seconds ...
Archlinux has some documentation:
https://wiki.archlinux.org/index.php/Power_management#Hybrid_sleep
And that looks really interesting:
https://www.kernel.org/doc/Documentation/admin-guide/pm/sleep-states.rst
This latter page - after a glance on it - seems to suggest that sleep
modes are organized by the kernel, via three files. Here, they look
like so:
--------------->
% cat /sys/power/mem_sleep
s2idle [deep]
% cat /sys/power/state
freeze mem disk
% cat /sys/power/disk
[platform] shutdown reboot suspend test_resume
<--------------
HTH,
Wolfgang