battery indicator is wrong

[loeppel]

Binary package hint: gnome-power-manager

On my Siemens Esprimo Mobile M9400 the detection if its charging or uncharging is completely wrong.
If there is no AC Adapter plugged in, it shows "fully charged" but if i click on the icon it says X % full (less than 100).
If i plug in the AC Adapter there is a uncharging event followed of a charging event.
ACPI-fix not changes this.

ProblemType: Bug
Architecture: i386
Date: Mon Oct 19 22:17:38 2009
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.28.0-0ubuntu7
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
SourcePackage: gnome-power-manager
Uname: Linux 2.6.31-13-generic i686

[gmcd (gmcd)]

Same problem on 9.10. I have this problem since 8.04. I wonder I will be this bug ever repaired?

[yuszuv (bussibaer)]

Same problem here. KDE and XFCE battery indicators work well. And besides the GNOME battery indicator in the panel doesn't show the right icon, GNOME doesn't seem to recognize a "critical battery state". It just shows the menu where to choose from "logout", "shutdown", etc. and three seconds later the computer turns off (due to an empty battery?). What really sucks is, that then (sometimes) a lot of my preferences are deleted (as e.g. my sticky notes!). I really hope there will be a fix in the near future. It would be great!

[yuszuv (bussibaer)]

Additionally, I've noticed that the more times my notebook crashes due to the empty battery (I can't note because of this bug), the lower the battery's capacity gets. So the bug will ruin my battery with the time.

[Chris Coulson (chrisccoulson)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only whilst the indicator is incorrect, as it will automatically gather debugging information, in a terminal:

apport-collect 455786

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!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[yuszuv (bussibaer)]

Architecture: amd64
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.28.1-0ubuntu1.3
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
Uname: Linux 2.6.31-19-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

[Hans-Dominik (hdm-mail)]

Architecture: i386
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.28.1-0ubuntu1.3
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
Uname: Linux 2.6.31-20-generic i686
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare video
XsessionErrors:
 (gnome-settings-daemon:3248): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:3366): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:3347): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (firefox-bin:3623): GLib-WARNING **: g_set_prgname() called multiple times

[Hans-Dominik (hdm-mail)]

Architecture: i386
DistroRelease: Ubuntu 10.04
GnomeSessionIdleInhibited: Unknown
GnomeSessionInhibitors: Failed to acquire
GnomeSessionSuspendInhibited: Unknown
MachineType: FUJITSU SIEMENS ESPRIMO Mobile M9400
Package: gnome-power-manager 2.29.91-0ubuntu9
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=2ecf1db5-416d-47f2-940f-0d2aba1e6675 ro splash quiet splash
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Tags: lucid
Uname: Linux 2.6.32-17-generic i686
UserGroups: mythtv
dmi.bios.date: 03/10/2008
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.05 - R057 - 1566
dmi.board.name: M11D
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 1.0
dmi.chassis.asset.tag: CID
dmi.chassis.type: 1
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnPhoenix:bvr1.05-R057-1566:bd03/10/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileM9400:pvr1.0:rvnFUJITSUSIEMENS:rnM11D:rvr1.0:cvnFUJITSUSIEMENS:ct1:cvr1.0:
dmi.product.name: ESPRIMO Mobile M9400
dmi.product.version: 1.0
dmi.sys.vendor: FUJITSU SIEMENS

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

same with lucid beta 1

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[Hans-Dominik (hdm-mail)]

apport information

[gmcd (gmcd)]

Architecture: i386
DistroRelease: Ubuntu 10.04
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
MachineType: FUJITSU SIEMENS ESPRIMO Mobile M9400
Package: gnome-power-manager 2.30.0-0ubuntu1
PackageArchitecture: i386
ProcCmdLine: root=UUID=8a0e94a0-9fcb-43c8-9a4a-edfcec812951 ro splash quiet
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic-pae 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-20-generic-pae i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
dmi.bios.date: 03/10/2008
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.05 - R057 - 1566
dmi.board.name: M11D
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 1.0
dmi.chassis.asset.tag: CID
dmi.chassis.type: 1
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnPhoenix:bvr1.05-R057-1566:bd03/10/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileM9400:pvr1.0:rvnFUJITSUSIEMENS:rnM11D:rvr1.0:cvnFUJITSUSIEMENS:ct1:cvr1.0:
dmi.product.name: ESPRIMO Mobile M9400
dmi.product.version: 1.0
dmi.sys.vendor: FUJITSU SIEMENS

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

apport information

[gmcd (gmcd)]

same with Lucid beta 2

[Raynald (lahondes)]

same with Lucid

