Version: (using Devel) Installed from: Compiled sources Compiler: x86_64-pc-linux-gnu-4.2.3 OS: Linux I was trying to move some mail folders when this happened. I did move 3 folders before and everything went ok Application: KMail (kmail), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0x2b3be2d0a230 (LWP 4220)] [New Thread 0x41001950 (LWP 4276)] [New Thread 0x40800950 (LWP 4250)] [KCrash handler] #5 0x00002b3bde1d636a in Q3ListView::contentsMousePressEventEx ( this=0x981e70, e=0x7fffd8340a20) at itemviews/q3listview.cpp:4161 #6 0x00002b3bda904795 in K3ListView::contentsMousePressEvent (this=0x981e70, e=0x7fffd8340a20) at /var/tmp/paludis/kde-base-kdelibs-scm/work/kdelibs-scm/kde3support/kdeui/k3listview.cpp:790 #7 0x00002b3bde2244a9 in Q3ScrollView::viewportMousePressEvent ( this=0x981e70, e=0x7fffd8341330) at widgets/q3scrollview.cpp:1744 #8 0x00002b3bde225ff2 in Q3ScrollView::eventFilter (this=0x981e70, obj=0x981c10, e=0x7fffd8341330) at widgets/q3scrollview.cpp:1472 #9 0x00002b3bde1ce63e in Q3ListView::eventFilter (this=0x981e70, o=0x981c10, e=0x7fffd8341330) at itemviews/q3listview.cpp:3777 #10 0x00002b3bd4371fa2 in KMFolderTree::eventFilter (this=0x981e70, o=0x981c10, e=0x7fffd8341330) at /var/tmp/paludis/kde-base-kmail-scm/work/kmail/kmail/kmfoldertree.cpp:1807 #11 0x00002b3bd2acffed in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0x981c10, event=0x7fffd8341330) at kernel/qcoreapplication.cpp:694 #12 0x00002b3bdd4b75d0 in QApplicationPrivate::notify_helper (this=0x62f430, receiver=0x981c10, e=0x7fffd8341330) at kernel/qapplication.cpp:3762 #13 0x00002b3bdd4bc815 in QApplication::notify (this=<value optimized out>, receiver=0x981c10, e=0x7fffd8341330) at kernel/qapplication.cpp:3495 #14 0x00002b3bd7c5fe7e in KApplication::notify (this=0x7fffd8341de0, receiver=0x981c10, event=0x7fffd8341330) at /var/tmp/paludis/kde-base-kdelibs-scm/work/kdelibs-scm/kdeui/kernel/kapplication.cpp:311 #15 0x00002b3bd2acfd38 in QCoreApplication::notifyInternal ( this=0x7fffd8341de0, receiver=0x981c10, event=0x7fffd8341330) at kernel/qcoreapplication.cpp:587 #16 0x00002b3bdd4b9aff in QApplicationPrivate::sendMouseEvent ( receiver=0x981c10, event=0x7fffd8341330, alienWidget=<value optimized out>, nativeWidget=0x815bf0, buttonDown=<value optimized out>, lastMouseReceiver=@0x2b3bdde806b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #17 0x00002b3bdd521b36 in QETWidget::translateMouseEvent (this=0x815bf0, event=<value optimized out>) at kernel/qapplication_x11.cpp:4112 #18 0x00002b3bdd5208a0 in QApplication::x11ProcessEvent (this=0x1a6, event=0x7fffd8341ab0) at kernel/qapplication_x11.cpp:3234 #19 0x00002b3bdd545394 in QEventDispatcherX11::processEvents (this=0x62ed40, flags=@0x7fffd8341bc0) at kernel/qeventdispatcher_x11.cpp:134 #20 0x00002b3bd2acf135 in QEventLoop::processEvents ( this=<value optimized out>, flags=@0x7fffd8341c00) at kernel/qeventloop.cpp:149 #21 0x00002b3bd2acf28e in QEventLoop::exec (this=0x7fffd8341c40, flags=@0x7fffd8341c50) at kernel/qeventloop.cpp:200 #22 0x00002b3bd2ad12e9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #23 0x000000000040336e in main (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/paludis/kde-base-kmail-scm/work/kmail/kmail/main.cpp:132 #0 0x00002b3bdede9c21 in nanosleep () from /lib64/libc.so.6
*** Bug 169002 has been marked as a duplicate of this bug. ***
*** Bug 172717 has been marked as a duplicate of this bug. ***
*** Bug 181085 has been marked as a duplicate of this bug. ***
Fixed in KDE 4.2 (there is no q3listview anymroe).
*** Bug 188436 has been marked as a duplicate of this bug. ***
*** Bug 170076 has been marked as a duplicate of this bug. ***
I could still reproduce the crashes with trunk not long ago, so I don't think it's a 4.2 thing alone. Anyway, after I removed my old ~/Mail folder (yes, I've been a kmail user for long before the default folder was changed), I cannot reproduce it anymore. Not sure what, but the use of the older folders was causing this. I don't think the bug is fixed or gone, rather hidden deeply ;)