Bug 223295

Application that crashed: kontact
Version of the application: 4.3.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-17-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
When my computer wakes up from sleep (RAM), I get an error message that the connection to the server was lost. I discard the error and continue. Sometime later the message pops up again, and when I discard this time, Kontact crashes. It is the same routine everytime my computer (Thinkpad T60p, kubuntu 9.10, KDE 4.3.4) wakes up from suspension to RAM. 
A possible hint is that one of my IMAP accounts is not checked immediately but only later, and I think the crash occurs, when this IMAP account is being checked for mail... but I also have two other IMAP accounts, and one pop3-account...

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KIO::Slave::deref (this=0xcef110) at ../../kio/kio/slave.cpp:242
#6  0x00007fabe9b48169 in KIO::Slave::gotInput (this=0xcef110) at ../../kio/kio/slave.cpp:335
#7  0x00007fabe9b4a27c in KIO::Slave::qt_metacall (this=0xcef110, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff79524f50) at ./slave.moc:76
#8  0x00007fabeb638ddc in QMetaObject::activate (sender=0xcef5b0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x5cf60) at kernel/qobject.cpp:3113
#9  0x00007fabe9a64ed7 in KIO::ConnectionPrivate::dequeue (this=0xcf0910) at ../../kio/kio/connection.cpp:82
#10 0x00007fabe9a64ffd in KIO::Connection::qt_metacall (this=0xcef5b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x415c3d0) at ./connection.moc:73
#11 0x00007fabeb6330f9 in QObject::event (this=0xcef5b0, e=0x49b0b20) at kernel/qobject.cpp:1111
#12 0x00007fabebf47efc in QApplicationPrivate::notify_helper (this=0x9fa7c0, receiver=0xcef5b0, e=0x49b0b20) at kernel/qapplication.cpp:4056
#13 0x00007fabebf4f1ce in QApplication::notify (this=0x7fff79525910, receiver=0xcef5b0, e=0x49b0b20) at kernel/qapplication.cpp:4021
#14 0x00007fabecb7ee56 in KApplication::notify (this=0x7fff79525910, receiver=0xcef5b0, event=0x49b0b20) at ../../kdeui/kernel/kapplication.cpp:302
#15 0x00007fabeb623c2c in QCoreApplication::notifyInternal (this=0x7fff79525910, receiver=0xcef5b0, event=0x49b0b20) at kernel/qcoreapplication.cpp:610
#16 0x00007fabeb62480a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x9cd080) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x9cd080) at kernel/qcoreapplication.cpp:1247
#18 0x00007fabeb64c533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#19 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#20 0x00007fabe4e9dbce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#21 0x00007fabe4ea1598 in ?? () from /lib/libglib-2.0.so.0
#22 0x00007fabe4ea16c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#23 0x00007fabeb64c1a6 in QEventDispatcherGlib::processEvents (this=0x9cccb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#24 0x00007fabebfdc4be in QGuiEventDispatcherGlib::processEvents (this=0xcef110, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007fabeb622532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#26 0x00007fabeb622904 in QEventLoop::exec (this=0x7fff79525850, flags=) at kernel/qeventloop.cpp:201
#27 0x00007fabeb624ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x0000000000403f47 in _start ()

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

Reported using DrKonqi