[Raynald (lahondes)]

this seems a duplicate of #270123

[Raynald (lahondes)]

I could resolve the bug using combining the trick in bug #270123 and the trick to update a buggy DSDT table in Karmic/Lucid : go to this bug to find out because it's really more a matter of ACPI than something to do with gnome-power-manager.

[yuszuv (bussibaer)]

So this seems to be a very easy to eliminate bug. Is there any chance that this can be done in the near future? This would be very cool, since I'm too dumb to compile without errors (aside from having seemingly too little hard disk space).

[gmcd (gmcd)]

Hi, nice to hear this has a solution. Could it be possible to fix this problem without recompiling kernel? XFCE and KDE indicators in Ludic stable work well.

[Matt Jones (mjones41)]

I have the same problem using a Fujitsu U9200 and Ubuntu 10.04. I do not believe this is a bios problem as when I run virtual box with a Ubuntu Host/XP guest, the Win XP will display the correct battery/charging state, complete with the low power warnings, it functions perfectly. There is just a problem with the way Ubuntu is displaying the battery/charging state.

[Hans-Dominik (hdm-mail)]

although affects Maveric beta, same as desrcibed above

[linuxrules (linuxrules)]

will this help

save this as /etc/acpi/battery.sh
in a root shell run: chmod +x /etc/acpi/battery.sh

#!/bin/sh
# UGLY HACK

AC_state=/proc/acpi/ac_adapter/AC/state

if grep -q "on-line" ${AC_state} ; then

    hal-set-property --udi `hal-find-by-capability --capability ac_adapter` --key ac_adapter.present --bool true

else

    hal-set-property --udi `hal-find-by-capability --capability ac_adapter` --key ac_adapter.present --bool false

fi

