wrong battery status info on top panel.

Bug #22280 reported by gurel kaynak
10
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
Medium
Ben Collins

Bug Description

I installed the latest Ubuntu (5.10) and did all the updates. But the battery
status is just rotating between the correct percentage after a few minutes says
that it's zero percent then again a few minutes later says that the laptop is
plugged and working with ac power. I have a Fujitsu-Siemens Amilo series laptop.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Does this still happen with the latest kernel in Breezy? Do you get the same
results from running "acpi" in a terminal?

Revision history for this message
gurel kaynak (gurel-kaynak) wrote :

(In reply to comment #1)
> Does this still happen with the latest kernel in Breezy? Do you get the same
> results from running "acpi" in a terminal?

yes this is happening with the latest kernel in Breezy. But when I run acpi that
just works. It shows the correct status of the battery. Power of the terminal :)

Revision history for this message
Matt Zimmerman (mdz) wrote :

Perhaps a HAL issue, then...are the values in Device Manager reasonable?

Revision history for this message
gurel kaynak (gurel-kaynak) wrote :

(In reply to comment #3)
in Device Manager the numbers are the same as top panel. Wrong. Im talking about
Battery Bay section.
the battery.charge_level.current and battery.charge_level.rate become 0 (zero)
every few minutes. And then it becomes normal again.

Revision history for this message
gurel kaynak (gurel-kaynak) wrote :

(In reply to comment #4)
> (In reply to comment #3)
> in Device Manager the numbers are the same as top panel. Wrong. Im talking about
> Battery Bay section.
> the battery.charge_level.current and battery.charge_level.rate become 0 (zero)
> every few minutes. And then it becomes normal again.
>
>

sorry not battery.charge_level.rate it should be percentage, not rate. Sorry
about that.

Revision history for this message
gurel kaynak (gurel-kaynak) wrote :

I realized that when battery.charge_level.current becomes 0,
battery.charge_level.percentage just disappears, instead of becoming zero. Is
that normal?

Revision history for this message
Martin Pitt (pitti) wrote :

Ryan, any idea about this?

Revision history for this message
Allison Karlitskaya (desrt) wrote :

No. I have no idea :)

Reporter: I suspect that you happened to run the 'acpi' command at a moment that
the kernel was providing the correct values. Can you try running something like:

while true; do acpi; sleep 1; done

And run that for a while and see if it experiences the same effect as the
battery applet?

Revision history for this message
gurel kaynak (gurel-kaynak) wrote :

ok I did that. So acpi shows the correct value when the information at the top
panel is wrong. So it goes like this:
Battery 1: discharging, 91%, rate information unavailable.
Battery 1: discharging, 91%, rate information unavailable.
Battery 1: discharging, 91%, rate information unavailable.

But when the top panel changes the status to zero acpi does something like this:
Battery 1: discharging, 91%, rate information unavailable.
Battery 1: charging/discharging, 90%, rate information unavailable
Battery 1: charged, 90%, rate information unavailable.
Battery 1: discharging, 90%, rate information unavailable.

So when passing from 91% to 90% something goes wrong and the program at the top
panel shows wrong information for a while.

When I tested this the laptop was unplugged from the power source. :)

Revision history for this message
Allison Karlitskaya (desrt) wrote :

If the ACPI commandline tool is freaking out like that then it must be a
kernel/acpi/dsdt/hardware/bios/???? issue.

Hi Ben :)

Revision history for this message
gurel kaynak (gurel-kaynak) wrote :

well the problem seems gone for the moment with the latest updates of kernel and
acpi-support.
Thanks all...

Revision history for this message
Ben Collins (ben-collins) wrote :

Ok, feel free to reopen the bug if it doesn't remain gone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.