GNOME Bugzilla – Bug 508779
When systems starts pulling from second battery the "Battery Discharging" warning pops up again
Last modified: 2009-03-04 14:49:22 UTC
[ forwarded from http://bugs.debian.org/460233 by Julien Goodwin ] On this machine (Lenovo T61) with two batteries installed (main and Ultrabay) the system only pulls from one at a time, but when the first is exausted and the system switches to the second the "Battery Dischaging" message reappears. Linked with this when the AC is plugged in it reports "Battery Charged" straight away as the system starts charging the flattest battery first.
Please can you get the output of gnome-power-bugreport.sh please. Thanks.
Distro version: cat: /etc/*-release: No such file or directory Kernel version: 2.6.24-1-amd64 g-p-m version: 2.20.2 HAL version: 0.5.10 System manufacturer: LENOVO System version: ThinkPad T61 System product: 7658CTO AC adapter present: yes Battery present: yes Laptop panel present: yes CPU scaling present: yes Battery Information: battery.charge_level.current = 0 (0x0) (int) battery.charge_level.design = 29160 (0x71e8) (int) battery.charge_level.last_full = 29160 (0x71e8) (int) battery.charge_level.percentage = 0 (0x0) (int) battery.charge_level.rate = 0 (0x0) (int) battery.is_rechargeable = true (bool) battery.model = '41U4890' (string) battery.present = true (bool) battery.rechargeable.is_charging = false (bool) battery.rechargeable.is_discharging = false (bool) battery.reporting.current = 0 (0x0) (int) battery.reporting.design = 29160 (0x71e8) (int) battery.reporting.last_full = 29160 (0x71e8) (int) battery.reporting.rate = 0 (0x0) (int) battery.reporting.technology = 'Li-poly' (string) battery.reporting.unit = 'mWh' (string) battery.technology = 'unknown' (string) battery.type = 'primary' (string) battery.vendor = 'SONY' (string) battery.voltage.current = 11002 (0x2afa) (int) battery.voltage.design = 10800 (0x2a30) (int) battery.voltage.unit = 'mV' (string) battery.charge_level.current = 37410 (0x9222) (int) battery.charge_level.design = 37430 (0x9236) (int) battery.charge_level.last_full = 41620 (0xa294) (int) battery.charge_level.percentage = 89 (0x59) (int) battery.charge_level.rate = 24080 (0x5e10) (int) battery.is_rechargeable = true (bool) battery.model = '42T5225' (string) battery.present = true (bool) battery.rechargeable.is_charging = false (bool) battery.rechargeable.is_discharging = true (bool) battery.remaining_time = 5592 (0x15d8) (int) battery.reporting.current = 37410 (0x9222) (int) battery.reporting.design = 37430 (0x9236) (int) battery.reporting.last_full = 41620 (0xa294) (int) battery.reporting.rate = 24080 (0x5e10) (int) battery.reporting.technology = 'Li-ion' (string) battery.reporting.unit = 'mWh' (string) battery.technology = 'lithium-ion' (string) battery.type = 'primary' (string) battery.vendor = 'Panasonic' (string) battery.voltage.current = 15698 (0x3d52) (int) battery.voltage.design = 14400 (0x3840) (int) battery.voltage.unit = 'mV' (string) GNOME Power Manager Process Information: 1000 4923 0.0 0.6 216020 12624 ? Ss Mar26 0:10 gnome-power-manager HAL Process Information: 107 4328 0.0 0.1 28836 2704 ? Ss Mar26 0:32 /usr/sbin/hald root 4329 0.0 0.0 17708 1184 ? S Mar26 0:07 \_ hald-runner root 4342 0.0 0.0 19820 1176 ? S Mar26 0:01 \_ hald-addon-input: Listening on /dev/input/event2 /dev/input/event1 /dev/input/event3 /dev/input/event4 /dev/input/event5 /dev/input/event6 /dev/input/event7 root 4344 0.0 0.0 19832 1240 ? S Mar26 0:00 \_ /usr/lib/hal/hald-addon-cpufreq 107 4345 0.0 0.0 16640 1016 ? S Mar26 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.