Comment 124 for bug 135548

Revision history for this message
Raúl Núñez de Arenas Coronado (dervishd) wrote : Re: [Gutsy] Action on critical battery isn't triggered - regression

My laptop does indeed hibernate (or suspend) succesfully, but last night I forgot to plug the AC power and let the laptop on. It didn't hibernate.

The problem, just in case anybody is having it, is that the time profiles are very optimistic in my machine, probably due to the fact that I haven't let the battery drain fully, ever. So, last night GPM thought that there were still time left when in fact the battery was empty.

I wasn't there (but I'm making the test right now) but I'm more or less sure that GPM issued the "low battery" warning because I swear I've seen it at some point in the past. I'm not so sure about the "critical" warning, since it should happen when only 5 minutes of battery remains. Given that the time profile was so optimistic, the laptop probably had the battery empty when GPM thought that there was half an hour left :(((

I don't know if people usually drains their batteries, but if they don't, time profiles are going to be very optimistic. Using time left for taking actions is, in that case, dangerous. Battery percentages should be much safer unless the battery lies about the percentages (which looks like it is very common...).

The solution is to tweak by hand threshold values using gconf-editor and use percentage instead of time left if profiles are way too optimistic.

I'm now carrying a test to see if time left reported by GPM has to do anything with reality in my laptop.

BTW, anybody knows where to go to know how to interpret discharge-time-profiles? I don't understand mine and maybe it explains the wrong behaviour of GPM in my laptop :?