Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1282594 - /lib64/libpowerdevilcore.so.2: undefined symbol
Summary: /lib64/libpowerdevilcore.so.2: undefined symbol
Keywords:
Status: CLOSED DUPLICATE of bug 1282261
Alias: None
Product: Fedora
Classification: Fedora
Component: powerdevil
Version: 22
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-16 20:32 UTC by Nick Strugnell
Modified: 2015-11-17 14:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-17 14:58:57 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Nick Strugnell 2015-11-16 20:32:15 UTC 
Description of problem:

After latest update, kded5 was constantly respawning. I tracked this down to an error in powerdevil. kded5 trace is:

kded5: symbol lookup error: /lib64/libpowerdevilcore.so.2: undefined symbol: _ZNK11QMetaObject10Connection18isConnected_helperEv



Version-Release number of selected component (if applicable):

powerdevil-5.4.3-1.fc22.x86_64
kf5-kded-5.15.0-1.fc22.x86_64

How reproducible:

always.


Steps to Reproduce:
1. Enable power management in Plasma
2. 
3.

Actual results:
kded5 constantly respawns and important system services such as NetworkManager and kdewallet are unavailable.


Expected results:
kded5 should run as normal.


Additional info:
Workaround:
cd /usr/share/kservices5/kded ; mv powerdevil.desktop powerdevil.desktop-disabled ; reboot
Comment 1 Jonathan Wakely 2015-11-17 12:56:07 UTC 
seems to be a dup of Bug 1282261 and Bug 1282324
Comment 2 Rex Dieter 2015-11-17 14:58:57 UTC 
Thanks!

*** This bug has been marked as a duplicate of bug 1282261 ***
Note You need to log in before you can comment on or make changes to this bug.