Application: kontact (4.4.6)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-25-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
These are two bugs really, but I have a hunch that they are related. 
1. IMAP CONNECTION LOST
I suspend-to-ram and kmail [kontact] was active. I wake up the laptop. Ubuntu reestablishes the wireless connection. This causes kmail to hang/timeout whenever some action is performed requiring imap contact. (the application itself does not freeze; for example, if one clicks on a message, the status indicator on the lower rightremains at 0% or 100% and the message contents never gets displayed/downloaded). This never recovers and kontact needs to be restarted. This brings me to the second issue.
2. KONTACT CRASHES ON STARTUP
When I restart kontact in order to fix the above issue, it crashes (backtrace attached). This crash seems to happen especially after kontact is in a state described above.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fa9af9f7780 (LWP 28977))]

Thread 2 (Thread 0x7fa989461700 (LWP 28999)):
#0  0x00007fa9aca34203 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fa9a57a7009 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fa9a57a745c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007fa9ad1781e6 in QEventDispatcherGlib::processEvents (this=0x1b55f70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007fa9ad14aa02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007fa9ad14adec in QEventLoop::exec (this=0x7fa989460d90, flags=) at kernel/qeventloop.cpp:201
#6  0x00007fa9ad0552fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007fa9ad12a5f8 in QInotifyFileSystemWatcherEngine::run (this=0x22e3c80) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fa9ad05827e in QThreadPrivate::start (arg=0x22e3c80) at thread/qthread_unix.cpp:266
#9  0x00007fa9a7b36971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#10 0x00007fa9aca4092d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa9af9f7780 (LWP 28977)):
[KCrash Handler]
#6  Kontact::MainWindow::activateInitialPluginModule (this=0x1378810) at ../../../kontact/src/mainwindow.cpp:289
#7  0x00000000004043f2 in KontactApp::newInstance (this=0x7fff84b88580) at ../../../kontact/src/main.cpp:149
#8  0x00007fa9ae85b976 in KUniqueApplicationAdaptor::newInstance (this=0x12ad120, asn_id=<value optimized out>, args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:440
#9  0x00007fa9ae85bfb6 in KUniqueApplicationAdaptor::qt_metacall (this=0x12ad120, _c=QMetaObject::InvokeMetaMethod, _id=24926800, _a=0x7fff84b87720) at ./kuniqueapplication_p.moc:81
#10 0x00007fa9ab2150ee in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>) at qdbusintegrator.cpp:919
#11 0x00007fa9ab2163cb in QDBusConnectionPrivate::activateCall (this=<value optimized out>, object=0x12ad120, flags=337, msg=...) at qdbusintegrator.cpp:829
#12 0x00007fa9ab216e65 in QDBusConnectionPrivate::activateObject (this=<value optimized out>, node=<value optimized out>, msg=..., pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1379
#13 0x00007fa9ab217108 in QDBusActivateObjectEvent::placeMetaCall (this=0x15d07c0) at qdbusintegrator.cpp:1493
#14 0x00007fa9ad15dbde in QObject::event (this=0x7fff84b88580, e=0x1378810) at kernel/qobject.cpp:1219
#15 0x00007fa9adb05186 in QApplication::event (this=0x7fff84b88580, e=0x15d07c0) at kernel/qapplication.cpp:2439
#16 0x00007fa9adb01fdc in QApplicationPrivate::notify_helper (this=0x1249360, receiver=0x7fff84b88580, e=0x15d07c0) at kernel/qapplication.cpp:4396
#17 0x00007fa9adb07aed in QApplication::notify (this=0x7fff84b88580, receiver=0x7fff84b88580, e=0x15d07c0) at kernel/qapplication.cpp:4277
#18 0x00007fa9ae854156 in KApplication::notify (this=0x7fff84b88580, receiver=0x7fff84b88580, event=0x15d07c0) at ../../kdeui/kernel/kapplication.cpp:310
#19 0x00007fa9ad14bcdc in QCoreApplication::notifyInternal (this=0x7fff84b88580, receiver=0x7fff84b88580, event=0x15d07c0) at kernel/qcoreapplication.cpp:732
#20 0x00007fa9ad14ec22 in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x1214380) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x1214380) at kernel/qcoreapplication.cpp:1373
#22 0x00007fa9ad178653 in sendPostedEvents (s=0x1242d80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#23 postEventSourceDispatch (s=0x1242d80) at kernel/qeventdispatcher_glib.cpp:277
#24 0x00007fa9a57a3342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x00007fa9a57a72a8 in ?? () from /lib/libglib-2.0.so.0
#26 0x00007fa9a57a745c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00007fa9ad178193 in QEventDispatcherGlib::processEvents (this=0x1213e90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#28 0x00007fa9adbb4a4e in QGuiEventDispatcherGlib::processEvents (this=0x1378810, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007fa9ad14aa02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#30 0x00007fa9ad14adec in QEventLoop::exec (this=0x7fff84b884c0, flags=) at kernel/qeventloop.cpp:201
#31 0x00007fa9ad14eebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#32 0x0000000000403b4e in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:224

This bug may be a duplicate of or related to bug 193514.

Possible duplicates by query: bug 262651, bug 257815, bug 257415, bug 256827, bug 256719.

Reported using DrKonqi