Bug 290532 - kmail2 does not show the mail selected in the message list, sais please wail
Summary: kmail2 does not show the mail selected in the message list, sais please wail
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 1.99.0
Platform: Unlisted Binaries Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-03 21:21 UTC by Rainer Merz
Modified: 2017-01-07 21:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Merz 2012-01-03 21:21:36 UTC 
Version:           1.99.0
OS:                Linux

when I selct a mail in one of the folders the preview and also the external window is not able to show the mail. Its continuously loading all messages ans sais please wait

Reproducible: Didn't try

Steps to Reproduce:
no need its always there, I am not able to read any mail


Expected Results:  
I expect that when I select a message that I can read it

OS: Linux (i686) release 3.0.0-14-generic
Compiler: gcc
Comment 1 Jerry L Kreps 2012-01-06 17:44:44 UTC 
I am running KMail2 4.8rc1 in Kubuntu 12.04 beta1.

Arriving email does not always show in the message list, but the count always  shows in the inbox counter.   If the message list does populate, a specific email  does reliably show the message body when that message header is clicked.

When the KMail client GUI is displayed, previously downloaded but unread email doesn't reliably show in the message list.  Often, while moving to the next message, the next message body does not display.  When clicking the "X" delete button the message header often grays out and remains in the message list even though the body disappears.

To correct the situation I have to close KMail and remove it from the system tray.  Then, when I restart it, the missing headers show in the message list and I can navigate through several msgs before KMail acts up again.   I repeat the shutdown-restart until I can read all the emails and move them to either the trash folder or another destination.   

The misbehavior appears to be related to the inbox.   When I browse and look at msgs stored in other folders they display as expected.
Comment 2 Jerry L Kreps 2012-01-06 17:46:54 UTC 
I am running KMail2 4.8rc1 in Kubuntu 12.04 beta1.

Arriving email does not always show in the message list, but the count always  shows in the inbox counter.   If the message list does populate, a specific email  does reliably show the message body when that message header is clicked.

When the KMail client GUI is displayed, previously downloaded but unread email doesn't reliably show in the message list.  Often, while moving to the next message, the next message body does not display.  When clicking the "X" delete button the message header often grays out and remains in the message list even though the body disappears.

To correct the situation I have to close KMail and remove it from the system tray.  Then, when I restart it, the missing headers show in the message list and I can navigate through several msgs before KMail acts up again.   I repeat the shutdown-restart until I can read all the emails and move them to either the trash folder or another destination.   

The misbehavior appears to be related to the inbox.   When I browse and look at msgs stored in other folders they display as expected.
Comment 3 dasaan.san 2013-11-03 13:11:18 UTC 
Unable to reproduce with KMail 4.10.5 in KDE 4.10.5
Comment 4 Denis Kurz 2016-09-24 17:56:53 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 21:59:33 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.