Version: unknown (using 4.0.3 (KDE 4.0.3) "release 18.1", compiled sources) Compiler: gcc OS: Linux (i686) release 2.6.22.17-0.1-default I have an imap account set up in kmail but I don't know if that is significant. Anyway, it seems that when filtering mail which includes spam checking kmail crashes. I've tried removing the spam checker and then seems to work okay. Most of the information from the backtrace in the crash handler states that "no debugging symbols found." However there are these lines at the end: Thread 1 (Thread 0xb475e6d0 (LWP 12981)): #0 0xffffe410 in __kernel_vsyscall () #1 0xb4f788b0 in nanosleep () from /lib/libc.so.6 #2 0xb4f786b7 in sleep () from /lib/libc.so.6 #3 0xb68f1ea9 in ?? () from /usr/lib/libkdeui.so.5 #4 0x00000001 in ?? () #5 0x00000000 in ?? () #0 0xffffe410 in __kernel_vsyscall () I hope that is useful. kmail version is 1.9.50 on kde 4.0.3 "release 18.1"
Please try to get a better backtrace, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
I've install kmail on two other machines running only pop accounts and they both behave well. So I assume that the imap is significant. I've tried using strace and obtained the following output: SpamAssassin version 3.2.3 SpamAssassin version 3.2.3 /bin/sh: /home/eddie/.annoyance-filter/annoyance-filter: No such file or directory /bin/sh: sb_filter.py: command not found X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x3a06d52 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x3a0685f Object::connect: No such signal KIO::TransferJob::processedSize(KJob*,KIO::filesize_t) Object::connect: No such signal KIO::TransferJob::processedSize(KJob*,KIO::filesize_t) *** KMail got signal 11 (Crashing) KCrash: Application 'kmail' crashing... I hope this is more helpful
Created attachment 24647 [details] strace of kmail crash Started kmail with strace -o strace.log /usr/bin/kmail and then let it run until I noticed that it had crashed. Used ctl-c to end strace. and have attached the log.
What we expect is a detailed backtrace. Once again, please follow instructions on this page to provide something that can help us : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Have anyone experienced this bug again with a recent KDE version? (4.1.3 / 4.2beta2 / 4.2svn) ? Thanks :)
Marking as WORKSFORME as the original bug reporter haven't experienced the crash again using a recent version of KDE. Please, reopen this bug report with new information if you experience this bug again. Thanks :)