Bug 195550

Summary:	kmail crashes when selecting a new message while the current one has not yet been rendered
Product:	[Applications] kmail	Reporter:	Kai Krakow <kai>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	christophe
Priority:	NOR
Version:	1.11.4
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description Kai Krakow 2009-06-07 13:01:44 UTC

Version:           1.11.4 (using 4.2.4 (KDE 4.2.4), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.29-gentoo-r5

Using imap I can reproduce the following behaviour:

Select a mail which does not instantly display (probably due to bug 195549 which I reported before). Then click on another mail to view it in the preview pane. Just a moment later kmail crashes with sig 11.

One can work around it waiting for a preview to completly render before switching to the next mail but that is impractical.

This doesn't seem to happen when using dimap. Haven't tried pop3 though.

Comment 1 Christophe Marin 2009-06-07 13:52:08 UTC

Do you have a backtrace for this crash ?

Comment 2 Kai Krakow 2009-06-08 13:30:01 UTC

My package (gentoo) is built without debug info (no gdb and framepointer omitted). I need to rebuild first. Will it be enough to just rebuild kmail? Or kdelibs also?

Comment 3 Kai Krakow 2009-06-08 22:31:27 UTC

Hmpf currently not reproducable but I am pretty sure the bug is not gone... I'll put this on ice until it happens again.

Comment 4 Christophe Marin 2009-06-11 23:51:11 UTC

(In reply to comment #2)
> My package (gentoo) is built without debug info (no gdb and framepointer
> omitted). I need to rebuild first. Will it be enough to just rebuild kmail? Or
> kdelibs also?


You need at least the debug symbols for kdepimlibs and kdepim (kdelibs may be useful but not required).

Changing the bug status until you're able to reproduce the crash.

Comment 5 Kai Krakow 2009-06-15 22:29:43 UTC

I can no longer reproduce it on any computer since I upgraded to kde 4.2.4 - so this is probably fixed and can be closed. My report was on kde 4.2.4 - yes. But I suppose my session was in need of a restart since that was reported just after upgrading and was thus probably only an artifact.

I will reopen it in case it happens again (against all odds).

Comment 6 Christophe Marin 2009-06-16 00:07:56 UTC

ok, changing to a better resolution then. Thanks for the feedback.