[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 94043] KMail crashes when applying a filter on a closed thread
From:       Juliano Ferraz Ravasi <jferraz () linkway ! com ! br>
Date:       2006-09-20 20:33:26
Message-ID: 20060920203326.21262.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=94043         




------- Additional Comments From jferraz linkway com br  2006-09-20 22:33 -------
Either this bug is NOT fixed, or there is another real bug wandering about (reports \
#112480, #112953, #123949, #126589, etc...) which is being improperly being marked as \
a duplicate of this bug.

I'm getting 100% reproducible crashes with Kmail 1.9.3, released AFTER this bug was \
supposedly fixed. The backtrace is compatible with the bugs listed below. The crash \
happens on QGDict::look_string().

All the following bugs were (directly or indirectly) marked as a dupe of this one, \
but ALL of them reports crashes on QGDict::look_string(), which was NOT reported on \
this bug. And these reports were reported for NEWER versions of Kmail:

Bug 105242 - kontact closes when deleting message from imap account
Bug 110113 - crash on marking spam or filtering
Bug 112480 - KMail crashing when deleting messages from an IMAP account
Bug 112816 - crash when emptying trash while having it open
Bug 112953 - Kmail stürzt ab, wenn ausgewählte E-Mails in anderen Ordner verschoben \
werden sollen Bug 114072 - Kmail crash on deleting mail with the DEL key
Bug 123949 - kmail crash while deleting subfolder of local trash
Bug 126589 - moving a group of mails to the trash from an imap account crashes kmail
Bug 127293 - SIGFPE crash when deleting message from nested remote IMAP folder
Bug 128880 - Crash when delete on IMAP

So, it looks like we have ANOTHER bug here. Please, stop marking bugs as dupe of this \
one, and reopen this issue (or one of the ones wrongly marked as duplicate).


[prev in list] [next in list] [prev in thread] [next in thread]