Bug 1282324

Summary:	powerdevil 5.4.3-1 prevents kded5 from starting
Product:	[Fedora] Fedora	Reporter:	larsh
Component:	powerdevil	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	22	CC:	enrico.tagliavini, jgrulich, jwakely, larsh, ltinkl, mail, me, rdieter, than
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-17 14:59:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description larsh 2015-11-16 06:10:41 UTC

Description of problem:
After the upgrade to powerdevil 5.4.3-1, kded5 will no longer start.

This has all kinds of other effects. The most prominent for me was that kmix goes into an endless loop upon starting, because kded wasn't started.
Volume and brightness controls also stopped working.

I eventually tracked it down to the new version of powerdevil.
After a downgrade to powerdevil-5.3.0-1 everything is fine again.

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

How reproducible:
always

Steps to Reproduce:
1. simply start KDE
2. notice kded5 is not running
3. logs in .xsession-errors indicate a shared library version issue with powerdevil (see below)

Actual results:
kde5 not running

Expected results:
kde5 running

Additional info:
The root of the problem is this (from .xsession-errors):
kded5 [kdeinit5]: symbol lookup error: /lib64/libpowerdevilcore.so.2: undefined symbol: _ZNK11QMetaObject10Connection18isConnected_helperEv

Comment 1 larsh 2015-11-16 06:12:54 UTC

Above should read:

Actual results:
kded5 not running

Expected results:
kded5 running

Comment 2 Jonathan Wakely 2015-11-17 12:57:11 UTC

dup of Bug 1282261 and Bug 1282594

Comment 3 Rex Dieter 2015-11-17 14:59:07 UTC

Thanks

*** This bug has been marked as a duplicate of bug 1282261 ***