Unplugging AC power reports critical battery / auto-suspend; battery is actually full

[flan_suse]

Ubuntu Lucid Lynx 10.04
Fully updated packages
Kernel: 2.6.32-22-generic

The computer is an MSI Wind u100 netbook, 3-cell battery. The BIOS is flashed with the latest available firmware, which is 1.0G, released on 2010-01-04.

Upon unplugging the netbook from AC power, the panel reports that the battery is critically low (2 minutes left) even though the indicator applet also reports the battery is 100% charged; and then the system auto-suspends without confirmation. After resuming from suspend, the panel reports that the battery is 100% charged (or whatever the actual value is.) In other words, the system is doing what is set under Power Management, which is to suspend when the battery is critically low. The problem is, the battery is NOT critically low, and the notification bubble reports the battery 100% charged, but only has 2 minutes left.

Whatever information is needed, I will supply. I am not sure if this is related to the kernel or a particular package.

This did not happen on Ubuntu Karmic Koala 9.10, 2.6.31 kernel.

=== WORKAROUND ===

gconftool-2 --type bool --set /apps/gnome-power-manager/general/use_time_for_policy false

(from <https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/572541/comments/1>)

=== apport info ===

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:223: no soundcards found...
Date: Tue May 11 21:31:05 2010
MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic root=/dev/mapper/sda9_crypt ro quiet splash i8042.reset
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: linux
dmi.bios.date: 12/01/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: U90/U100
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: Ver.001
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.chassis.version: Ver.001
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
dmi.product.name: U90/U100
dmi.product.version: Ver.001
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

[Jeremy Foshee (jeremyfoshee)]

Hi flan_suse,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[flan_suse (flansuse)]

The same exact thing occurs, even on Mainline Kernel 2.6.34-999-generic, i386.

[flan_suse (flansuse)]

A more accurate description of the problem: The indicator applet will report the battery is 100% charged, but it will also say "2 minutes remaining", in which it will suspend.

[Konstantin Lavrov (lacosta)]

It is gnome-power-manager bug.

Here is workaround:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/572541/comments/1

[flan_suse (flansuse)]

Reply to comment #5:

So the gconf workaround will force gnome-power-manager to read the "percetage remaining" in order to dictate critical battery level, instead of "time remaining"?

[flan_suse (flansuse)]

I applied the gconf workaround (ran in a terminal as the current user), and it seems to fix the problem, for the time being.

I notice that it will still report the battery as 100% charged with only 2 minutes remaining, but it will not suspend; it acts as if the battery is not at a critical level anymore. I guess the gnome-power-manager package needs to be patched with a fix for Lucid.

[flan_suse (flansuse)]

Almost forgot! Thank you for the tip, Konstantin!

[Milton (miltonlaufer)]

I have the same problem (on a MSI PR310X) and it's very annoying. I hope
that a patch appears soon!

[flan_suse (flansuse)]

@Milton, comment #9:

For the time-being, try the temporary workaround in comment #5. It's not a "fix" but it works, until gnome-power-manager is patched.

[Jeremy Jongsma (jeremy-jongsma)]

Same on my Dell Vostro 1710. After resume from suspend, if I unplug the power cord it gives me a critical battery warning even at 90% power. Fortunately it doesn't actually hibernate for me (just displays the dialog), which may be another bug.

[Milton (miltonlaufer)]

Thanks! The workaround worked perfectly. But, as it was said, I still get the 2 minute message. Anyway, thanks again! [Every time more proud to be an Ubuntu user for almost three years :) ]

[Ketil Wendelbo Aanensen (ketilwaa-deactivatedaccount)]

I'm also experiencing this on an MSI s262. Thanks for the workaround in comment #5

[David Tombs (dgtombs)]

flan_suse: could you please execute the following command in a terminal to gather gnome-power-manager info:

apport-collect 579069

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

[David Tombs (dgtombs)]

Cancel that, Konstantin already created a good report at bug 531190. Marking as duplicate.