Application that crashed: kontact Version of the application: 4.3.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.30-1-686 i686 Distribution: Debian GNU/Linux unstable (sid) What I was doing when the application crashed: I typed in the first few letters of an e-mail address to wait for Microsoft Exchange ldap lookup to finish off the address. Instead it crashed. Happens consistently. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 QListWidgetItem::text (this=0x9273780, adrs=...) at /usr/include/qt4/QtGui/qlistwidget.h:90 #7 KPIM::AddresseeLineEdit::slotLDAPSearchData (this=0x9273780, adrs=...) at ../../libkdepim/addresseelineedit.cpp:820 #8 0xb7e3038a in KPIM::AddresseeLineEdit::qt_metacall (this=0x9273780, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfd2160c) at ./addresseelineedit.moc:95 #9 0xb131438a in KMLineEdit::qt_metacall (this=0x9273780, _c=QMetaObject::InvokeMetaMethod, _id=84, _a=0xbfd2160c) at ./kmlineeditspell.moc:68 #10 0xb1388f3a in RecipientLineEdit::qt_metacall (this=0x9273780, _c=QMetaObject::InvokeMetaMethod, _id=84, _a=0xbfd2160c) at ./recipientseditor.moc:123 #11 0xb7702b33 in QMetaObject::activate (sender=0x91b9d50, from_signal_index=5, to_signal_index=5, argv=0xbfd2160c) at kernel/qobject.cpp:3112 #12 0xb7703782 in QMetaObject::activate (sender=0x91b9d50, m=0xb7eb4248, local_signal_index=1, argv=0xbfd2160c) at kernel/qobject.cpp:3186 #13 0xb7e33613 in KPIM::LdapSearch::searchData (this=0x91b9d50, _t1=...) at ./ldapclient.moc:205 #14 0xb7e373af in KPIM::LdapSearch::slotDataTimer (this=0x91b9d50) at ../../libkdepim/ldapclient.cpp:465 #15 0xb7e3a3b3 in KPIM::LdapSearch::qt_metacall (this=0x91b9d50, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfd216f8) at ./ldapclient.moc:185 #16 0xb7702b33 in QMetaObject::activate (sender=0x91b9d60, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #17 0xb7703782 in QMetaObject::activate (sender=0x91b9d60, m=0xb77dede4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #18 0xb773e177 in QTimer::timeout (this=0x91b9d60) at .moc/release-shared/moc_qtimer.cpp:128 #19 0xb7708e9e in QTimer::timerEvent (this=0x91b9d60, e=0xbfd21b7c) at kernel/qtimer.cpp:261 #20 0xb76fdbcf in QObject::event (this=0x91b9d60, e=0xbfd21b7c) at kernel/qobject.cpp:1074 #21 0xb6d2d814 in QApplicationPrivate::notify_helper (this=0x8cef2a8, receiver=0x91b9d60, e=0xbfd21b7c) at kernel/qapplication.cpp:4056 #22 0xb6d3597e in QApplication::notify (this=0xbfd21f2c, receiver=0x91b9d60, e=0xbfd21b7c) at kernel/qapplication.cpp:3603 #23 0xb7bee4ad in KApplication::notify (this=0xbfd21f2c, receiver=0x91b9d60, event=0xbfd21b7c) at ../../kdeui/kernel/kapplication.cpp:302 #24 0xb76ed9cb in QCoreApplication::notifyInternal (this=0xbfd21f2c, receiver=0x91b9d60, event=0xbfd21b7c) at kernel/qcoreapplication.cpp:610 #25 0xb771c361 in QCoreApplication::sendEvent (this=0x8ce939c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #26 QTimerInfoList::activateTimers (this=0x8ce939c) at kernel/qeventdispatcher_unix.cpp:572 #27 0xb7718900 in timerSourceDispatch (source=0x8ce9368) at kernel/qeventdispatcher_glib.cpp:165 #28 0xb51474b8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #29 0xb514aa13 in ?? () from /usr/lib/libglib-2.0.so.0 #30 0xb514ab98 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #31 0xb7718858 in QEventDispatcherGlib::processEvents (this=0x8cc86e8, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #32 0xb6dccfd5 in QGuiEventDispatcherGlib::processEvents (this=0x8cc86e8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #33 0xb76ec01a in QEventLoop::processEvents (this=0xbfd21da0, flags=...) at kernel/qeventloop.cpp:149 #34 0xb76ec462 in QEventLoop::exec (this=0xbfd21da0, flags=...) at kernel/qeventloop.cpp:201 #35 0xb76ee8b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #36 0xb6d2d697 in QApplication::exec () at kernel/qapplication.cpp:3525 #37 0x0804bd40 in main (argc=1, argv=0xbfd22124) at ../../../kontact/src/main.cpp:218 This bug may be a duplicate of or related to bug 206245 Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 206024 ***