Bug 117926 - kmail message headings vanish, only thread-tree outline remain, kmail becomes very slow
Summary: kmail message headings vanish, only thread-tree outline remain, kmail becomes...
Status: RESOLVED DUPLICATE of bug 89549
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-08 14:24 UTC by Alain Knaff
Modified: 2007-09-14 12:17 UTC (History)
1 user (show)

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 Alain Knaff 2005-12-08 14:24:26 UTC
Version:           1.9 (using KDE 3.5.0 Level "a" , SUSE 9.3 UNSUPPORTED)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-21.9-default

Very often, mostly after forwarding a set of messages, the message heading in the top right view just vanish. However, the lines and crosses of the tree structure stay. Clicking on one of those empty headers does not bring up the message either.

When this happens, kmail also seems to become slower, with some disk activity going on.

The view stays like this, until entering another folder, and then coming back.

However, in some cases, even going to another folder doesn't fix it... In such cases clicking on a folder on a different IMAP server, and then coming back helps though.

It's an old bug (has been happening since I've been using kmail), but somehow since 3.5 it has been happening much more often and in a worse way (more swapping, kmail slower) than before!
Comment 1 gentoo 2006-02-27 05:22:07 UTC
Version: kmail-3.5.1 on Gentoo 2.6.15

Confirmation about this bug. It seems to happen every morning when I read my email and there are several new messages in each imap folder. I use '+' and 'Ctrl-+' to read unread messages and when it jumps to a new folder, this problem almost always occurs. If I move to another folder and then back to the first folder, the problem always goes away. This seems to be linked to the colour used to display the messages. If I jump into a folder and the unread messages stay red, then the folder will work correctly. But usually the messages will initially be drawn in red and then change to blue. The message headings will then disappear if I use 'N' or 'P' to move to a different message,
Comment 2 Juha Tuomala 2006-02-27 10:16:06 UTC
I confirm this, using KDE 3.5.1 with Fedora Core 4 RPMS. 

I guess it started when I enabled 'threaded message list'.
Comment 3 Samuel Penn 2006-03-18 13:29:23 UTC
KDE 3.5.1 on Gentoo/AMD64. I get this as well. Often, a few seconds after going into a folder, the folder view will hang and all the message headings vanish (though the +/- icons are still visible). If I select a different message, I get a blank content pane. If I try an operation from the folder menu (e.g. RMB and 'Mark all messages as read') then nothing happens.

Selecting another folder, then switching back fixes it, though it will re-occur sometime later (normally within a minute).

Never seen it before KDE 3.5.
Comment 4 Juha Tuomala 2006-03-18 14:09:48 UTC
I must take back that threaded list thing. I happens even with that disabled.
Comment 5 Samuel Penn 2006-04-01 16:31:33 UTC
It seems to be something to do with the account. I have two IMAP accounts set up, and I am seeing the problem quite often in one, but have never seen it in the other. Not sure what the difference is, since they are both on the same IMAP server (Courier IMAP).
Comment 6 Ismail Onur Filiz 2006-04-10 09:13:47 UTC
Might be a stretch but is there a difference between the settings of these two accounts? If you could do key-by-key comparison in ~/.kde/share/config/kmailrc, that would be great. Are they disconnected IMAP or online IMAP by the way?

A more likely possibility is the corruption of index files in one of the accounts. Next thing to do might be moving the index files to somewhere else and then trying.
Comment 7 Carsten Burghardt 2006-04-16 17:37:05 UTC

*** This bug has been marked as a duplicate of 89549 ***