[hardy] guidance-powermanager does not display right information on battery discharging or charging

Bug #196638 reported by deepdraft
4
Affects Status Importance Assigned to Milestone
acpi (Ubuntu)
Invalid
Undecided
Unassigned
kde-guidance (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kde-guidance-powermanager

I am running latest Kubuntu Hardy alpha on Dell Latitude D510 and when the battery is discharging the kde-guidance-powermanager does not display the right information.
It always shows the the battery level is 100%, if the battery was fully charged or is stuck at different value, if not fully charged. It always says "Discharging" and the time always 0:00h.
The level when discharging not on full battery is higher the the level it was showing a second ago, while charging.

It also shows time "0:00h to charge" when charging, but the battery level is changing.

Revision history for this message
deepdraft (dimitar.nedev) wrote :
Revision history for this message
deepdraft (dimitar.nedev) wrote :
Revision history for this message
nosrednaekim (nosrednaekim) wrote :

Could you provide the contents of "/proc/acpi/battery/BAT1/state" while charging, charged, and discharging?

Revision history for this message
deepdraft (dimitar.nedev) wrote :

I all three cases I got:
present: no

Revision history for this message
nosrednaekim (nosrednaekim) wrote :

in that case, I'm changing this to a bug in ACPI.

Revision history for this message
Scott Kitterman (kitterman) wrote :

This is almost certainly a kernel bug.

Changed in kde-guidance:
status: New → Invalid
Revision history for this message
deepdraft (dimitar.nedev) wrote :

Under the latest development version of Kubuntu 8.04 I can report that I did not manage to reproduce the bug, hence assuming it got fixed.

Revision history for this message
J. Austin Rodriguez (jeanaustinr) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

Changed in acpi (Ubuntu):
status: New → Invalid
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.