Red Hat Bugzilla – Bug 495989
gnome-power-manager doesn't let my second battery discharge
Last modified: 2013-04-02 00:22:42 EDT
I have two batteries in this laptop. It appears like they discharge serially. g-p-m seems to panic when the first battery gets low, and never gives the second battery a chance to discharge. Attaching some dumps from devkit-power --dump at various points. The last one happened within 10 seconds of the machine powering off.
Created attachment 339745 [details]
Created attachment 339746 [details]
Created attachment 339747 [details]
Created attachment 339748 [details]
The battery in /org/freedesktop/DeviceKit/Power/devices/battery_BAT0 never seems to have any state other than "unknown".
When the first battery is discharging, what's the value of the file:
As DeviceKit isn't either parsing the kernel value, or the kernel is not sure itself.
Also, can you please get one more "devkit-power --dump" output, this time after killing gnome-power-manager and letting the second battery start discharging. I want to see if the second battery ever reports a valid status.
Created attachment 340785 [details]
devkit-power --dump (after second battery kicks in)
Looks like the status on the second battery is right.
How very odd. I'll add support for this in DeviceKit-power tomorrow. Thanks for the debug dumps.
Tried gnome-power-manager-2.27.1-0.4.20090507git.fc12.x86_64; doesn't seem to fix the problem.
I've just purchased an IBM Thinkpad Ultrabay Slim Battery so I can debug this locally here. Sorry for the delay.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
*** Bug 511411 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.