Bug 1598649 - upower no longer picks up events such as connecting/disconnecting from power source
Summary: upower no longer picks up events such as connecting/disconnecting from power ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: upower
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-06 06:06 UTC by Alexander Ploumistos
Modified: 2019-05-28 23:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:11:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alexander Ploumistos 2018-07-06 06:06:18 UTC
After the update to upower 0.99.8-1, events such as connecting or disconnecting from the power source aren't picked up any longer. If the laptop is plugged in after the system gets turned on, it retains the power scheme settings  for running on battery. I have to manually restart upower in order to get it to notice the change.
I have added a SELinux policy module to deal with the permission problems that appeared with this update (e.g. rhbz#1594554, rhbz#1593496), but that hasn't help with the problem.

Comment 1 David H. Gutteridge 2018-07-17 02:29:49 UTC
I'm seeing similar issues. (Adding myself to the CC list.)

Comment 2 Daniel Mach 2018-07-30 10:57:42 UTC
Same here.
I'm running Rawhide.
Downgrading from upower-0.99.8-2.fc29.x86_64 to upower-0.99.7-3.fc28.x86_64.rpm helped.

Comment 3 Arkadiusz Miskiewicz 2018-08-10 06:21:11 UTC
Most likely: https://gitlab.freedesktop.org/upower/upower/issues/68

Comment 4 Alexander Mikhaylenko 2018-09-20 21:55:13 UTC
Same on upower-0.99.8-2.fc29.x86_64 in F29.

Comment 5 David H. Gutteridge 2018-11-02 22:33:31 UTC
A related patch was added for Fedora 29 last month (https://src.fedoraproject.org/rpms/upower/c/6e20417f1c655343256743c8adae39e6c7f150e9), this addresses the issue for me.

Comment 6 Ben Cotton 2019-05-02 20:23:41 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

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 28 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.

Comment 7 Ben Cotton 2019-05-28 23:11:43 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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