Application: kontact (4.14.10) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-42-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Wanted to re-send a message and clicked on a deleted attachement. The crash does not seem to be reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f924d72c800 (LWP 2627))] Thread 4 (Thread 0x7f922f665700 (LWP 2628)): #0 0x00007f9244c7a03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x00007f9248446686 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x00007f92484466b9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x00007f9244c760a4 in start_thread () at /lib64/libpthread.so.0 #4 0x00007f924ac4acbd in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f91eed4a700 (LWP 2629)): #0 0x00007f9244c7a03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x00007f92481b8e7d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x00007f924846e1e6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x00007f9244c760a4 in start_thread () at /lib64/libpthread.so.0 #4 0x00007f924ac4acbd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f91df5f5700 (LWP 2638)): #0 0x00007f924ac3e95d in read () at /lib64/libc.so.6 #1 0x00007f92446e2750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007f92446a1714 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x00007f92446a1b7b in () at /usr/lib64/libglib-2.0.so.0 #4 0x00007f92446a1cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x00007f924b3c60de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7f91d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x00007f924b397e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7f91df5f4de0, flags=...) at kernel/qeventloop.cpp:149 #7 0x00007f924b398165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7f91df5f4de0, flags=...) at kernel/qeventloop.cpp:204 #8 0x00007f924b2950bf in QThread::exec() (this=<optimized out>) at thread/qthread.cpp:538 #9 0x00007f924b29779f in QThreadPrivate::start(void*) (arg=0x19f0fb0) at thread/qthread_unix.cpp:349 #10 0x00007f9244c760a4 in start_thread () at /lib64/libpthread.so.0 #11 0x00007f924ac4acbd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f924d72c800 (LWP 2627)): [KCrash Handler] #5 0x00007f924b864914 in KMimeType::allParentMimeTypes() const () at /usr/lib64/libkdecore.so.5 #6 0x00007f91e4b272ae in MessageComposer::AttachmentControllerBase::showContextMenu() () at /usr/lib64/libmessagecomposer.so.4 #7 0x00007f91e4b2c9f5 in () at /usr/lib64/libmessagecomposer.so.4 #8 0x00007f924b3ad1fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=0x472c2d0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3576 #9 0x00007f924be02ed2 in QWidget::event(QEvent*) () at /usr/lib64/libQtGui.so.4 #10 0x00007f924c19f5de in QFrame::event(QEvent*) () at /usr/lib64/libQtGui.so.4 #11 0x00007f924c2aee03 in QAbstractItemView::viewportEvent(QEvent*) () at /usr/lib64/libQtGui.so.4 #12 0x00007f924c2ed9b0 in QTreeView::viewportEvent(QEvent*) () at /usr/lib64/libQtGui.so.4 #13 0x00007f924b399416 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) (this=<optimized out>, receiver=0x2c806c0, event=0x7ffdc3c5fd80) at kernel/qcoreapplication.cpp:1063 #14 0x00007f924bdb374c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #15 0x00007f924bdbaa68 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #16 0x00007f924cad2e0a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #17 0x00007f924b3992ad in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffdc3c60590, receiver=0x2c806c0, event=0x7ffdc3c5fd80) at kernel/qcoreapplication.cpp:953 #18 0x00007f924be2acf0 in () at /usr/lib64/libQtGui.so.4 #19 0x00007f924be2970c in QApplication::x11ProcessEvent(_XEvent*) () at /usr/lib64/libQtGui.so.4 #20 0x00007f924be505c2 in () at /usr/lib64/libQtGui.so.4 #21 0x00007f92446a1a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #22 0x00007f92446a1c48 in () at /usr/lib64/libglib-2.0.so.0 #23 0x00007f92446a1cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #24 0x00007f924b3c60be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x15da030, flags=...) at kernel/qeventdispatcher_glib.cpp:450 #25 0x00007f924be50676 in () at /usr/lib64/libQtGui.so.4 #26 0x00007f924b397e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffdc3c60490, flags=...) at kernel/qeventloop.cpp:149 #27 0x00007f924b398165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffdc3c60490, flags=...) at kernel/qeventloop.cpp:204 #28 0x00007f924b39d5b9 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1225 #29 0x00000000004037f2 in () #30 0x00007f924ab87b05 in __libc_start_main () at /lib64/libc.so.6 #31 0x0000000000403c97 in _start () Reported using DrKonqi
I have the same problem after updating to kmail2.
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.