Bug 31423 - KMail crashes when you move an email out of an IMAP folder
Summary: KMail crashes when you move an email out of an IMAP folder
Status: CLOSED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.3.1
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-23 22:18 UTC by fredrikh
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fredrikh 2001-08-23 22:08:14 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kmail
Version:           1.3.1 (using KDE 2.2.1 pre)
Severity:          normal
Installed from:    compiled sources
Compiler:          gcc version 2.95.4 20010319 (Debian prerelease)
OS:                Linux (i586) release 2.4.9
OS/Compiler notes: 

This resembles previously reported problems that are marked as done however this can be reproduced in the currect CVS Branch.

KMail frequently crashes when I attempt to move email from an IMAP folder to another folder (local or IMAP)

I believe the crash occurs when you try to move or delete an email after KMail has requested it from the mail server but hasn't yet finished downloading it or hasn't started downloading it.

Another possibility is that it tries to display an email after it's been deleted.

It doesn't crash if you select an email and wait for KMail to download and display it before moving or deleting it. It almost always crashes when you select multiple emails and then move/delete them.

It's possible that this bug can only be reproduced on IMAP servers that are under a heavy load or are otherwise slow in responding.

Backtrace:
0x41164f89 in wait4 () from /lib/libc.so.6
#0  0x41164f89 in wait4 () from /lib/libc.so.6
#1  0x411ceb4c in __check_rhosts_file () from /lib/libc.so.6
#2  0x40923145 in KCrash::defaultCrashHandler (signal=11) at kcrash.cpp:197
#3  0x410eea28 in sigaction () from /lib/libc.so.6
#4  0x814d150 in KMImapJob::messageRetrieved (this=0x83ce358 t0=0x839a158)
    at kmacctimap.moc:166
#5  0x81600d0 in KMImapJob::slotGetMessageResult (this=0x83ce358 
    job=0x83d1bc0) at kmacctimap.cpp:793
#6  0x404aa7df in KIO::Job::result (this=0x83d1bc0 t0=0x83d1bc0)
    at jobclasses.moc:189
#7  0x4048f159 in KIO::Job::emitResult (this=0x83d1bc0) at job.cpp:159
#8  0x40490406 in KIO::SimpleJob::slotFinished (this=0x83d1bc0) at job.cpp:373
#9  0x40492bb9 in KIO::TransferJob::slotFinished (this=0x83d1bc0)
    at job.cpp:631
#10 0x40bd672b in QObject::activate_signal () from /usr/lib/libqt.so.2


(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 Michael Haeckel 2001-09-29 15:43:31 UTC
On Friday 24 August 2001 00:08 fredrikh@mailandnews.com wrote:
>
> It's possible that this bug can only be reproduced on IMAP servers that are
> under a heavy load or are otherwise slow in responding.

Well at least for me that always worked well but I finally managed to 
reproduce it. That didn't seem to happen with all local folder...
Should be fixed now.

Regards
Michael Häckel