Application that crashed: systemsettings
Version of the application: 1.0
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.26 x86_64
Distribution: Debian GNU/Linux testing (squeeze)

What I was doing when the application crashed:
After some fuirther fooling around, i was able to ascertain that any attempt ot access the screensaver control page invariably causes a crash.

Thank you very much for your attention.


 -- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f23d6846210 in XVisualIDFromVisual () from /usr/lib/libX11.so.6
#6  0x00007f23d8cd89a4 in qt_x11_getX11InfoForWindow (xinfo=0x2b48218, att=...) at kernel/qwidget_x11.cpp:2896
#7  0x00007f23d8cd8a30 in qt_x11_getX11InfoForWindow (xinfo=0x0, a=<value optimized out>) at kernel/qwidget_x11.cpp:400
#8  0x00007f23d8cdd2ac in QWidgetPrivate::create_sys (this=0x2b48080, window=75501881, initializeWindow=false, destroyOldWindow=true) at kernel/qwidget_x11.cpp:545
#9  0x00007f23d8ca48fe in QWidget::create (this=0x2b3efd0, window=75501881, initializeWindow=80, destroyOldWindow=true) at kernel/qwidget.cpp:1253
#10 0x00007f23bd11d3fa in KSWidget (this=0x2b3efd0, parent=<value optimized out>, wf=<value optimized out>) at ../../../kcontrol/screensaver/kswidget.cpp:66
#11 0x00007f23bd10fa11 in KSSMonitor (this=0x22e4130) at ../../../kcontrol/screensaver/kssmonitor.h:9
#12 KScreenSaver::slotPreviewExited (this=0x22e4130) at ../../../kcontrol/screensaver/scrnsave.cpp:607
#13 0x00007f23bd1116be in KScreenSaver::findSavers (this=0x22e4130) at ../../../kcontrol/screensaver/scrnsave.cpp:575
#14 0x00007f23bd111e60 in KScreenSaver::qt_metacall (this=0x22e4130, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffe2333010) at ./scrnsave.moc:98
#15 0x00007f23d80a2682 in QMetaObject::activate (sender=0x22cacd0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1) at kernel/qobject.cpp:3112
#16 0x00007f23d809cbf3 in QObject::event (this=0x22cacd0, e=0x0) at kernel/qobject.cpp:1074
#17 0x00007f23d8c5280d in QApplicationPrivate::notify_helper (this=0x2255370, receiver=0x22cacd0, e=0x7fffe23336c0) at kernel/qapplication.cpp:4056
#18 0x00007f23d8c5a86a in QApplication::notify (this=0x7fffe2333a00, receiver=0x22cacd0, e=0x7fffe23336c0) at kernel/qapplication.cpp:4021
#19 0x00007f23d98ac43b in KApplication::notify (this=0x7fffe2333a00, receiver=0x22cacd0, event=0x7fffe23336c0) at ../../kdeui/kernel/kapplication.cpp:302
#20 0x00007f23d808d51c in QCoreApplication::notifyInternal (this=0x7fffe2333a00, receiver=0x22cacd0, event=0x7fffe23336c0) at kernel/qcoreapplication.cpp:610
#21 0x00007f23d80b9826 in QCoreApplication::sendEvent (this=0x2264d00) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#22 QTimerInfoList::activateTimers (this=0x2264d00) at kernel/qeventdispatcher_unix.cpp:572
#23 0x00007f23d80b5c9d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#24 0x00007f23d4f8312a in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x00007f23d4f86988 in ?? () from /lib/libglib-2.0.so.0
#26 0x00007f23d4f86b3c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00007f23d80b5bff in QEventDispatcherGlib::processEvents (this=0x2231490, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#28 0x00007f23d8ce964f in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#29 0x00007f23d808bde2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#30 0x00007f23d808c1b4 in QEventLoop::exec (this=0x7fffe2333970, flags=...) at kernel/qeventloop.cpp:201
#31 0x00007f23d808e424 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#32 0x000000000040cada in main (argc=1, argv=0x7fffe2333cb8) at ../../../systemsettings/app/main.cpp:51

This bug may be a duplicate of or related to bug 209817

Reported using DrKonqi