My laptop just shut off without warning. No "you're on battery and its almost empty" popup. No automatic hibernate, just power off. Odder still, when I connected AC, and powered back up, a few minutes after logging in, I got a popup telling me my battery was critical, even though it was charging. Then another telling me I have approximately 'Unknown time of battery remaining'. If I hover over the applet, I get a 'Laptop battery 3 hours 45 minutes until charged (3.5%)' balloon /proc/acpi/battery/* looks like this right now.. alarm: unsupported present: yes design capacity: 59500 mWh last full capacity: 59500 mWh battery technology: rechargeable design voltage: 10800 mV design capacity warning: 5950 mWh design capacity low: 120 mWh capacity granularity 1: 0 mWh capacity granularity 2: 1 mWh model number: serial number: battery type: Lion OEM info: Sony Corporation present: yes capacity state: ok charging state: charging present rate: 15161 mW remaining capacity: 2160 mWh present voltage: 10265 mV lshal | grep battery shows.. udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0' battery.charge_level.current = 2160 (0x870) (int) battery.charge_level.design = 59500 (0xe86c) (int) battery.charge_level.last_full = 59500 (0xe86c) (int) battery.charge_level.percentage = 3 (0x3) (int) battery.charge_level.rate = 15161 (0x3b39) (int) battery.is_rechargeable = true (bool) battery.model = '' (string) battery.present = true (bool) battery.rechargeable.is_charging = true (bool) battery.rechargeable.is_discharging = false (bool) battery.remaining_time = 13615 (0x352f) (int) battery.reporting.current = 2160 (0x870) (int) battery.reporting.design = 59500 (0xe86c) (int) battery.reporting.last_full = 59500 (0xe86c) (int) battery.reporting.rate = 15161 (0x3b39) (int) battery.reporting.technology = 'Li-ion' (string) battery.reporting.unit = 'mWh' (string) battery.serial = '' (string) battery.technology = 'lithium-ion' (string) battery.type = 'primary' (string) battery.vendor = 'Sony Corporation' (string) battery.voltage.current = 10265 (0x2819) (int) battery.voltage.design = 10800 (0x2a30) (int) battery.voltage.unit = 'mV' (string) info.capabilities = {'battery'} (string list) info.category = 'battery' (string) info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0' (string)
*** Bug 495483 has been marked as a duplicate of this bug. ***
This happens to me all throughout the F-11 development cycle too. On two different laptops, if you drain the battery until g-p-m automatically powers off the machine, attempts to reboot the machine -- while on AC power -- will fail. Once GDM is started, currently g-p-m will detect the critical battery status and initiate a shut-down, *even on AC*.
just had it happen again in different circumstances. laptop had been suspended, and had ran out of power overnight. plugged in power, and turned on. booted up. a few minutes later, up popped a dialog telling me it was going to shutdown in 'unknown time' because the battery was critically low. I've seen this happen about a half dozen times in the last week. All with the latest rawhide bits applied.
I'm guessing the battery is not identifying itself as charging when it's very low. When you completely discharge the machine, if you plug in the power, then wait 60 seconds, then turn on the machine, does this still happen? DeviceKit-power looks at the battery state, not the AC state when it's doing policy actions. It's the only sane way (IMO) to do this when you're dealing with multiple batteries in one machine, or with multiple power supplies. If you boot the machine when completely discharged, what's the output of "devkit-power --dump"? Thanks.
I get this behaviour too... I didn't really get the point with multiple power supplies : as long as we're one power supply we shoudln't hibernate, should we ? BTW it takes more than 60 sec for me, actually I have to wait 'til the battery level is >2% if I don't want gpm to rehibernate my laptop.
Can you try installing https://admin.fedoraproject.org/updates/F11/FEDORA-2009-5740 and https://admin.fedoraproject.org/updates/F11/FEDORA-2009-5728 and then reboot please. Thanks.
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
I am using fedora 11 full release here 1. gnome-power-manager does not hibernate when my battery is at 4% with AC unplugged 2.giving wrong battery reading most times 90% when acpi already at 77% 3.info bubble popup giving "on battery" when plugging AC in 4. battery icon often disappears even when I selected "show icon when there is a battery"
actually it hibernated at 2% because my battery is not as fit. The battery icon on the gnome panel still does not display with correct information about charge. "battery low" popup message still display at wrong times or delayed
Running gnome-power-manager-2.26.2-1.fc11.x86_64. Removing the power chord: "You have approximately 4 minutos of remaining battery life (98.1%)" Reconnecting the power chord: "The AC power has been unplugged. The system is now using battery power"
yes this exactly what I got as well. Popup wrong messages.
additional problem to devkit-power/gpm is the cpu fan full speed every time you are at login screen and doesnt stop for a long time. I am not sure if it is to do above problem. I started the devkit-power --monitor with AC plugged in then logout and while at the login screen the log says: "Device Changed: /org/freedsktop/DeviceKit/Power/devices/battery_BAT0" repeatedly while the cpu fan is running high.
I'm not sure if it's useful, but this is what I get from devkit-power monitor: [pedro@pmatiello-notebook ~]$ devkit-power -m Monitoring activity from the power daemon. Press Ctrl+C to cancel. # Removing power cable. device changed: /org/freedesktop/DeviceKit/Power/devices/line_power_ACAD device changed: /org/freedesktop/DeviceKit/Power/devices/battery_BAT1 daemon changed: # Connecting power cable. device changed: /org/freedesktop/DeviceKit/Power/devices/line_power_ACAD daemon changed: device changed: /org/freedesktop/DeviceKit/Power/devices/battery_BAT1 ^C Is this expected?
I have observed the same behaviour and same messages as in comment#10, after moving to Fedora 11 from Fedora 10. Output or devkit-power --monitor: [rajeesh@anish-laptop tinyAccounting]$ devkit-power --monitor Monitoring activity from the power daemon. Press Ctrl+C to cancel. #Unplgging power cable here device changed: /org/freedesktop/DeviceKit/Power/devices/line_power_ACAD device changed: /org/freedesktop/DeviceKit/Power/devices/battery_BAT1 daemon changed: #Plugging power cable back in device changed: /org/freedesktop/DeviceKit/Power/devices/line_power_ACAD daemon changed: device changed: /org/freedesktop/DeviceKit/Power/devices/battery_BAT1 ^C
I missed the version details in comment#14. DeviceKit-power-008-1.fc11.i586 gnome-power-manager-2.26.2-1.fc11.i586 I think bug#501367 is related to/duplicate of this.
you can try gnome-power-manager 2.27 in rawhide. works great so far for me now. solves the above issues.
I'm not sure if it's ok to mix packages from gnome 2.26 and gnome 2.27. I'm still waiting for a fix for f11. I'll be happy to test any updates suggested by the maintainers.
I've already built DeviceKit-power 009 and gnome-power-manager 2.26.3 which when used together should approximately match the logic what is in rawhide. Grab them here: https://admin.fedoraproject.org/updates/gnome-power-manager-2.26.3-1.fc11 https://admin.fedoraproject.org/updates/DeviceKit-power-009-1.fc11
I installed both packages and rebooted the system. It seems to be working fine here now. Thanks!
Cool. Please add positive karma to the updates when you get a few minutes. Thanks.
I've added comments in both pages with the "works for me" option, but the karma hasn't increased. Do I need an account or this behaviour is expected?
It did not work for me. Fujitsu-Siemens Esprimo Mobile 9200
I found that with this new update it hibernates by itself on resume when the battery is full. Had to resume twice to bring up the system.