Application that crashed: kmail Version of the application: 1.12.4 KDE Version: 4.3.5 (KDE 4.3.5) Qt Version: 4.5.2 Operating System: Linux 2.6.31-20-generic-pae i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Crash after failing to connect to an Imap Server kmail version 4.3.5-0ubuntu1~karmic1 (i386) Running on kubuntu 2.6.31-20-generic-pae #57-Ubuntu SMP Mon Feb 8 10:23:59 UTC 2010 i686 GNU/Linux -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 KIO::Slave::deref (this=0xc1acd40) at ../../kio/kio/slave.cpp:243 #7 0xb4bfcec6 in KIO::Slave::gotInput (this=0xc1acd40) at ../../kio/kio/slave.cpp:336 #8 0xb4bff393 in KIO::Slave::qt_metacall (this=0xc1acd40, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbf80336c) at ./slave.moc:76 #9 0xb5f72263 in QMetaObject::activate (sender=0xc0aeed0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #10 0xb5f72ec2 in QMetaObject::activate (sender=0xc0aeed0, m=0xb4cef8a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #11 0xb4b06227 in KIO::Connection::readyRead (this=0xc0aeed0) at ./connection.moc:86 #12 0xb4b07fee in KIO::ConnectionPrivate::dequeue (this=0xc0aeee0) at ../../kio/kio/connection.cpp:82 #13 0xb4b0811e in KIO::Connection::qt_metacall (this=0xc0aeed0, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xc5f5048) at ./connection.moc:73 #14 0xb5f6af0b in QMetaCallEvent::placeMetaCall (this=0xc548470, object=0xc0aeed0) at kernel/qobject.cpp:477 #15 0xb5f6c5fe in QObject::event (this=0xc0aeed0, e=0xc548470) at kernel/qobject.cpp:1111 #16 0xb6170f54 in QApplicationPrivate::notify_helper (this=0x9355af8, receiver=0xc0aeed0, e=0xc548470) at kernel/qapplication.cpp:4056 #17 0xb617867c in QApplication::notify (this=0xbf803ca0, receiver=0xc0aeed0, e=0xc548470) at kernel/qapplication.cpp:3603 #18 0xb76d325a in KApplication::notify (this=0xbf803ca0, receiver=0xc0aeed0, event=0xc548470) at ../../kdeui/kernel/kapplication.cpp:302 #19 0xb5f5c6cb in QCoreApplication::notifyInternal (this=0xbf803ca0, receiver=0xc0aeed0, event=0xc548470) at kernel/qcoreapplication.cpp:610 #20 0xb5f5d2b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9326fa8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9326fa8) at kernel/qcoreapplication.cpp:1247 #22 0xb5f5d47d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #23 0xb5f873ff in QCoreApplication::sendPostedEvents (s=0x934f510) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #24 postEventSourceDispatch (s=0x934f510) at kernel/qeventdispatcher_glib.cpp:210 #25 0xb3efae88 in g_main_dispatch (context=0x934f490) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960 #26 IA__g_main_context_dispatch (context=0x934f490) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513 #27 0xb3efe730 in g_main_context_iterate (context=0x934f490, block=<value optimized out>, dispatch=1, self=0x934c538) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591 #28 0xb3efe863 in IA__g_main_context_iteration (context=0x934f490, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654 #29 0xb5f8702c in QEventDispatcherGlib::processEvents (this=0x9327180, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #30 0xb6211be5 in QGuiEventDispatcherGlib::processEvents (this=0x9327180, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #31 0xb5f5ac79 in QEventLoop::processEvents (this=0xbf803b64, flags=) at kernel/qeventloop.cpp:149 #32 0xb5f5b0ca in QEventLoop::exec (this=0xbf803b64, flags=...) at kernel/qeventloop.cpp:201 #33 0xb5f5d53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #34 0xb6170dd7 in QApplication::exec () at kernel/qapplication.cpp:3525 #35 0x0804a702 in main (argc=3, argv=0xbf803e54) at ../../kmail/main.cpp:146 This bug may be a duplicate of or related to bug 200788 Reported using DrKonqi
This is reported at bug 191589, and fixed in KDE SC 4.4 Regards *** This bug has been marked as a duplicate of bug 191589 ***