GNOME Bugzilla – Bug 506305
Battery low level -> No Messages, No Actions
Last modified: 2008-04-06 21:34:06 UTC
Please describe the problem: When battery level is low, nothing appear. No notifies (libnotify is active) and it don't suspend my system (the option is enabled). Simply the system goes down and i lost all my unsaved works! Also at the boot i find Inconsistency in my file systems. The only solution is manually check sometimes the battery level and shutdown the notebook before it halt. My notebook is a Dell XPS M1330. Steps to reproduce: 1. Waiting for low battery level 2. 3. Actual results: The system goes down Expected results: G-P-M should show me a message and, if when power is critical, suspend my system. Does this happen every time? Other information: System uname: 2.6.22-suspend2-r2 i686 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
Created attachment 101803 [details] gnome-power-bugreport.sh output
At what percentage level does your computer turn itself off?
(In reply to comment #2) > At what percentage level does your computer turn itself off? I've checked it: When g-p-m indicates 0%/1%. After is impossible to turn on the notebook on battery because it's completely drained.
When your system is discharging at < 10% can you get the output of: killall gnome-power-manager gnome-power-manager --verbose --no-daemon You'll need to let it run for a few minutes. Thanks.
Created attachment 101851 [details] The output of "gnome-power-manager --verbose --no-daemon" asked.
I'm seeing this as well, I left it until my computer (IBM x31) was beeping manicly (gpm reported battery level as 0.1W), nothing happened at all, no notification or anything. I see in the attachment above: "profile is not accurate. Not doing policy action" If that what it sounds like (i.e. as gpm doesn't know about the discharge profile yet it isn't going to take any action?), that sounds to me like an extremely bad idea....
Confirming this issue on Ubuntu Hardy Alpha 5.
Same problem with ubuntu gutsy and debian lenny
Created attachment 106329 [details] gpm-debug-25_2-1 the first file I wrote about
Created attachment 106330 [details] gpm-debug-25_2-2
Created attachment 106331 [details] last debug file gpm-debug-1-3-08
Don't know why but it's working today. I'll try to explain all I've done (at least all I remember) because maybe something is usefull. In the file "gpm-debug-25_2-1" I saw a line (63) saying "[gpm_array_load_from_file] gpm-array.c:264 (11:44:31): cannot open file /home/franute/.gnome2/gnome-power-manager/profile-MW1/HW1$-charging.csv" so, I created the directory "~/.gnome2/gnome-power-manager/profile-MW1" After that, I took again a debug file (gpm-debug-25_2-1), but nothing changed, no notification and no action. I remember that I removed the package "laptop-mode-tools" and when the battery level was at 10% the notification dialog appeared and later, my laptop switched off by itself. The new debug-file is "gpm-debug-1-3-08". I don't know if this is usefull, if any information is needed just tell me.
Comment on attachment 106330 [details] gpm-debug-25_2-2 the second file
Ahh, /home/franute/.gnome2/gnome-power-manager/profile-MW1/HW1$-charging.csv contains an invalid char '$' - it's likely your BIOS doesn't adhere to the ACPI spec. Can you try using trunk please, as I added a fix for this a couple of weeks ago.
I'm marking the Launchpad version of this bug as resolved. With the updated GPM and HAL it is working for me now.
As stated on launchpad: "Latest updates for Hardy (alpha6), 3-4 days ago has broken this again for me, no notifications, no actions on low/crit battery."
also broken for me in hardy beta You can find logs https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/135548