| Summary: | Crashes when filtering IMAP folder | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | eddie |
| Component: | IMAP | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | andresbajotierra, christophe |
| Priority: | NOR | ||
| Version First Reported In: | 1.9.50 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | strace of kmail crash | ||
|
Description
eddie
2008-04-24 08:46:39 UTC
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 :) |