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
Opened by akhenaton (aky) - Thursday, 16 April 2009, 11:46 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 14 June 2009, 13:46 GMT
|
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
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
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
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.
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
no more "IgnorePkg = gnome-power-manager" in my /etc/pacman.conf :)
thank you, Jan!