if code is in battery.sh add to top (below #!/bin/sh)

# UGLY HACK

AC_state=/proc/acpi/ac_adapter/AC/state

if grep -q "on-line" ${AC_state} ; then

    hal-set-property --udi `hal-find-by-capability --capability ac_adapter` --key ac_adapter.present --bool true

else

    hal-set-property --udi `hal-find-by-capability --capability ac_adapter` --key ac_adapter.present --bool false

fi

[Hans-Dominik (hdm-mail)]

with or without the script i get this results

if AC_Adaptor is pluged

root@laptop:/etc/acpi# hal-get-property --udi `hal-find-by-capability --capability ac_adapter` --key ac_adapter.present
true

if AC_Adaptor unpluged

root@hdm-laptop:/etc/acpi# hal-get-property --udi `hal-find-by-capability --capability ac_adapter` --key ac_adapter.present
false

-

to get script working i hafe to change

AC_state=/proc/acpi/ac_adapter/AC/state
to
AC_state=/proc/acpi/ac_adapter/ADP1/state

[linuxrules (linuxrules)]

did this help solve the problem?
I hope it did i had this problem and fixed it with that code.

[linuxrules (linuxrules)]

chmod +x bugfix.pl
su -c bugfix.pl

DONE!
ps may need to edit script if script fails

[linuxrules (linuxrules)]

fixed bug for bugfix.pl

line with

acpi_event() if ( !-f $acpi_event );

corrected to

QuickWrite($acpi_event, acpi_event()) if ( !-f $acpi_event );

[gmcd (gmcd)]

Thanks for fix, unfortunately, on my M9400 it's not working. System correctly recognize connection of AC adapter with or without fix. However, GNOME battery applet doesn't show it properly.
Conclusion: No change with or withour fix.
I appreciate your time and believe, we are almost there to really fix it. I can post any relevant information which could help you to fix it.
Thanks. John

[linuxrules (linuxrules)]

Does the GNOME battery applet use dbus?
Could that be the problem? (oh, wait did you reboot?)

[gmcd (gmcd)]

Thanks for respond linuxrules. Yeah, I've rebooted, my battery.sh in /etc/acpi looks like this:

jan@jan-laptop:~$ cat /etc/acpi/battery.sh
#!/bin/bash
### ID FOR ACPI / HAL BUGFIX DON'T TOUCH (START) ###
AC_state=/proc/acpi/ac_adapter/ADP1/state
if grep -q "on-line" ${AC_state} ; then

    hal-set-property --udi `hal-find-by-capability --capability ac_adapter` --key ac_adapter.present --bool true

else

    hal-set-property --udi `hal-find-by-capability --capability ac_adapter` --key ac_adapter.present --bool false

fi
### ID FOR ACPI / HAL BUGFIX DON'T TOUCH (END) ###
# UGLY HACK
jan@jan-laptop:~$

According to http://projects.gnome.org/gnome-power-manager/
Gnome power manager with it's applet gnome battery use DBus.

[linuxrules (linuxrules)]

Is this the whole file?
What if its the way GNOME Power Manager talks to dbus?
Maybe it's a problem in dbus?

I read it also reads udev

Wow! this is a tough egg to crack.

I have openSUSE on my laptop & Ubuntu on my desktop (and I'm on the laptop) So right now I'm almost clueless!

[linuxrules (linuxrules)]

can you run the below:

ls -l /etc/acpi/battery.sh
ls -l /etc/acpi/events/battery
cat /etc/acpi/events/battery
ls /proc/acpi/ac_adapter/

cat each entry from

ls /proc/acpi/ac_adapter/

and post the results

[linuxrules (linuxrules)]

do this with & with ac

ls /proc/acpi/ac_adapter/

cat each entry from

ls /proc/acpi/ac_adapter/

and post the results

[linuxrules (linuxrules)]

meant to say "wuth and wthout ac". Sorry

[linuxrules (linuxrules)]

curse this laptop keyboard! :)

[Hans-Dominik (hdm-mail)]

without any fixes installed, ...

i seems that NOT the ac_adapter/ADP1/state is wrog,
instead battery/BAT0/state is wrong when discharging see below.

*ac_adaptor is _pluged_ while Battery is fully
charged*

/proc/acpi/ac_adapter/ADP1$ cat state
state: on-line

cat /proc/acpi/battery/BAT0/state

present: yes
capacity state: ok
charging state: discharging
present rate: 0 mA
remaining capacity: 4383 mAh
present voltage: 12382 mV

*ac_aaptor is _unpluged_ while Battery is fully
charged*

/proc/acpi/ac_adapter/ADP1$ cat state
state: off-line

cat /proc/acpi/battery/BAT0/state
present: yes
capacity state: ok
charging state: charged
present rate: 2047 mA
remaining capacity: 4165 mAh
present voltage: 12066 mV

*ac_adaptor is _pluged_ while Battery is half discharged*

/proc/acpi/ac_adapter/ADP1$ cat state
state: on-line

/proc/acpi/battery/BAT0$ cat state

present: yes
capacity state: ok
charging state: charging
present rate: 2417 mA
remaining capacity: 3249 mAh
present voltage: 12426 mV

*ac_adaptor is _unpluged_ while Battery is half discharged*

/proc/acpi/ac_adapter/ADP1$ cat state
state: off-line

/proc/acpi/battery/BAT0$ cat state
present: yes
capacity state: ok
charging state: charged
present rate: 2178 mA
remaining capacity: 3251 mAh
present voltage: 11748 mV

[linuxrules (linuxrules)]

oh, are you saying that the charge level indicator of the battery is wrong?
how about:

# modprobe fujitsu-laptop

[linuxrules (linuxrules)]

add this to grub options:

acpi_osi=Linux

[linuxrules (linuxrules)]

http://www.google.com/search?q=kernel+options+acpi_osi+linux+fujitsu
https://wiki.ubuntu.com/HardwareSupport/Machines/Netbooks

[linuxrules (linuxrules)]

when grub pops up on boot
press E & add to kernel options: acpi=force

[yuszuv (bussibaer)]

Unfortunately, neither "modprobe fujitsu-laptop" nor "acpi_osi=Linux" nor "acpi=force" helps. If I try this, my python applet that reads out the current battery states, doesn't work anymore.

[yuszuv (bussibaer)]

I wonder if the reason for the problem is, that acpi doesn't recognize the status of the battery. If I run

jan@xylakant:/sys/class/power_supply/BAT0$ acpi
Battery 0: Unknown, 45

you can see, that the status of the battery is "unknown" if the ac adapter is *un*plugged, while it is

jan@xylakant:/sys/class/power_supply/BAT0$ acpi
Battery 0: Charging, 43%, 00:54:34 until charged

when the ac adapter is plugged. I think in the first case there should be an "uncharging" instead of "unknown". And could it be, that the xfce and kde battery indicators doesn't care if the status is "unknown" or not and just display the other (correct) informations while the gnome battery indicator stops working as it gets the information, that the battery status is "unknown"?

[yuszuv (bussibaer)]

Okay, I found out some things:

1. If the ac adapter is plugged in:

jan@xylakant:/proc/acpi/battery/BAT0$ lshal | grep ac_adapter
udi = '/org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ADP1'
  ac_adapter.present = true (bool)
  info.capabilities = {'ac_adapter'} (string list)
  info.category = 'ac_adapter' (string)
  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ADP1' (string)

jan@xylakant:/proc/acpi/battery/BAT0$ lshal | grep battery
udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0'
  battery.charge_level.current = 33399 (0x8277) (int)
  battery.charge_level.design = 57720 (0xe178) (int)
  battery.charge_level.last_full = 45299 (0xb0f3) (int)
  battery.charge_level.percentage = 73 (0x49) (int)
  battery.charge_level.rate = 27772 (0x6c7c) (int)
  battery.is_rechargeable = true (bool)
  battery.model = 'Modelxxx' (string)
  battery.present = true (bool)
  battery.rechargeable.is_charging = true (bool)
  battery.rechargeable.is_discharging = false (bool)
  battery.remaining_time = 1542 (0x606) (int)
  battery.reporting.current = 3009 (0xbc1) (int)
  battery.reporting.design = 5200 (0x1450) (int)
  battery.reporting.last_full = 4081 (0xff1) (int)
  battery.reporting.rate = 2502 (0x9c6) (int)
  battery.reporting.technology = 'Li-ion' (string)
  battery.reporting.unit = 'mAh' (string)
  battery.serial = 'SN' (string)
  battery.technology = 'lithium-ion' (string)
  battery.type = 'primary' (string)
  battery.vendor = 'Vendor12345678901234567890' (string)
  battery.voltage.current = 12389 (0x3065) (int)
  battery.voltage.design = 11100 (0x2b5c) (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)

2. If the ac adapter is unplugged, I get:

jan@xylakant:/proc/acpi/battery/BAT0$ lshal | grep ac_adapter
udi = '/org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ADP1'
  ac_adapter.present = false (bool)
  info.capabilities = {'ac_adapter'} (string list)
  info.category = 'ac_adapter' (string)
  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ADP1' (string)

jan@xylakant:/proc/acpi/battery/BAT0$ lshal | grep battery
udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0'
  battery.charge_level.current = 33843 (0x8433) (int)
  battery.charge_level.design = 57720 (0xe178) (int)
  battery.charge_level.last_full = 45299 (0xb0f3) (int)
  battery.charge_level.percentage = 74 (0x4a) (int)
  battery.charge_level.rate = 0 (0x0) (int)
  battery.is_rechargeable = true (bool)
  battery.model = 'Modelxxx' (string)
  battery.present = true (bool)
  battery.rechargeable.is_charging = false (bool)
  battery.rechargeable.is_discharging = false (bool)
  battery.reporting.current = 3049 (0xbe9) (int)
  battery.reporting.design = 5200 (0x1450) (int)
  battery.reporting.last_full = 4081 (0xff1) (int)
  battery.reporting.rate = -1 (0xffffffff) (int)
  battery.reporting.technology = 'Li-ion' (string)
  battery.reporting.unit = 'mAh'...

[yuszuv (bussibaer)]

OK, I managend to build my own kernel with the modified dsdt table. And it works. So I think it's only a matter of the acpi tables and not a bug in the gnome power manager. I wonder where I get send my corrected dsdt table, so that some day it will be integrated in the kernel. Can anyone help me to get this bug smashed?

[linuxrules (linuxrules)]

that’s what I thought it's a acpi dsdt table issue

[linuxrules (linuxrules)]

http://ubuntuforums.org/showthread.php?t=1036051
http://forums.linuxmint.com/viewtopic.php?f=60&t=18222

[yuszuv (bussibaer)]

So is there any way to get my fixed dsdt tables into the kernel?

[linuxrules (linuxrules)]

will this help:
https://help.ubuntu.com/community/ACPIBattery

[yuszuv (bussibaer)]

No, that doesn't help so much, because the option to load an dsdt table via the kernel boot options has deprecated. I just want that the corrected dsdt table I have is going to make it into the kernel source, but I don't know where and how to post my dsdt tables.

[linuxrules (linuxrules)]

this page gives info where to submit patch and extract dsdt table
http://www.lesswatts.org/projects/acpi/overridingDSDT.php

[linuxrules (linuxrules)]

http://acpi.sourceforge.net/dsdt/index.php

[Jonatan Zeidler (jonius)]

Will the repaired dsdt table come with any new kernel?

[linuxrules (linuxrules)]

It seem that there won't according to this: http://acpi.sourceforge.net/dsdt/index.php

[linuxrules (linuxrules)]

Try pressing the "Add attachment or patch" button on this launchpad page (and upload the DSDT table) and see if it go upstream to the kernel

[linuxrules (linuxrules)]

@yuszuv can you press the "Add attachment or patch" button on this launchpad page and upload the DSDT table

[linuxrules (linuxrules)]

should I mark this as in-progress

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.