[Bug 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]

Siu Chung Cheung (Clement) clement.cc at gmail.com
Fri Jun 11 22:32:39 BST 2010


https://bugs.kde.org/show_bug.cgi?id=169048


Siu Chung (Clement) Cheung <clement.cc at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |clement.cc at gmail.com




--- Comment #25 from Siu Chung (Clement) Cheung <clement cc gmail com>  2010-06-11 23:32:32 ---
Hi,

This crash is due to you all having a rule with no actions but having "stop
processing here" to make certain emails immune to subsequent rules. (see
Michal's filter #1) Kmail currently chokes on that.

I have already debugged this crash and attached a fix in bug 169646. Please see
comments and attachment there for full explanation of this crash. I notice now
that the bug is already closed when I posted due to lack of feedback, which is
probably why nobody noticed my patch. Sorry about that. Should have searched
more.

Can someone try my patch and see if it works for you and maybe have someone
from the kmail team take a look? There have been so many reports of this bug
already. The crash is fully reproducible. But you must have *NEW* email
matching the no action rule to trigger this crash. So if you rerun kmail
immediately after the crash, it no longer happens due to the mail being no
longer new. This is probably why people are saying the crash is "random". To
reproduce the bug consistently, simply make a no action rule matching your own
email address and send an email to yourself.

As a workaround, add a sound action to your empty rule. If you find the barrage
of sound annoying, simply record one second of silence and use that as your
"sound".

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list