[kdelibs] [Bug 331784] New: Kded4 crashes when RANDR is disabled.

[Neil Whelchel]

https://bugs.kde.org/show_bug.cgi?id=331784

            Bug ID: 331784
           Summary: Kded4 crashes when RANDR is disabled.
    Classification: Unclassified
           Product: kdelibs
           Version: unspecified
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: kded
          Assignee: unassigned-bugs at kde.org
          Reporter: neil.whelchel at gmail.com

I am using kded4 version 4.12.3 (Ubuntu 14.04).
When I disable RANDR, kded4 crashes on startup. When I enable RANDR, kded4
works as expected.

My configuration requires that I have RANDR disabled, I have to use Xinerama
due to multiple monitors in portrait orientation (90 degrees rotation).

Reproducible: Always

Steps to Reproduce:
1. Disable RANDR.
2. Start DM.
3. Log in.

Actual Results:  
In the process of logging into KDE kded4 crashes.


I marked this is major because it blocks me from using my computer with more
than one monitor.

STDOUT/STDERR when ran from the command prompt:
kded4 
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.                                                      
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.                                                      
kded(8625) ColorD::connectToDisplay: RandR extension missing                    
kded(8625) ColorD::ColorD: Failed to connect to DISPLAY and get the needed
resources                                                                       
Xlib:  extension "RANDR" missing on display ":0".                               
Xlib:  extension "RANDR" missing on display ":0".                               
Can't get XRandR version                                                        
kded4: Fatal IO error: client killed                                            
kded(8624): Communication problem with  "kded" , it probably crashed.           
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" "

-- 
You are receiving this mail because:
You are the assignee for the bug.