auto hibernate / auto shutdown doesn't work when battery power is critical or the battery is totally empty before
Bug #136777 reported by
Fabien Lusseau
This bug report is a duplicate of:
Bug #135548: Action on critical battery isn't triggered.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: gnome-power-manager
It is the same problem in all my laptops (a dell inspiron 640m, an ASUS A6K and a Gericom Webgine)
And can you add a system to set the percentage of the battery when it auto shutdown/hibernate the GUI ?
It is a critical bug because it can cause damages to the lithium in the battery when the power is less than 5 % and reduce the battery uptime
Confirmed. I thought it was my imagination but since an update about a week ago (so, around 20th September 2007) gnome-power-manager doesn't hibernate the PC when battery level gets to critical. This had been working fine up to then and was in regular use.
I did a manual hibernate test from a fresh start, and it also fails. Screen goes blank immediately, there's no hard disk activity as you'd expect, and there is no way to interact with the PC (Ctrl+Alt+SysRq+K tried to restart GDM).
There's not much in the log files for the battery-critical event. syslog and daemon.log just show NetworkManager releasing and then re-establishing the network lease, kern.log just shows the restart, auth.log seems to show an hourly cron process at about the same time, but I think that is coincidence. Here's what could be found:
=== auth.log === cron:session) : session opened for user root by (uid=0) cron:session) : session closed for user root
Sep 26 03:17:01 hephaestion CRON[11416]: pam_unix(
Sep 26 03:17:01 hephaestion CRON[11416]: pam_unix(
=== acpid ==== power.sh" power.sh" power.sh" power.sh"
[Wed Sep 26 03:11:02 2007] executing action "/etc/acpi/
[Wed Sep 26 03:11:02 2007] BEGIN HANDLER MESSAGES
[Wed Sep 26 03:11:02 2007] END HANDLER MESSAGES
[Wed Sep 26 03:11:02 2007] action exited with status 0
[Wed Sep 26 03:11:02 2007] completed event "battery BAT0 00000080 00000001"
[Wed Sep 26 03:14:09 2007] received event "battery BAT0 00000080 00000001"
[Wed Sep 26 03:14:09 2007] notifying client 5379[107:115]
[Wed Sep 26 03:14:09 2007] notifying client 5928[0:0]
[Wed Sep 26 03:14:09 2007] notifying client 5928[0:0]
[Wed Sep 26 03:14:09 2007] executing action "/etc/acpi/
[Wed Sep 26 03:14:09 2007] BEGIN HANDLER MESSAGES
[Wed Sep 26 03:14:09 2007] END HANDLER MESSAGES
[Wed Sep 26 03:14:09 2007] action exited with status 0
[Wed Sep 26 03:14:09 2007] completed event "battery BAT0 00000080 00000001"
[Wed Sep 26 03:17:54 2007] received event "battery BAT0 00000080 00000001"
[Wed Sep 26 03:17:54 2007] notifying client 5379[107:115]
[Wed Sep 26 03:17:54 2007] notifying client 5928[0:0]
[Wed Sep 26 03:17:54 2007] notifying client 5928[0:0]
[Wed Sep 26 03:17:54 2007] executing action "/etc/acpi/
[Wed Sep 26 03:17:54 2007] BEGIN HANDLER MESSAGES
[Wed Sep 26 03:17:54 2007] END HANDLER MESSAGES
[Wed Sep 26 03:17:54 2007] action exited with status 0
[Wed Sep 26 03:17:54 2007] completed event "battery BAT0 00000080 00000001"
[Wed Sep 26 05:53:04 2007] starting up
[Wed Sep 26 05:53:04 2007] 72 rules loaded
[Wed Sep 26 05:53:05 2007] client connected from 5375[107:115]
[Wed Sep 26 05:53:05 2007] 1 client rule loaded
[Wed Sep 26 05:53:20 2007] client connected from 5923[0:0]
[Wed Sep 26 05:53:20 2007] 1 client rule loaded
[Wed Sep 26 05:53:22 2007] client connected from 5923[0:0]
[Wed Sep 26 05:53:22 2007] 1 client rule loaded
[Wed Sep 26 05:54:40 2007] received event "battery BAT0 00000080 00000001"
[Wed Sep 26 05:54:40 2007] notifying client 5375[107:115]
[Wed Sep 26 05:54:40 2007] notifying client 5923[0:0]
[Wed Sep 26 05:54:40 2007] notifying client 5923[0:0]
[Wed Sep 26 05:54:40 2007] executing action "/etc/acpi/