Bug 213525

Application that crashed: kontact
Version of the application: 4.3.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Kontact crashed randomly at start-up. On next start-up, it worked as expected.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  QString (this=0x10) at /usr/include/qt4/QtCore/qstring.h:711
#7  Kontact::Plugin::identifier (this=0x10) at ../../kontactinterfaces/plugin.cpp:97
#8  0x007fd50e in Kontact::MainWindow::activatePluginModule (this=0x9ac37e0) at ../../../kontact/src/mainwindow.cpp:303
#9  0x007fd5c4 in Kontact::MainWindow::setActivePluginModule (this=0x9ac37e0, module=...) at ../../../kontact/src/mainwindow.cpp:281
#10 0x0804bd0f in KontactApp::newInstance (this=0xbffc68d4) at ../../../kontact/src/main.cpp:147
#11 0x00d4f8d0 in KUniqueApplicationAdaptor::newInstance (this=0x9b2f6e8, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:459
#12 0x00d4ffe2 in KUniqueApplicationAdaptor::qt_metacall (this=0x9b2f6e8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbffc5efc) at ./kuniqueapplication_p.moc:75
#13 0x00a6a7b4 in QDBusConnectionPrivate::deliverCall (this=0x9aadc90, object=0x9b2f6e8, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:891
#14 0x00a6b9c5 in QDBusConnectionPrivate::activateCall (this=0x9aadc90, object=0x9b2f6e8, flags=337, msg=...) at qdbusintegrator.cpp:803
#15 0x00a6c234 in QDBusConnectionPrivate::activateObject (this=0x9aadc90, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1347
#16 0x00a6c4da in QDBusActivateObjectEvent::placeMetaCall (this=0xa439e50) at qdbusintegrator.cpp:1464
#17 0x009655fe in QObject::event (this=0xbffc68d4, e=0xa439e50) at kernel/qobject.cpp:1111
#18 0x00954ffb in QCoreApplication::event (this=0xbffc68d4, e=0xa439e50) at kernel/qcoreapplication.cpp:1434
#19 0x0102e9a6 in QApplication::event (this=0xbffc68d4, e=0xa439e50) at kernel/qapplication.cpp:2317
#20 0x01028f54 in QApplicationPrivate::notify_helper (this=0x9abebd0, receiver=0xbffc68d4, e=0xa439e50) at kernel/qapplication.cpp:4056
#21 0x0103067c in QApplication::notify (this=0xbffc68d4, receiver=0xbffc68d4, e=0xa439e50) at kernel/qapplication.cpp:3603
#22 0x00d4814a in KApplication::notify (this=0xbffc68d4, receiver=0xbffc68d4, event=0xa439e50) at ../../kdeui/kernel/kapplication.cpp:302
#23 0x009556cb in QCoreApplication::notifyInternal (this=0xbffc68d4, receiver=0xbffc68d4, event=0xa439e50) at kernel/qcoreapplication.cpp:610
#24 0x009562b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9a95820) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9a95820) at kernel/qcoreapplication.cpp:1247
#26 0x0095647d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#27 0x009803ff in QCoreApplication::sendPostedEvents (s=0x9ab4c10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#28 postEventSourceDispatch (s=0x9ab4c10) at kernel/qeventdispatcher_glib.cpp:210
#29 0x06332e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0x06336720 in ?? () from /lib/libglib-2.0.so.0
#31 0x06336853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0x0098002c in QEventDispatcherGlib::processEvents (this=0x9a959f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#33 0x010c9be5 in QGuiEventDispatcherGlib::processEvents (this=0x9a959f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#34 0x00953c79 in QEventLoop::processEvents (this=0xbffc6834, flags=) at kernel/qeventloop.cpp:149
#35 0x009540ca in QEventLoop::exec (this=0xbffc6834, flags=...) at kernel/qeventloop.cpp:201
#36 0x0095653f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0x01028dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#38 0x0804b4e6 in main (argc=1, argv=0xbffc6af4) at ../../../kontact/src/main.cpp:218

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

Reported using DrKonqi