Red Hat Bugzilla – Bug 815733
GUI is giving incorrect information about battery state.
Last modified: 2015-02-17 09:14:28 EST
Created attachment 579832 [details]
Description of problem:
I'm quite curious where the Gnome takes the information about battery charging.
Since my kernel battery status tells me this:
# cat /proc/acpi/battery/BAT0/state
capacity state: ok
charging state: charged
present rate: 0 mW
remaining capacity: 46030 mWh
present voltage: 11925 mV
# cat /proc/acpi/battery/BAT0/info
design capacity: 56160 mWh
last full capacity: 56160 mWh
battery technology: rechargeable
design voltage: 10800 mV
design capacity warning: 2808 mWh
design capacity low: 200 mWh
cycle count: 0
capacity granularity 1: 1 mWh
capacity granularity 2: 1 mWh
model number: 92P1141
serial number: 1726
battery type: LION
OEM info: SONY
Which definitely means that charging of my battery is not in progress - and it's correct since I'm using different charging thresholds.
Here is what extra tp_smapi shows:
--- TLP 0.3.6 --------------------------------------------
+++ ThinkPad Battery (Main)
/sys/devices/platform/smapi/BAT0/manufacturer = SONY
/sys/devices/platform/smapi/BAT0/model = 92P1141
/sys/devices/platform/smapi/BAT0/manufacture_date = 2007-11-12
/sys/devices/platform/smapi/BAT0/first_use_date = 2007-12-06
/sys/devices/platform/smapi/BAT0/cycle_count = 49
/sys/devices/platform/smapi/BAT0/design_capacity = 56160 [mWh]
/sys/devices/platform/smapi/BAT0/last_full_capacity = 56160 [mWh]
/sys/devices/platform/smapi/BAT0/remaining_capacity = 46030 [mWh]
/sys/devices/platform/smapi/BAT0/remaining_percent = 82 [%]
/sys/devices/platform/smapi/BAT0/remaining_running_time_now = not_discharging [min]
/sys/devices/platform/smapi/BAT0/remaining_charging_time = not_charging [min]
/sys/devices/platform/smapi/BAT0/force_discharge = 0
/sys/devices/platform/smapi/BAT0/power_now = 0 [mW]
/sys/devices/platform/smapi/BAT0/start_charge_thresh = 40 [%]
/sys/devices/platform/smapi/BAT0/stop_charge_thresh = 70 [%]
I'll attache gnome window picture - and one could observe charging state,
which is also being displayed on the applet window.
And since the value of actual capacity remains the same - it's obvious there is no charging.
And one extra - from which version number applet lost the ability to start gnome-power-statistic on right mouse button ?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.