Bug 206673

Summary: Kontact crashed because kmail got a misstake while geting Imap
Product: [Applications] kontact Reporter: Jonathan Kolberg <j_kolberg11>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jonathan Kolberg 2009-09-07 21:15:21 UTC
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.28-15-generic i686
Distribution: Ubuntu 9.04

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KIO::Slave::deref (this=0x95d57b8) at /build/buildd/kde4libs-4.3.1/kio/kio/slave.cpp:242
#7  0xb6f80b3c in KIO::Slave::gotInput (this=0x95d57b8) at /build/buildd/kde4libs-4.3.1/kio/kio/slave.cpp:335
#8  0xb6f82fc3 in KIO::Slave::qt_metacall (this=0x95d57b8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe38988) at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/slave.moc:76
#9  0xb5ba31b8 in QMetaObject::activate (sender=0x93e79d8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#10 0xb5ba3e42 in QMetaObject::activate (sender=0x93e79d8, m=0xb706e880, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#11 0xb6e8c697 in KIO::Connection::readyRead (this=0x93e79d8) at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/connection.moc:86
#12 0xb6e8e003 in KIO::ConnectionPrivate::dequeue (this=0x97df790) at /build/buildd/kde4libs-4.3.1/kio/kio/connection.cpp:82
#13 0xb6e8e3e6 in KIO::Connection::qt_metacall (this=0x93e79d8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x9e8d460) at /build/buildd/kde4libs-4.3.1/obj-i486-linux-gnu/kio/connection.moc:73
#14 0xb5b9c8cb in QMetaCallEvent::placeMetaCall (this=0x9ed8538, object=0x93e79d8) at kernel/qobject.cpp:477
#15 0xb5b9e3b0 in QObject::event (this=0x93e79d8, e=0x9ed8538) at kernel/qobject.cpp:1111
#16 0xb6050d3c in QApplicationPrivate::notify_helper (this=0x86d54a8, receiver=0x93e79d8, e=0x9ed8538) at kernel/qapplication.cpp:4056
#17 0xb605903e in QApplication::notify (this=0xbfe39148, receiver=0x93e79d8, e=0x9ed8538) at kernel/qapplication.cpp:3603
#18 0xb6c4a85d in KApplication::notify (this=0xbfe39148, receiver=0x93e79d8, event=0x9ed8538) at /build/buildd/kde4libs-4.3.1/kdeui/kernel/kapplication.cpp:302
#19 0xb5b8dbcb in QCoreApplication::notifyInternal (this=0xbfe39148, receiver=0x93e79d8, event=0x9ed8538) at kernel/qcoreapplication.cpp:610
#20 0xb5b8e825 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x86a1440) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 0xb5b8ea1d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#22 0xb5bb96af in postEventSourceDispatch (s=0x86cbd90) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#23 0xb4c5eb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb4c620eb in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb4c62268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb5bb92f8 in QEventDispatcherGlib::processEvents (this=0x86a1028, flags={i = -1075605480}) at kernel/qeventdispatcher_glib.cpp:327
#27 0xb60f2a75 in QGuiEventDispatcherGlib::processEvents (this=0x86a1028, flags={i = -1075605432}) at kernel/qguieventdispatcher_glib.cpp:202
#28 0xb5b8c1fa in QEventLoop::processEvents (this=0xbfe390c0, flags={i = -1075605368}) at kernel/qeventloop.cpp:149
#29 0xb5b8c642 in QEventLoop::exec (this=0xbfe390c0, flags={i = -1075605304}) at kernel/qeventloop.cpp:201
#30 0xb5b8eae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#31 0xb6050bb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#32 0x0804bfef in _start ()

Reported using DrKonqi
Comment 1 Christophe Marin 2009-09-07 21:19:37 UTC

*** This bug has been marked as a duplicate of bug 191589 ***