Red Hat Bugzilla – Bug 1276665
KDE Reports that Power Management Plugin Not loaded but KDE setting lists the service as running
Last modified: 2016-07-19 14:56:02 EDT
Created attachment 1087920 [details]
Power management listed as not available
Description of problem:
KDE reports that the power management plugin as not running thus power management is not available. However in the KDE Setting the service is listed as running. Since the power management is not available, it is taking a long time to recover from a sleep mode. This only happens after the latest KDE5 update.
Version-Release number of selected component (if applicable):
Happened after the latest KDE5 update.
Steps to Reproduce:
Power management plugin is not running.
Power management should be running and the sleep recovery shouldn't take a long time to realize.
See the attached images
Links to both images;
1. Can you try from konsole:
and post any output?
2. Does this problem only occur after resuming from sleep or does it happen on a fresh boot/login too?
1. Output from the above command, http://i.imgur.com/G3VHpfl.png
2. This happens from both fresh boot and resuming from sleep.
I wanted the output (if any) displayed in konsole after executing the command, not a screenshot of the UI. sorry if that wasn't clear.
There was no output in the terminal and after waiting for sometime, the UI showed up so I screen grabbed that. I don't know if the command was supposed to do that.
I tried one more time, and I'm not sure if this is the right output that's needed;
QObject::connect: No such signal QDBusAbstractInterface::DeviceAdded(QString)
QObject::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QString)
virtual QStringList Solid::Backends::UPower::UPowerManager::allDevices() error: "org.freedesktop.DBus.Error.TimedOut"
Let me know if I can be of any assistance further.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Thank you for reporting this bug and we are sorry it could not be fixed.