Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 452297 - Kpowersave inaccurately reports charge when battery is added after KDE startup
Summary: Kpowersave inaccurately reports charge when battery is added after KDE startup
Alias: None
Product: Fedora
Classification: Fedora
Component: kpowersave
Version: 9
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-20 19:18 UTC by Greg W
Modified: 2008-07-28 20:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-07-28 20:22:16 UTC

Attachments (Terms of Use)

Description Greg W 2008-06-20 19:18:08 UTC
Description of problem:
KPowersave reports battery at 1% charged in a Compaq Presario F700 laptop.
KPowersave also doesn't seem to recognize when the battery is removed.
Gnome-power-manager seems to report the battery charge properly.

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Start KDE with the battery absent from the laptop
2. Add fully charged battery to the laptop
3. Remove AC plug
Actual results:
KPowersave reports 1% charged on the battery
if battery is removed while KDE is running, it does not change to the 'AC Power
only' icon, difficult to tell if other expected behavior occurs

Expected results:
Accurate charge report on the battery

Additional info:
I found this because I tend to run on AC power only without the battery present
and when I want to move around I add the battery and remove AC adapter.
I usually run the laptop on AC power to avoid unnecessary charge/discharge
cycles on the battery.
It was behaving as expected in Fedora 8.

Comment 1 Steven M. Parrish 2008-06-20 20:48:26 UTC
Checked upstream and could not find matching bug report.  Please report upstream
at and add upstream info to this report.  We will monitor
upstream for resolution.  Thanks 

Comment 2 Steven M. Parrish 2008-07-28 20:22:16 UTC
The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present.  Since it has been thirty days or
more since we first requested additional information, we're assuming
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.

Thank you in advance.

Note You need to log in before you can comment on or make changes to this bug.