Version: (using KDE KDE 3.3.0) Installed from: FreeBSD Ports Compiler: gcc 2.95.3, unless the FreeBSD port requests something later (which I don't think it does) OS: FreeBSD Under some circumstances that I don't understand (but rather often), selecting an unread mail message in my IMAP inbox neither shows it in the preview pane nor marks it as read. This has happened when the selection was done - by clicking with the mouse; - by pressing "n" to move to the next message; - by applying a filter that moves the current message into a different folder, making a later message current. Clicking on the message again doesn't make any difference. Selecting a different message first and then the original one again (either with the mouse or, e.g., the keys p,n) reliably selects the message properly -- i.e., previews it and marks it read. This sounds similar to bug 88511, but seems to differ from it in at least the following ways: - Selecting a different message consistently makes that message appear in the preview pane. - I have not found it necessary to select a different folder to get the messages to appear. The behaviour is not consistent, in that sometimes selecting a new message works absolutely fine. However, it seems to be "bursty"; if I have a block of new messages and KMail misbehaves on the first one, it will generally do so on the second as well. Unfortunately I haven't yet discerned what it is that breaks this pattern. I *think* (with very little confidence) that the failure commonly begins when I filter away some messages. I do not think this has ever happened with an already-read message. I have only observed this in my inbox (which, as I say, is an IMAP one, talking to a MS Exchange 5 server) and not in any other folder. I spend much longer in my inbox than elsewhere, though, so this is not strong evidence that it can't happen elsewhere. This has happened to me ever since installing KDE 3.3 (built from the FreeBSD ports collection without specifying any special flags, environment variables, etc.). I don't recall it ever happening in earlier versions of KMail. I'd love to give a repro recipe, but I don't have one. :-) I'm running KMail in pretty much its default setup. No plugins. I'm *not* running it in a full KDE environment; I'm using the Ion window manager. There's nothing obviously relevant in such debugging output as I have, although I often get the following line kmail: WARNING: KMMessagePart::bodyDecoded(): body is binary but used as text! output to whatever-I-ran-kmail-from when I select a new message. (I haven't looked for any correlation between this and the bad behaviour mentioned above, but it certainly sometimes happens when that bad behaviour doesn't occur, and I used to get that message all the time with an earlier version of KMail that never exhibited the message-selection problem.) Operating system: FreeBSD 4.5.
I have the same thing happening to me. It seems to be happening when the mail check is kinda sorta allmost done, i.e. you move to a new unread message during mail check. Doesn't always happen, but when it happens it seems to be when the check is almost done. Normally, when you do that during a mailcheck, it'll wait until the check is over and display the message then.
Correction: this doesn't happen only with unread messages. Old messages that I haven't read for some time are also affected. But any message I've selected recently is OK.
*** Bug 91354 has been marked as a duplicate of this bug. ***
It appears to me it happens all the time, when the background process reading messages finishes. I use IMAP folders too. K<o>
Oops, it just happened to me again. It not only does blank the preview, it also closes all open threads in the list of mails in my folder. May be that info helps to pin down the culprit. K<o>
That doesn't happen to me. When I said "any message I've selected recently is OK", that may have been overoptimistic. Something along those lines is true, but "recently" needs to be defined quite strictly. I haven't pinned down whether it's time that matters, or how many other messages viewed in between, or something else, but we're looking at time on the order of 30 seconds or #messages on the order of 8.
Hi all. I've done some major investigation here. Ihave recompiled kmail from the branch and it does not happen to me. Till committed this fix: http://lists.kde.org/?l=kde-cvs&m=109683551407295 That was on October 3rd (version 1.658.2.5). Sadly enough the Tag for kde 3.3.1 is at 1.658.2.4 So this is fixed just after the tagging of the new version. To make sure this fixes the problem I have compiled without Tills fix and the problem appeared instantly. So I am sure this problem will not be there in 3.3.2, nor in 3.4 (whenever that comes).
*** Bug 93302 has been marked as a duplicate of this bug. ***
*** Bug 93510 has been marked as a duplicate of this bug. ***