Bug 195284 - kmail requires restart after sleep
Summary: kmail requires restart after sleep
Status: RESOLVED DUPLICATE of bug 186936
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-05 01:48 UTC by andrew
Modified: 2009-06-05 10:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andrew 2009-06-05 01:48:23 UTC
Version:           Version 1.11.90
Using KDE 4.2.87 (KDE 4.2.87 (KDE 4.3 >= 20090519)) (KDEmod) (using Devel)
OS:                Linux
Installed from:    Compiled sources

Backdrop: Using kmail to connect to gmail via imap
use case: Start kmail and read email - everything works just fine; put laptop to sleep; later resume; kmail no longer connects to the mail server.  Quit and restart kmail - everything is good again.

The behaviour of kmail is not quite a "hang".  The UI still responds but the download of message headers or email to view never completes.  On occations it will take a very long time to *appear* to initiate but then stop at 90%.  Sometimes it will appear to complete (according to progress bar) but the actual folder contents displayed are stale and are not correctly updated until kmail is restarted.  I expect each task timed out and kmail just reported it as complete.

My guess (sorry) is that kmail is trying to keep its connections to the mail server open; these connections go stale connections when the network is stopped and restarted but kmail doesn't notice or correct the situation.  Just a guess but that's what it feels like.
Comment 1 Jaime Torres 2009-06-05 10:46:38 UTC
Thank you for taking the time to report this bug and helping to make KDE better. This particular bug has already been reported and is a duplicate of bug 186936, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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