Bug 212236

Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-1-686-bigmem i686

What I was doing when the application crashed:
I started kontact (which usually works), but instead of opening the window it immediately crashed

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:711
#7  Kontact::Plugin::identifier (this=0x0) at ../../kontactinterfaces/plugin.cpp:97
#8  0xb7fe22b9 in Kontact::MainWindow::activatePluginModule (this=0x8756c90) at ../../../kontact/src/mainwindow.cpp:303
#9  0xb7fe2364 in Kontact::MainWindow::setActivePluginModule (this=0x8756c90, module=...) at ../../../kontact/src/mainwindow.cpp:281
#10 0x0804aac7 in KontactApp::newInstance (this=0xbff6673c) at ../../../kontact/src/main.cpp:147
#11 0xb7cfa3e6 in KUniqueApplicationAdaptor::newInstance (this=0x8727af8, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:459
#12 0xb7cfa482 in KUniqueApplicationAdaptor::qt_metacall (this=0x8727af8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbff65c98) at ./kuniqueapplication_p.moc:75
#13 0xb6113be5 in QDBusConnectionPrivate::deliverCall (this=0x8611d10, object=0x8727af8, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:891
#14 0xb6114e31 in QDBusConnectionPrivate::activateCall (this=0x8611d10, object=0x8727af8, flags=337, msg=...) at qdbusintegrator.cpp:803
#15 0xb6115254 in QDBusConnectionPrivate::activateObject (this=0x8611d10, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1370
#16 0xb611573a in QDBusActivateObjectEvent::placeMetaCall (this=0xab08870) at qdbusintegrator.cpp:1464
#17 0xb78015e0 in QObject::event (this=0xbff6673c, e=0xab08870) at kernel/qobject.cpp:1110
#18 0xb77f0b8b in QCoreApplication::event (this=0xbff6673c, e=0xab08870) at kernel/qcoreapplication.cpp:1434
#19 0xb6e362c9 in QApplication::event (this=0xbff6673c, e=0xab08870) at kernel/qapplication.cpp:2317
#20 0xb6e30a94 in QApplicationPrivate::notify_helper (this=0x8619518, receiver=0xbff6673c, e=0xab08870) at kernel/qapplication.cpp:4065
#21 0xb6e38bee in QApplication::notify (this=0xbff6673c, receiver=0xbff6673c, e=0xab08870) at kernel/qapplication.cpp:3605
#22 0xb7cf30fd in KApplication::notify (this=0xbff6673c, receiver=0xbff6673c, event=0xab08870) at ../../kdeui/kernel/kapplication.cpp:302
#23 0xb77f11eb in QCoreApplication::notifyInternal (this=0xbff6673c, receiver=0xbff6673c, event=0xab08870) at kernel/qcoreapplication.cpp:610
#24 0xb77f1e2e in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x86001e0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x86001e0) at kernel/qcoreapplication.cpp:1247
#26 0xb77f200d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#27 0xb781c4cf in QCoreApplication::sendPostedEvents (s=0x861be40) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#28 postEventSourceDispatch (s=0x861be40) at kernel/qeventdispatcher_glib.cpp:276
#29 0xb5272e98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0xb5276623 in ?? () from /lib/libglib-2.0.so.0
#31 0xb52767a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0xb781c041 in QEventDispatcherGlib::processEvents (this=0x86183d0, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#33 0xb6ed0305 in QGuiEventDispatcherGlib::processEvents (this=0x86183d0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#34 0xb77ef83a in QEventLoop::processEvents (this=0xbff665b0, flags=...) at kernel/qeventloop.cpp:149
#35 0xb77efc82 in QEventLoop::exec (this=0xbff665b0, flags=...) at kernel/qeventloop.cpp:201
#36 0xb77f20d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0xb6e30917 in QApplication::exec () at kernel/qapplication.cpp:3525
#38 0x0804bd40 in main (argc=1, argv=0xbff66954) at ../../../kontact/src/main.cpp:218

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

Reported using DrKonqi