Bug 1033969
| Summary: | upower uses wrong battery values | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | jan p. springer <jsd> | ||||||||
| Component: | upower | Assignee: | Richard Hughes <rhughes> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 19 | CC: | katmeef, rhughes | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2014-11-24 20:53:30 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 828433 [details]
grep -r . /sys/class/power_supply/BAT0
Created attachment 828439 [details]
upower --montor-detail
I have the same problem with Fedora 20 for the past 2 months, bug 1060579 unfortunately noone has responded to my bug report either... does anybody actually look at this bug? with upower-0.9.23-3.fc20.x86_64 this issue never showed up again. |
Created attachment 828432 [details] upower -d Description of problem: upower uses wrong values for energy-full that are clearly above energy-full-design, thus miscalculating charge and triggering hibernation often. Version-Release number of selected component (if applicable): upower-0.9.20-1.fc19.x86_64 How reproducible: Steps to Reproduce: 1. boot f19 (rMBP in my case) 2. watch upower to go wrong (upower --monitor-detail) 3. Actual results: after some time (minutes, sometimes half an hour) the energy-full value becomes non-sensical high, percentage changes and hibernation follows. resume usually corrects this fro some time before the cycle starts again. Expected results: normal battery drain until empty then hibernation; energy-full shoudl never exceed energy-full-design. Additional info: see attachment(s)