gnome-power-manager does not detect battery discharging
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devicekit-power (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
gnome-power-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
In Karmic, gnome-power-manager does not detect the current charge of the battery while it is discharging. To summarize:
1. Disconnect power cord:
2. Note that gpm's tray icon detects that the power cord's disconnected, and says 99% battery
3. Wait a while
4. Note that the battery charge monitor applet shows the charge dropping, while the tooltip of gnome-power-manager shows the battery still full.
5. Plug the cord back in.
6. Note that gpm's tray icon detects that the power cord is plugged back in, and suddenly knows the correct charge.
To be make things even clearer, I shall attach a screenshot of the power graph, with data points enabled. Basically, the charge level of the battery is only detected when the power cord is disconnected, when it's connected, and when it's charging, but not when it's discharging. This is dangerous as the user will not be warned when the power hits critical level (because gpm thinks it's still 99%), and the system will not auto-hibernate despite being configured to do so, resulting in "sudden death" of the computer with the battery completely exhausted.
ProblemType: Bug
Architecture: amd64
Date: Thu May 28 18:03:49 2009
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.26.1-0ubuntu4
ProcEnviron:
PATH=(custom, user)
LANG=en_SG.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-power-manager
Uname: Linux 2.6.30-
UnreportableReason: This is not a genuine Ubuntu package
Changed in devicekit-power (Ubuntu): | |
status: | Invalid → New |
status: | New → Invalid |
Changed in gnome-power-manager (Ubuntu): | |
status: | Invalid → New |
I'd like to add that -0ubuntu4 does not exist at the moment, but is actually -0ubuntu3 with the applied debdiff from Bug #381187. The only thing different is the notify-osd patch. I can confirm that this behaviour happens even with -0ubuntu3.