drastic color scheme for battery mode

[Ralf Hildebrandt]

Binary package hint: gnome-power-manager

The indicator applet for the power management displays the status of my battery as red.
The red icon with a fill level of about "nothing left" is suitable to imply the imminent demise of my laptop's battery.

A closer look at the status reveals: A whopping 1h 10 minutes of runtime left (see screenshot).
So WTF is the icon red when there's really a quite a lot of time left? It would be ok to display a yellow warning, but red always implies a critical status. I'd consider 15 minutes to be a crititcal threshold, but 1h:10m?

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
Architecture: amd64
Date: Tue Dec 28 16:31:37 2010
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
MachineType: FUJITSU SIEMENS LIFEBOOK P8010
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic root=UUID=d3877693-43c0-45cc-821c-6c4dcd692cde ro quiet splash rootfstype=ext4
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gnome-power-manager
dmi.bios.date: 08/20/2008
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.08
dmi.board.name: FJNB1E3
dmi.board.vendor: FUJITSU
dmi.board.version: CP365186-01
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: P8010
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd08/20/2008:svnFUJITSUSIEMENS:pnLIFEBOOKP8010:pvr:rvnFUJITSU:rnFJNB1E3:rvrCP365186-01:cvnFUJITSUSIEMENS:ct10:cvrP8010:
dmi.product.name: LIFEBOOK P8010
dmi.sys.vendor: FUJITSU SIEMENS

[Gary M (garym)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #701941, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.