FS#14262 - [gnome-power-manager] battery charge level stuck on 100% after charge

Attached to Project: Arch Linux
Opened by akhenaton (aky) - Thursday, 16 April 2009, 11:46 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 14 June 2009, 13:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:
after the battery fully loads and i remove the ac adapter gnome-power-manager continues to show 100% charge on the battery even until my laptop powers off because of depleted battery
i checked the battery level with `acpi` and that one shows the good/real value [for the battery charge level]

Additional info:
* package version(s)
gnome-power-manager 2.26.0-1
* config and/or log files etc.


Steps to reproduce:
leave the laptop on ac adapter until the battery reaches 100% charge then remove the ac adapter [and from now on the battery status on gnome-power-manager will continue to show 100%]

i'll be glad to provide any further details on this issue, my config[s] or anything needed in order to solve this

kind regards
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Sunday, 14 June 2009, 13:46 GMT
Reason for closing:  Fixed
Comment by akhenaton (aky) - Thursday, 16 April 2009, 14:10 GMT
reverting to gnome-power-manager 2.24.4-1 [from my /var/cache/pacman/pkg] solved the problem: after reaching 100% charge on battery and removing the ac adapter gnome-power-manager will now, again, correctly update the percentage of remaining battery thus making possible a suspend on critical battery and also notifying me about the low battery level
this makes me think it's a bug on the new gnome-power-manager [from gnome 2.26]

just to be sure it's clearly stated: i use x86_64 archlinux with full gnome 2.26; i cleanly installed arch on this system after xorg-server 1.6 [and gnome 2.26] were moved on extra [stable] so no configs or anything else to remove/alter/.. because there were no prior versions of gnome or xorg-server before these that could possibly interfere with gnome-power-manager 2.26.0-1 [except gnome-power-manager 2.24.4-1 which was updated later than the rest of gnome 2.26 packages]

kind regards
Comment by akhenaton (aky) - Friday, 17 April 2009, 08:20 GMT
i dug through the docs and wikis and as far as i understand the new gnome-power-manager doesn't use hal anymore but devicekit instead and if i understand correctly devicekit is new enough to be more error prone than hal so maybe it's a devicekit thing after all
the old [2.24.4-1] gnome-power-manager not only shows correctly the battery status after full/100% charge but also keeps track of charge/discharge history for my battery, things at which the new gnome-power-manager fails miserably
following pacman's current dependency info the only package that can drag devicekit on my system is devicekit-power [needed by the new gnome-power-manager, 2.26.0-1] which, in turn, depends on devicekit itself; i can't find any other packages depending directly or indirectly on devicekit at the moment
i'm wondering if anyone noticed/experienced the bug i reported here
Comment by Jori Hardman (jyro215) - Monday, 20 April 2009, 16:29 GMT
I'm having the same problem using x86_64 and gpm 2.26. The issue seems to happen to me after suspend. If I plug my laptop back in after suspending, the applet begins reporting the correct % again.
Comment by Jori Hardman (jyro215) - Monday, 20 April 2009, 17:51 GMT
I'm having the same problem using x86_64 and gpm 2.26. The issue seems to happen to me after suspend. If I plug my laptop back in after suspending, the applet begins reporting the correct % again.
Comment by Federico Chiacchiaretta (baghera) - Tuesday, 21 April 2009, 12:19 GMT
same problem here, I'm on i686.
Comment by Jori Hardman (jyro215) - Tuesday, 21 April 2009, 18:43 GMT
Right clicking the applet and bringing up power history shows info on the battery. I noticed that after unplugging my laptop, the refreshed field keeps increasing. It seems that the battery info is not being automatically refreshed. Take a look at this post: https://bugzilla.redhat.com/show_bug.cgi?id=479322#c5
Comment by Jori Hardman (jyro215) - Tuesday, 21 April 2009, 20:24 GMT
I found a way to wake up the battery. Run this:

dbus-send --print-reply --system --dest=org.freedesktop.DeviceKit.Power /org/freedesktop/DeviceKit/Power/devices/battery_BAT1 org.freedesktop.DeviceKit.Power.Device.Refresh

I haven't tested this yet, but I bet adding the same command to a pm-suspend hook would fix the issue after waking from suspend.
Comment by akhenaton (aky) - Tuesday, 21 April 2009, 21:16 GMT
@Jori Hardman: i haven't used suspend EVER on this laptop so i doubt what i reported is related to your suspend problem
however the link you gave on redhat's bugzilla seems to cover your problem [involving suspend] and my problem too, so they might be related [in some way]
the thing is your fix doesn't apply in my case unless i always _manually_ run that right after the battery is 100% charged and i pull the plug
anyway.. as far as i can see the guys at ubuntu [ok, canonical :D ] are avoiding gnome-power-manager 2.26 and their next ubuntu release will come with gnome 2.26 but the power-manager will still be the one in gnome 2.24; maybe they saw there's a problem with the gpo+devicekit duo and they decided to let devicekit earn its territory before they allow it to the 'unwashed masses'; here's the proof: http://anotherubuntu.blogspot.com/2009/02/what-you-wont-get-in-jaunty.html

i consider this one to be really annoying and i think i must be fixed somehow because with the power manager not knowing the battery's real state you might end up loosing your work [from a premature and `unannounced`/unpredicted shutdown caused by uncaught battery depletion]; not a very nice thing after all, right? :|

maybe somebody, somehow manages to find at least a temporary fix to this

kind regards
Comment by João Vieira (Vieira) - Saturday, 06 June 2009, 18:31 GMT
It's probably solved in 2.27.
Comment by Jan de Groot (JGC) - Saturday, 13 June 2009, 13:21 GMT
please try devicekit 008 and gnome-power-manager 2.26.2.
Comment by akhenaton (aky) - Sunday, 14 June 2009, 13:33 GMT
i just tested gnome-power-manager 2.26.2-1 and it seems to do the job correctly
no more "IgnorePkg = gnome-power-manager" in my /etc/pacman.conf :)
thank you, Jan!

Loading...