Created attachment 427655 [details] Screenshot Description of problem: Unplugging the power cord from my netbook with its battery nearly fully charged, causes a cascade of "Laptop battery critically low, The battery is below the critical levels and this computer is about to hibernate" "Battery discharging, 2 minutes of battery power remaining (97.1%)" ca. 2mins later the netbook is being shutdown. Version-Release number of selected component (if applicable): gnome-power-manager-2.30.1-1.fc13.i686 dbus-1.2.24-1.fc13.i686 hal-0.5.14-3.fc13.i686 How reproducible: Always. Steps to Reproduce: 1. reboot with power cord plugged in. 2. Login 3. unplug power cord. Actual results: Before-mentioned "notification boxes" pop up. Machine shuts down (hibernates?) shortly afterwards. Expected results: Machine not to shut down Additional info: * This behavior is completely bogus. The battery is nearly full and far away from being critically low. * openSUSE-11.2 on the same machine behaves correctly. * the machine is a Medion E1210 (almost identical to an MSI Wind U100), with a Intel Atom N270. * I am not sure if the culprit really is gnome-power-manager. I am inclined to think it's something underneath (kernel, dbus, hal, ... ??), but I don't know were to look into.
Have exact the same behavior now at a HP mini 2133 laptop running Fedora 14. Any idea, how we/I can help fixing this bug?
A "me too" from me on this. I see it on my Atom tablet PC, I'm currently working around it by setting gconf:/apps/gnome-power-manager/general/use_time_for_policy to false. If I unplug the mains, I get a pop-up "3 minutes (97%) remaining", but now no critical shutdowns. I'll attach some upower monitor logs below.
Created attachment 491876 [details] upower --monitor-detail output Output from upower --monitor-detail captured when tablet was running on mains, then unplugged, then plugged in again.
Ralf, Ingo, when your machines are on mains power, what do you see in /sys/class/power_supply/BAT0/current_now ? (Note: You may need to replace BAT0 above with something else appropriate to your system's battery.) If it's something ridiculous like 65336000 (or thereabouts, it's in micro-Amps), this probably indicates a BIOS issue.
James, using BAT1 I see indeed 65535000 there. Using the (not fully charged) 6-cell pack I see 62801000 there. So I can confirm your investigation. About your workaround: What exactly does setting this variable do? Are there any other effects to consider before setting that or can I safely set it to no? Regards, Ingo
I believe setting that gconf key simply tells g-p-m to use the percentage remaining to judge the critical power level, rather than estimated time left. In the meantime, I have filed kernel bug https://bugzilla.kernel.org/show_bug.cgi?id=33722 to track getting a workaround into the kernel. You may wish to follow this bug.
(In reply to comment #4) > Ralf, Ingo, when your machines are on mains power, what do you see in > /sys/class/power_supply/BAT0/current_now ? When being on AC power, */BAT1/current_now contains 0. Shortly after unplugging, it reports 461000, some seconds later it reports numbers in the 1000000 range.
My Toshiba u300-13u also auto-suspends in most cases after unplugging the power adapter. It also sometimes does it after resume (that means you have to resume two-three times). Gnome shell sometimes freezes after that (and is hard to kill and get back). By the way, closing the lid often does *not* make it suspend (that means you even have to close two-three times).
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I'm sorry I forgot to mention I'm seeing this on Fedora 15 (!)
(In reply to comment #6) > I believe setting that gconf key simply tells g-p-m to use the percentage > remaining to judge the critical power level, rather than estimated time left. > > In the meantime, I have filed kernel bug > https://bugzilla.kernel.org/show_bug.cgi?id=33722 to track getting a workaround > into the kernel. You may wish to follow this bug. OK, there's now a more general patch attached to this kernel.org bug that detects unreasonable current rates and works around it, solving the problem on my tablet. Might want to give that a go.
(In reply to comment #10) > I'm sorry I forgot to mention I'm seeing this on Fedora 15 (!) Me too: FC15 on a Sony VAIO BZ12XN.
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.
Bug is still present in all versions of Fedora.
Happens often in Fedora 15.
I made several tests and verified that this type of bug, at least on my computer, happens only when 'upower --dump' reports wrong value of 'lid-is-closed'. I now believe the battery check acts only triggers this bug but is not its cause (at least in my case). For this 'upower --dump' bug, please refer to Bug 718365.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping