Version: 1.9.4 (using KDE 3.5.4, compiled sources) Compiler: Target: i586-mandriva-linux-gnu OS: Linux (i686) release 2.6.17-5mdv At the time this happened, my computer was particularly slow due to doing SETI calculations at nice =-19, and also doing a computer intensive hard drive image backup using the command: dd if=/dev/hdb | gzip -c | split -b 630m - /shared/backup.img.gz. At this time, kmail was also in the process of trying to fetch some mail and had not finished yet. To reduce the number of programs running, I pressed the "X" on the top-right corner of kmail to tell kmail to close and exit. This is where the crash happened. Please see the following bug report: ------------------------------------ (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1251649840 (LWP 15486)] [New Thread -1280152672 (LWP 15490)] [New Thread -1271759968 (LWP 15489)] [New Thread -1263367264 (LWP 15488)] [New Thread -1254974560 (LWP 15487)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb7b50a35 in KMail::AccountManager::cancelMailCheck () from /usr/lib/libkmailprivate.so #7 0xb7c0e618 in KMMainWin::~KMMainWin$delete () from /usr/lib/libkmailprivate.so #8 0xb7c79132 in KMKernel::cleanup () from /usr/lib/libkmailprivate.so #9 0x0804a46a in ?? () #10 0xb567075c in __libc_start_main () from /lib/i686/libc.so.6 #11 0x0804a1b1 in ?? ()
Can you reproduce the crash again?
Created attachment 20294 [details] while terminal window "Konsole" open at this time - doing nothing The debug report appears to have new values on this crash. I don't think "Konsole" had anything to do with it but just mentioning it in case it affects the debug results. I think what may have caused it is that I'm in the process of trying to download into about 7 "mbox" email boxes at once. I flipped up the download indicator to visually display how many email accounts were being accessed (about 7), then clicked on the "X" close tab on the top right even though Kmail was not done yet (one of my email accounts was in the process of downloading a 1M file). Nothing happened at this point. Then 3 email accounts reported "can't access mail". no crash yet. Clicked the okay to close those "Okay tabs". Started-up Kmail again and noticed that it was still in the process of downloading the large 1M email. Interesting, appears that Kmail still downloads even though you supposedly closed it because the bar-graph for that email account was further along (about the right point in time for the time that passed). Closed Kmail again and estimated about the amount of time for that large download to finish - about the time I think the download finished - NOW Kmail reports a crash (see attached report#2). I'll send you a 3rd crash, more or less same sequence of events even though my email accounts are now empty since I tried again soon afterwards.
Created attachment 20297 [details] another crash, no "konsole" It appears getting mail, wait til done is okay because you can close Kmail and no harm done then. It appears that closing Kmail while still accessing the email accounts causes problems (see 3rd attachment). Here are some more details: Several of my email accounts are receive as: POP3, port 110, Encryption=none, Authentication Method=PLAIN 2 accounts are receive as: POP3, port 110, Encryption=Use TLS, Authentication method=Clear text These 2 accounts usually complain daily that the certificate is not current, do you want to accept this new certificate? - which I usually press Okay. Since I closed Kmail via the "X" on the top right, maybe these 2 accounts cause the problem ????
Created attachment 20298 [details] open-close-open-close-(not finished yet)-crash 1) It appears that opening Kmail and closing Kmail during download is okay. 2) Opening Kmail, Clicking "File->Check Mail", closing Kmail, opening Kmail before getting to the TLS email accounts is okay. 3) Opening Kmail, Clicking "File->Check Mail", closing Kmail, opening Kmail and then closing Kmail before getting to the TLS email accounts causes a crash. All email boxes are in mbox format. The 1st 5 accounts are general POP plain text, the last 2 are "Use TLS, Clear Text"
Those backtraces in the attachments more or less match the one in bug 134911, so I suspect this is the same issue. *** This bug has been marked as a duplicate of 134911 ***