My case is: When AC is unplug I immediately see "battery critically low" then the hibernate/suspend action is happend according the settings in power management.
So: devkit-power (or upower) reports enormous energy-rate for first time after cord is unplugged. GPM reacts on this first event not checking if situation changes after one second though then devkit-power starts to send right reports.
I can confirm my case (https:/ /bugs.launchpad .net/ubuntu/ +source/ gnome-power- manager/ +bug/516023 ) in Lucid Alpha 3.
My case is: When AC is unplug I immediately see "battery critically low" then the hibernate/suspend action is happend according the settings in power management.
The same situation like was described here http:// mail.gnome. org/archives/ gnome-power- manager- list/2010- January/ msg00001. html
So: devkit-power (or upower) reports enormous energy-rate for first time after cord is unplugged. GPM reacts on this first event not checking if situation changes after one second though then devkit-power starts to send right reports.
Plugging cord again not prevent to suspend or hibernate, but it is perhaps another bug in upstream https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 594739
How I can provide devkit-power output it seems that it is now upower.
But it seems upower --monitor-detail not fully implement devkit-power output
Will be gpm --verbose enough?