Bug 1020973 - upower statuses often incorrect
Summary: upower statuses often incorrect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: upower
Version: 20
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F20BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2013-10-18 15:58 UTC by Adam Williamson
Modified: 2013-11-24 21:11 UTC (History)
4 users (show)

Fixed In Version: upower-0.9.23-1.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-24 01:42:40 UTC


Attachments (Terms of Use)

Description Adam Williamson 2013-10-18 15:58:28 UTC
As reported by hadess in IRC:

<hadess> adamw, the values for "on battery" and "on ac" are nearly random
<hadess> adamw, "lid-is-closed" was always true, so was on-battery, on-low-battery, is-docked, and lid-force-sleep
<hadess> adamw, what this means is different on each desktop, but it's pretty bad

This could cause all kinds of issues - incorrect power management, closing the lid of a laptop not causing suspend (and so cooking the laptop), odd external display behaviour and various others. We really ought to fix it for Beta. https://admin.fedoraproject.org/updates/upower-0.9.23-1.fc20 should fix the problem. Proposing as a freeze exception issue.

Comment 1 Fedora Update System 2013-10-18 16:00:28 UTC
upower-0.9.23-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/upower-0.9.23-1.fc20

Comment 2 Tomasz Torcz 2013-10-18 16:20:06 UTC
I wonder if this is related to #703791 , which I lost interest in analysing further.

Comment 3 Fedora Update System 2013-10-19 00:14:23 UTC
Package upower-0.9.23-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing upower-0.9.23-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-19428/upower-0.9.23-1.fc20
then log in and leave karma (feedback).

Comment 4 Mike Ruckman 2013-10-21 16:59:20 UTC
Discussed this in 2013-10-21 Blocker Review Meeting [1]. Accepted as a freeze exception issue as it can cause confusing and potentially problematic behaviour with power management.

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-21/

Comment 5 Fedora Update System 2013-10-24 01:42:40 UTC
upower-0.9.23-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 jan p. springer 2013-11-03 19:33:55 UTC
(In reply to Fedora Update System from comment #3)
> Package upower-0.9.23-1.fc20:
> * should fix your issue,
> * was pushed to the Fedora 20 testing repository,
> * should be available at your local mirror within two days.
> Update it with:
> # su -c 'yum update --enablerepo=updates-testing upower-0.9.23-1.fc20'
> as soon as you are able to.
> Please go to the following url:
> https://admin.fedoraproject.org/updates/FEDORA-2013-19428/upower-0.9.23-1.
> fc20
> then log in and leave karma (feedback).

any chance to get this for f19 too?

Comment 7 jan p. springer 2013-11-24 16:37:36 UTC
hi,

is there any chance to get upower-0.9.23-1.fc19? i'm willing to test and leave double karma if necessary.

out of sheer desperation i just downloaded and installed upower-0.9.23-1.fc20 (well yum just let me do it), but it doesn't work (executing upower just does not return anything). i'm stuck with f19 for some time (at least until march) and would really appreciate a fix for hibernating usually at the most inconvenient of times.

Comment 8 Adam Williamson 2013-11-24 16:45:12 UTC
I don't believe this bug is thought to affect f19. You're probably hitting something else.

Comment 9 jan p. springer 2013-11-24 21:11:26 UTC
maybe, maybe not. it would still though if upower-0.9.23 was available for f19 to find out.


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