Bug 1392198 - Neither UPower nor DeviceKit.Power could be initialized!
Summary: Neither UPower nor DeviceKit.Power could be initialized!
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: batti
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-05 23:29 UTC by Petr Machata
Modified: 2017-08-08 19:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 19:09:19 UTC
Type: Bug


Attachments (Terms of Use)
Fix (3.68 KB, patch)
2016-11-05 23:46 UTC, Petr Machata
no flags Details | Diff

Description Petr Machata 2016-11-05 23:29:29 UTC
Description of problem:

I'm getting the following output when I try to use batti on Fedora 24:

Neither UPower nor DeviceKit.Power could be initialized!
This can have multiple reasons.
Here is the error for UPower:

    org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.DBus.Properties' on object at path /org/freedesktop/UPower/devices/line_power_AC

And this is the error for DeviceKit.Power:

    org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.DeviceKit.Power was not provided by any .service files


Version-Release number of selected component (if applicable):
$ rpm -q batti
batti-0.3.8-9.fc24.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Run batti

Actual results:
As indicated above.

Expected results:
Batti runs and does battery stuff.

Additional info:

Comment 1 Petr Machata 2016-11-05 23:46:37 UTC
Created attachment 1217670 [details]
Fix

This packaging patch is formed against the master branch rather than F24, because I didn't realize master is the checked-out branch when I fedpkg clone'd.  Sorry about that.

I don't know why CanHibernate and CanSuspend are not available.  Per my brief reading of documentation they should, and the others (LidIsPresent, DaemonVersion, etc.) are available as expected.

Comment 2 Fedora End Of Life 2017-07-25 23:47:09 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 3 Fedora End Of Life 2017-08-08 19:09:19 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.