Reports "Laptop battery critically low" as soon as power supply is removed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
This happened in release 10.04 as well, but not before then IIRC.
When I remove the power, I get a notification message (? - the thing on a black background near the top right hand corner of the screen) saying "Battery discharging // 0.03 of battery remaining (95%)". The 95% is correct (it can be higher) but the 0.03 (hours.minutes?) is nonsense.
I also get a warning dialogue saying "Laptop battery critically low // Computer will hibernate very soon unless it is plugged in." However, the battery icon on the panel shows full, and hovering over it says something like "Laptop battery 2:30 left" and that is the correct situation - the warning dialogue shouldn't appear for ages.
As far as I can see, everything in gnome-power-
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.32.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Fri Oct 15 23:21:45 2010
ExecutablePath: /usr/bin/
GConfNonDefault:
/apps/
/apps/
/apps/
/apps/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gericom Ego
PccardctlStatus:
Socket 0:
3.3V 16-bit PC Card
Subdevice 0 (function 0) bound to driver "sdricoh_cs"
Socket 1:
no card
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: gnome-power-manager
XsessionErrors:
(polkit-
(nautilus:1459): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nm-applet:1458): Gdk-CRITICAL **: IA__gdk_
(nautilus:1459): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
dmi.bios.date: 08/12/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A1003IG7 V5.50
dmi.board.name: Ego
dmi.board.vendor: Gericom
dmi.board.version: REV.C
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Gericom
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: Ego
dmi.product.
dmi.sys.vendor: Gericom
Same problem here.
I can bypass gnome-power-manager hybernating or suspending my machine by killing it just before I disconnect power and re-starting it shortly after power has been disconnected.