Bug 703791

Summary: readings from upower delayed by 13 minutes
Product: [Fedora] Fedora Reporter: Tomasz Torcz <tomek>
Component: upowerAssignee: Richard Hughes <richard>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: rhughes, richard
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 20:02:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
log file from upower --monitor-detail none

Description Tomasz Torcz 2011-05-11 09:25:13 UTC
Description of problem:
I've noticed that readings from upower are delayed by few minutes.  The noticable lag is  apparent - for example percentage is falling down even after reconnecting UPS to mains power.
I am using APC Back-UPS ES 700VA, connected via USB.

Please see attached log files (created by upower --monitor-detail).
Timeline of events:

1) UPS was fully charged
2) UPS was disconnected from mains 09:06:52.  The beeper on ups starts beeping.
3) upowerd continue to claim UPS is connected and fully charged.
4) at 09:18:52 upower started to notice that UPS is discharging. 13 minutes delay!
5) UPS continue to discharge, percentage in upower goes steadily down.
6) UPS reach critical battery charge at 09:26:56. Beeper starts sounding critically. I've reconnected mains. UPS started charging itself.
7) At this moment, upower reports UPS is at 67% full with 14.2 minutes of runtime left.
8) UPS keeps charging, upower keeps reporting decreasing percentage.
9) at 09:28:22 upower notices UPS is charging, updates time to empty and percentage.
10) while UPS is charging, upower still reports _decresing_ percentage.
11) at around 09:35 upower begin to increase percentage.

This is second time I do this test. Previously after _reconnecting_ UPS mains, upower kept reporting decreasing percentage for about 15 minutes before noticing UPS is charging.

Version-Release number of selected component (if applicable):
upower-0.9.10-1.fc15.i686

How reproducible:
Always.

Steps to Reproduce:
1. Disconnect mains from UPS
2. Observe upower --monitor-detail
3. Wait few minutes before UPS state is updated
  
Actual results:
information provided by upower is delayed by about 13 minutes.

Expected results:
Reported UPS state information should be up-to-date.

Comment 1 Tomasz Torcz 2011-05-11 09:44:17 UTC
Created attachment 498240 [details]
log file from upower --monitor-detail

Sorry, forgot attachment.

Comment 2 Richard Hughes 2011-09-05 13:10:05 UTC
Hmm, I've never heard of anything like this before. Could you try resetting the UPS hardware (i.e. unplugging it, turning it off, leaving it a few minutes, turning it back on, and plugging it in) and see if you can reproduce? If this doesn't work, then can you please get me the daemon log of upower --verbose and reproduce the delay. Thanks.

Comment 3 Fedora End Of Life 2012-08-07 20:02:57 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping