Application: kontact (4.4.8) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.2 Operating System: Linux 2.6.32-27-generic i686 Distribution: Ubuntu 10.04.1 LTS -- Information about the crash: Kontact decided to crash on me after I opened an E-mail but had since abandoned the window. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb7801990 (LWP 26248))] Thread 2 (Thread 0xb27e2b70 (LWP 26357)): #0 0x00489ba9 in pthread_mutex_lock (mutex=0x95151f4) at forward.c:182 #1 0x01978b03 in g_main_context_prepare () from /lib/libglib-2.0.so.0 #2 0x01978ee9 in ?? () from /lib/libglib-2.0.so.0 #3 0x019794b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #4 0x0114f60f in QEventDispatcherGlib::processEvents (this=0x9000bd0, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #5 0x01122059 in QEventLoop::processEvents (this=0xb27e2270, flags=) at kernel/qeventloop.cpp:149 #6 0x011224aa in QEventLoop::exec (this=0xb27e2270, flags=...) at kernel/qeventloop.cpp:201 #7 0x0101e5a8 in QThread::exec (this=0x8df7e28) at thread/qthread.cpp:487 #8 0x01101c1b in QInotifyFileSystemWatcherEngine::run (this=0x8df7e28) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x0102132e in QThreadPrivate::start (arg=0x8df7e28) at thread/qthread_unix.cpp:248 #10 0x0075896e in start_thread (arg=0xb27e2b70) at pthread_create.c:300 #11 0x0047ca4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb7801990 (LWP 26248)): [KCrash Handler] #6 0x0ada6e17 in ?? () #7 0xb46cf6c2 in KMReplyToAllCommand::qt_metacall (this=0xad58bc0, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfa4233c) at ./kmcommands.moc:1093 #8 0x01128c9a in QMetaObject::metacall (object=0xad58bc0, cl=182087192, idx=181767104, argv=0x1) at kernel/qmetaobject.cpp:237 #9 0x011373d5 in QMetaObject::activate (sender=0xacab5f0, m=0x1236188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293 #10 0x0113efe7 in QSingleShotTimer::timeout (this=0xacab5f0) at .moc/release-shared/qtimer.moc:82 #11 0x0113f0fc in QSingleShotTimer::timerEvent (this=0xacab5f0) at kernel/qtimer.cpp:308 #12 0x01134254 in QObject::event (this=0xacab5f0, e=0xacf1f68) at kernel/qobject.cpp:1212 #13 0x01b864dc in QApplicationPrivate::notify_helper (this=0x861a660, receiver=0xacab5f0, e=0xbfa42870) at kernel/qapplication.cpp:4300 #14 0x01b8d05e in QApplication::notify (this=0xbfa42bd4, receiver=0xacab5f0, e=0xbfa42870) at kernel/qapplication.cpp:3704 #15 0x00b0240a in KApplication::notify (this=0xbfa42bd4, receiver=0xacab5f0, event=0xbfa42870) at ../../kdeui/kernel/kapplication.cpp:302 #16 0x01123a3b in QCoreApplication::notifyInternal (this=0xbfa42bd4, receiver=0xacab5f0, event=0xbfa42870) at kernel/qcoreapplication.cpp:704 #17 0x01152d66 in QCoreApplication::sendEvent (this=0x8622b34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #18 QTimerInfoList::activateTimers (this=0x8622b34) at kernel/qeventdispatcher_unix.cpp:603 #19 0x0114f8e4 in timerSourceDispatch (source=0x8622b00) at kernel/qeventdispatcher_glib.cpp:184 #20 0x019755e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #21 0x019792d8 in ?? () from /lib/libglib-2.0.so.0 #22 0x019794b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #23 0x0114f5d5 in QEventDispatcherGlib::processEvents (this=0x85ef588, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #24 0x01c46135 in QGuiEventDispatcherGlib::processEvents (this=0x85ef588, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #25 0x01122059 in QEventLoop::processEvents (this=0xbfa42b34, flags=) at kernel/qeventloop.cpp:149 #26 0x011224aa in QEventLoop::exec (this=0xbfa42b34, flags=...) at kernel/qeventloop.cpp:201 #27 0x0112669f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #28 0x01b86577 in QApplication::exec () at kernel/qapplication.cpp:3579 #29 0x0804b472 in main (argc=1, argv=0xbfa42df4) at ../../../kontact/src/main.cpp:224 This bug may be a duplicate of or related to bug 176845. Possible duplicates by query: bug 252022, bug 244430, bug 242998, bug 241404. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 176845 ***