Bug 323832

Summary: kded crashes when XRANDR extension is missing
Product: [Plasma] KScreen Reporter: Martin Herkt <lachs0r>
Component: kdedAssignee: Alex Fiestas <afiestas>
Status: RESOLVED DUPLICATE    
Severity: crash CC: dvratil
Priority: NOR    
Version: 1.0.1   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Martin Herkt 2013-08-21 12:16:26 UTC 
…or at least that’s what I think is happening. The only hint I have is strace output, since I couldn’t get gdb to attach properly (--nofork didn’t help), and the fact that removing $libdir/kde4/plugins/kscreen made it work.

Reproducible: Always

Steps to Reproduce:
1. Start kded4 on a system without XRANDR.
Actual Results:  
kded4 crashed.

Expected Results:  
It should have made me a sandwich.

The XRANDR extension is missing on my system because I’m using two NVIDIA GPUs with Xinerama to drive four monitors.

strace output: http://p.srsfckn.biz/show/7/
Comment 1 Daniel Vrátil 2013-08-21 13:00:56 UTC 

*** This bug has been marked as a duplicate of bug 323778 ***
Comment 2 Daniel Vrátil 2013-08-21 13:07:31 UTC 
Git commit 06f1bf76f6f932b9b99cca990ed6d4e661d42740 by Dan Vrátil.
Committed on 21/08/2013 at 12:29.
Pushed by dvratil into branch 'master'.

Initialize member variables in XRandrX11Helper

Prevents showing bogus XRandR version in debug output when XRandR is
not available and fixes a crash when unloading an invalid backend

M  +6    -1    backends/xrandr/xrandrx11helper.cpp
M  +0    -1    backends/xrandr/xrandrx11helper.h

http://commits.kde.org/libkscreen/06f1bf76f6f932b9b99cca990ed6d4e661d42740