Version: (using Devel) OS: Linux Installed from: Compiled sources Toying around with multiple desktop settings, I managed to create a setup, with which the "Display" settings can't be opened. Randr is mentioned in xorg.conf, but auto-disabled on X startup. Application: System Settings (systemsettings), signal SIGSEGV 0x00007fd708d28fd0 in __nanosleep_nocancel () from /lib/libc.so.6 Thread 1 (Thread 0x7fd70c86d750 (LWP 19589)): [KCrash Handler] #5 0x00007fd70195231c in RandRDisplay::isValid (this=0x0) at /home/e/kde/src/KDE/kdebase/workspace/kcontrol/randr/randrdisplay.cpp:112 #6 0x00007fd70194e102 in LegacyRandRConfig::load (this=0x620740) at /home/e/kde/src/KDE/kdebase/workspace/kcontrol/randr/legacyrandrconfig.cpp:67 #7 0x00007fd70194bd86 in KRandRModule::load (this=0x120d690) at /home/e/kde/src/KDE/kdebase/workspace/kcontrol/randr/krandrmodule.cpp:106 #8 0x00007fd70b73b0b3 in KCModule::qt_metacall (this=0x120d690, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x12940f0) at /home/e/kde/build/kdelibs/kdeui/kcmodule.moc:78 #9 0x00007fd70194bc21 in KRandRModule::qt_metacall (this=0x120d690, _c=QMetaObject::InvokeMetaMethod, _id=29, _a=0x12940f0) at /home/e/kde/build/kdebase/workspace/kcontrol/randr/krandrmodule.moc:58 #10 0x00007fd70aa6be3b in QMetaCallEvent::placeMetaCall (this=0x1298170, object=0x120d690) at kernel/qobject.cpp:484 #11 0x00007fd70aa70488 in QObject::event (this=0x120d690, e=0x1298170) at kernel/qobject.cpp:1110 #12 0x00007fd7099d98e1 in QWidget::event (this=0x120d690, event=0x1298170) at kernel/qwidget.cpp:7908 #13 0x00007fd70997be73 in QApplicationPrivate::notify_helper (this=0xf24f90, receiver=0x120d690, e=0x1298170) at kernel/qapplication.cpp:4051 #14 0x00007fd70997dd7a in QApplication::notify (this=0x7fff149ae820, receiver=0x120d690, e=0x1298170) at kernel/qapplication.cpp:4016 #15 0x00007fd70b6919a7 in KApplication::notify (this=0x7fff149ae820, receiver=0x120d690, event=0x1298170) at /home/e/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307 #16 0x00007fd70aa5c303 in QCoreApplication::notifyInternal (this=0x7fff149ae820, receiver=0x120d690, event=0x1298170) at kernel/qcoreapplication.cpp:593 #17 0x00007fd70aa5fdc7 in QCoreApplication::sendEvent (receiver=0x120d690, event=0x1298170) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:208 #18 0x00007fd70aa5c855 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xf0eef0) at kernel/qcoreapplication.cpp:1231 #19 0x00007fd70aa5ca2c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1127 #20 0x00007fd70aa8b96b in QCoreApplication::sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #21 0x00007fd70aa8abac in postEventSourceDispatch (s=0xf27980) at kernel/qeventdispatcher_glib.cpp:204 #22 0x00007fd7061a1aa2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0x00007fd7061a521d in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #24 0x00007fd7061a53db in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0x00007fd70aa89eee in QEventDispatcherGlib::processEvents (this=0xf14de0, flags={i = 345695840}) at kernel/qeventdispatcher_glib.cpp:318 #26 0x00007fd709a2300b in QGuiEventDispatcherGlib::processEvents (this=0xf14de0, flags={i = 345695936}) at kernel/qguieventdispatcher_glib.cpp:197 #27 0x00007fd70aa59587 in QEventLoop::processEvents (this=0x7fff149ae780, flags={i = 345696032}) at kernel/qeventloop.cpp:144 #28 0x00007fd70aa59794 in QEventLoop::exec (this=0x7fff149ae780, flags={i = 345696144}) at kernel/qeventloop.cpp:191 #29 0x00007fd70aa5cb4e in QCoreApplication::exec () at kernel/qcoreapplication.cpp:875 #30 0x00007fd70997bbd0 in QApplication::exec () at kernel/qapplication.cpp:3526 #31 0x0000000000412ab9 in main (argc=1, argv=0x7fff149aeb38) at /home/e/kde/src/KDE/kdebase/workspace/systemsettings/main.cpp:67
Created attachment 31727 [details] xorg.conf
Thanks :), this is related to bug 157549 and bug 169470 Also, what KDE version (or SVN revision/branch) are you using ?
Can't say the exactly exact revision, but everything was a fairly recent trunk, as of 2009-03-01-ish, or even from the same day.
*** This bug has been marked as a duplicate of bug 192129 ***