Description of problem: Happen on a Dell Lattitude D620 laptop with a second battery. gnome-power-manager triggers shutdown in case of the second battery runs empty while second battery is still on 100%. Version-Release number of selected component (if applicable): F11 version, laptop is currently powered off... How reproducible: At least one time Steps to Reproduce: 1. Put in second battery 2. Let laptop run Actual results: Both batteries are recognized, the internal one keeps 100% while the second one is used. In case this battery runs out of power, an automatic shutdown is triggered. Expected results: Trigger of automatic shutdown only in case of both batteries are running empty. Additional info:
Have you tried the DeviceKit-power and gnome-power-manager in updates testing? Thanks.
Hmm, looks like I have already the latest ones, neither --enablerepo updates-testing nor --enablerepo rawhide shows me newer packages # grep power /var/log/yum.log May 25 22:04:16 Installed: DeviceKit-power-008-0.1.20090401git.fc11.i586 May 25 22:05:01 Updated: gnome-power-manager-2.26.1-3.fc11.i586 # rpm -qa |grep power DeviceKit-power-008-0.1.20090401git.fc11.i586 gnome-power-manager-2.26.1-3.fc11.i586
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Looks like versions from updates-testing fix this problem: DeviceKit-power-008-1.fc11.i586 gnome-power-manager-2.26.2-1.fc11.i586 But still a strange message was displayed according to that the system runs out of battery, some minutes later gnome-power-manager recognized, that the second battery is now used. Perhaps this can be improved somehow, e.g. displaying 2 battery symbol (or one symbol containing 2 batteries).
I'm seeing this two on my Dell D620 laptop. What's even worse - if one battery is out of juice, even if the laptop is on AC power, after login g-p-m reports that the battery is low and turns off the machine .. but I'm on AC!
*** This bug has been marked as a duplicate of bug 511411 ***