registry team mailing list archive

[Peter Curtis <secondary@xxxxxxxxxxx>]

Alfrenovsky

The 'drain in 10 minutes' limit might still gives us a potential problem
between 10 minutes battery life left and the 2 minutes that is the
normal shutdown point on machines that have intermediate readings.

A delay of 30 secs  would use some of the hibernate time and need the
standard 120 seconds to be increased to say 150 secs so neither are
perfect.

I tried a time as short as 10 ms on Jauntyin 'invalid-timeout'  and
could not reproduce the effect there so I am not sure we have got to the
bottom of it. i suspect the answer will be obvious to the writers of
upower and gnome-power-manager as it has obviously been an issue in the
past and many others have found it and the ' use_time_for_policy' fudge
as shown by a google search for use_time_for_policy .

The output of a script such as yours on a higher time resolution for
various machines may help them set suitable default parameters if they
can not make them available via the Configure Editor.

By the way, I have put a way of making Configure Editor available via
the Applications menu and avoiding using a terminal on my 'Wind' web
page at www.pcurtis.com/wind.htm#critical_power for users who are
frightened of the terminal (95%?!)

-- 
Power manager mistakenly thinks my battery power is critically low, and hibernates -- MSI Wind U100
https://bugs.launchpad.net/bugs/558627
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for gnome-power.