Version: 1.7.1 (using KDE 3.3.1, SuSE)
Compiler: gcc version 3.3.3 (SuSE Linux)
OS: Linux (i686) release 2.6.5-7.111-default
when i cycle through unread mails in imap folders, kmail sometimes does not show the mails in the preview pane (the preview pane stays empty instead). from ethersniffing i see that kmail actually fetches the message in question, but it does not show it.
the version i use is packaged by email@example.com and the package changelog suggests that his last change (which seems to be the cause for this) was this:
* Thu Nov 25 2004 - firstname.lastname@example.org
- update to current 3_3_BRANCH to get latest SLOX fixes
So i guess its something in there that is the reason for this misbehaviour.
seems to happen only on one of my two machines. only difference that i can think of is that the machine that seems to work ok has 512meg ram, the other one has 256meg. besides, it seems to happen more often with mime multipart messages, and/or pgp-signed messages.
upgraded to kde 3.3.2 / kmail 1.7.2, problem still exists, on both machines.
with this bug, kmail is pretty much useless in an imap environment.
i dont know if anyone cares, but i'd classify this as a showstopper.
CVS commit by tilladam:
Make sure the preview area is not prematurely emptied.
Adrian, would you consider an update, this is fairly annoying for users.
M +1 -2 kmheaders.cpp 1.658.2.9
--- kdepim/kmail/kmheaders.cpp #1.658.2.8:1.658.2.9
@@ -1252,5 +1252,4 @@ void KMHeaders::msgAdded(int id)
- emit messageListUpdated();
@@ -2189,5 +2188,5 @@ void KMHeaders::highlightMessage(QListVi
KMMessage *msg = mFolder->getMsg(idx);
- if (!msg || msg->transferInProgress())
+ if (!msg )
emit selected( 0 );
i don't think this is about "premature emptying", because when it happens, the message i try to read is also not marked as read if it was unread...
oh, also, if i select all messages in the folder when it happens, do "mark all read", and then select another message, and then "the one" again, it shows up in the preview as wanted.
*** Bug 95420 has been marked as a duplicate of this bug. ***
oh, btw, when can users expect this patch to be "in effect" in some _released_ version of kde/kmail? earlier than kde 4.0?
It will be in 3.3.3, 3.4 and if there is one your next updated kdepim rpm from SuSE. I've told the packagers about this fix, it's their decision whether to release updates or not.
/me starts cronjob to pester a certain person about it
i was asking because i already experienced bugfixes and feature requests within kde which were tagged as "solved in CVS" several years ago, and are still not implememted in a released version...
On Monday 27 December 2004 19:19, Mathias Homann wrote:
> i was asking because i already experienced bugfixes and feature requests
> within kde which were tagged as "solved in CVS" several years ago, and are
> still not implememted in a released version...
If there is such a bug or feature then please tell us. If something is fixed
in cvs it will be in the next release. If it isn't, that's new bug. So I'd be
interested what feature/bug you are refering to.