Application that crashed: kontact
Version of the application: 4.3.5
KDE Version: 4.3.5 (KDE 4.3.5) "release 3"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.12-0.1-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
Closed Kontact
Restarted Kontact
Seg fault on restart...
Checking running processes before restarting shows that kontact process is still running after closing application.
When restarting, I'm guessing there is a conflict between already open process and newly started process.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  Kontact::MainWindow::activatePluginModule (this=0x6430a0) at /usr/src/debug/kdepim-4.3.5/kontact/src/mainwindow.cpp:303
#6  0x0000000000404792 in KontactApp::newInstance (this=0x7fffd9f5ca50) at /usr/src/debug/kdepim-4.3.5/kontact/src/main.cpp:147
#7  0x00007ff31fc25d36 in KUniqueApplicationAdaptor::newInstance (this=0x77a760, asn_id=<value optimized out>, args=...) at /usr/src/debug/kdelibs-4.3.5/kdeui/kernel/kuniqueapplication.cpp:459
#8  0x00007ff31fc26326 in KUniqueApplicationAdaptor::qt_metacall (this=0x77a760, _c=InvokeMetaMethod, _id=10170656, _a=0x7fffd9f5bd80)
    at /usr/src/debug/kdelibs-4.3.5/build/kdeui/kuniqueapplication_p.moc:75
#9  0x00007ff31c873b78 in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=<value optimized out>, 
    slotIdx=<value optimized out>) at qdbusintegrator.cpp:891
#10 0x00007ff31c8749b3 in QDBusConnectionPrivate::activateCall (this=<value optimized out>, object=0x77a760, flags=337, msg=...) at qdbusintegrator.cpp:803
#11 0x00007ff31c875237 in QDBusConnectionPrivate::activateObject (this=<value optimized out>, node=..., msg=<value optimized out>, pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1347
#12 0x00007ff31c8754b8 in QDBusActivateObjectEvent::placeMetaCall (this=0x1687ea0) at qdbusintegrator.cpp:1464
#13 0x00007ff31f2b02d9 in QObject::event (this=0x7fffd9f5ca50, e=0x1687ea0) at kernel/qobject.cpp:1111
#14 0x00007ff31e775efd in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007ff31e76c2ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007ff31e77357e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007ff31fc1f016 in KApplication::notify (this=0x7fffd9f5ca50, receiver=0x7fffd9f5ca50, event=0x1687ea0) at /usr/src/debug/kdelibs-4.3.5/kdeui/kernel/kapplication.cpp:302
#18 0x00007ff31f2a0ddc in QCoreApplication::notifyInternal (this=0x7fffd9f5ca50, receiver=0x7fffd9f5ca50, event=0x1687ea0) at kernel/qcoreapplication.cpp:610
#19 0x00007ff31f2a19ea in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#20 QCoreApplicationPrivate::sendPostedEvents (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.cpp:1247
#21 0x00007ff31f2c9803 in sendPostedEvents () at kernel/qcoreapplication.h:218
#22 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:276
#23 0x00007ff317e9edee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#24 0x00007ff317ea27b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#25 0x00007ff317ea28e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#26 0x00007ff31f2c93a3 in QEventDispatcherGlib::processEvents (this=0x60ee60, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#27 0x00007ff31e7ff31e in ?? () from /usr/lib64/libQtGui.so.4
#28 0x00007ff31f29f712 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#29 0x00007ff31f29fae4 in QEventLoop::exec (this=0x7fffd9f5c990, flags=) at kernel/qeventloop.cpp:201
#30 0x00007ff31f2a1c99 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#31 0x0000000000403f67 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.3.5/kontact/src/main.cpp:218

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

Reported using DrKonqi