Summary: | crash when using 2.3.8 cyrus-imapd server. | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Jim Ramsey <jwramsey> |
Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 1.9.5 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Backtrace from KMail IMAP crash |
Description
Jim Ramsey
2007-04-15 19:30:04 UTC
I must have miss-typed something. I'm running KDE 3.5.5 not 3.5.6 I can't figure out how change this. Looks like bug 143250. Please try the SVN version (3.5 branch) or the KDE 3.5.7 version (as soon as it is released) and see if the problem is fixed. >I can't figure out how change this.
You can't, but it does not matter. The KMail version (1.9.5) is correct.
OK. I'm hunting around now in hopes of finding a test openSUSE repository. I'd like to avoid to the full build myself if I can. On Sunday 15 April 2007, Thomas McGuire wrote: [bugs.kde.org quoted mail] Hmmm. I looked for version 3.5.7 and found version 3.5.6 which didn't help. I also found version 3.8 but that is apparently the kde4 beta. Should I be looking to grab an svn snapshot ? How? On Sunday 15 April 2007, Thomas McGuire wrote: [bugs.kde.org quoted mail] This is very interesting. I wasn't able to find kde 3.5.7, so I decided to try version 3.5.6 I'm running it now. Initially, I had the same failure. I didn't even save the trace back. Then I decided to run it again and looked at the traceback, and noticed this interesting part. [KCrash handler] #9 0xb7cf0c16 in KMMsgBase::storage () from /opt/kde3/lib/libkmailprivate.so #10 0xb7d2b101 in KMFolderImap::deleteMessage () from /opt/kde3/lib/libkmailprivate.so #11 0xb7d2b874 in KMFolderImap::removeMsg () from /opt/kde3/lib/libkmailprivate.so The interesting part is that I had disabled periodic checks for new messages. Then it hit me ---- Expired messages. I have many sub-folders under my IMAP Account. I added some expire rules. That struck as a bit odd at the time, but I couldn't see a way to do this using sieve. Anyway, kontact / kmail let me do it. Just now I went through all my sub-folders and removed all the expire rules, and surprise, surprise I'm up and staying up. I've been up now for 2hrs and 20 minutes. Previously, I would stay of for 5 or 10 minutes and then crash. I'm going to re-enable periodic checks for new mail. Manual checks work, so I am hopefull. I'm also hopefull that this is a clue. On Sunday 15 April 2007 13:38:03 Thomas McGuire wrote: [bugs.kde.org quoted mail] >Should I be looking to grab an svn snapshot ? How? I couldn't find a document explaining how to do this, so better wait until 3.5.7 is released, which it should be at May 8th. About the expire settings: The expire settings by default delete the mail. Since deleting mail causes the crash (see bug 143250), switching off those settings prevents the periodic crashes. But the interesting part is that deleting mail from an IMAP account folder just normally works fine. On Monday 16 April 2007 09:35:25 Thomas McGuire wrote: [bugs.kde.org quoted mail] Created attachment 20367 [details]
Backtrace from KMail IMAP crash
I get this crash when I am going through my Inbox message list and deleting messages. If the list of IMAP messages is updated while I am doing this KMail will crash. the IMAP messages will be updated using a combination of Fetchmail / Postfix / Cyrus IMAP. The KMail, running inside Kontact, is on the same box as the IMAP server. I don't get crashes with KMail in "disconnected IMAP" mode on another box. bug #150038 has better backtrace *** This bug has been marked as a duplicate of 150038 *** |