Bug 321482

Summary:	infinite loop then crash when trying to open "Configure Filters..."
Product:	[Applications] kmail2	Reporter:	Martin Buerger <massimo79>
Component:	UI	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	major	CC:	montel
Priority:	NOR
Version:	4.10.4
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	backtrace mail filter configuration file

Description Martin Buerger 2013-06-22 06:56:14 UTC

I do not know since when but currently I am not able to configure my filters.

Reproducible: Always

Steps to Reproduce:
1. Go to Settings -> Configure Filters...

Actual Results:  
crash and exit

Expected Results:  
display the filter settings dialog

Comment 1 Martin Buerger 2013-06-22 06:57:21 UTC

Created attachment 80703 [details]
backtrace

Comment 2 Laurent Montel 2013-06-22 07:21:52 UTC

Please install debug package.
For the moment I can't see pb there is not kmail symbol here.

Comment 3 Martin Buerger 2013-06-22 07:28:03 UTC

Since my OS is Gentoo I compiled kmail with
CFLAGS="-march=amdfam10 -O2 -pipe -ggdb"
and USE="debug". I probably need to recompile kdelibs/kdepimlibs/... with that too but I'm not sure. Please advise.

Comment 4 Jekyll Wu 2013-06-22 09:08:49 UTC

the backtrace shows an infinite loop

Comment 5 Martin Buerger 2013-07-02 12:40:50 UTC

same problem with 4.10.4

Comment 6 Laurent Montel 2013-07-02 14:19:13 UTC

Attach your export filter here. Perhaps there is a pb with it.

Comment 7 Martin Buerger 2013-07-02 19:44:31 UTC

Created attachment 80903 [details]
mail filter configuration file

Comment 8 Denis Kurz 2016-09-24 18:20:54 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 9 Denis Kurz 2017-01-07 21:48:49 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.