Bug 190331 - After shutting down KMail, a thread remains open
Summary: After shutting down KMail, a thread remains open
Status: RESOLVED DUPLICATE of bug 185820
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.9.10
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-22 12:01 UTC by Axel Braun
Modified: 2009-04-23 09:57 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 Axel Braun 2009-04-22 12:01:47 UTC
Version:            (using KDE 3.5.10)
OS:                Linux
Installed from:    SuSE RPMs

After closing KMail (CRTL-Q), I noticed that there is still a process running:

axel@z60m:~> ps ax | grep kmai
10338 ?        Sl     0:16 kmail -caption KMail -icon kmail -miniicon kmail
10766 pts/0    S+     0:00 grep kmai

can that be that Kmail is synchronizing with DIMAP-folders? If so, a popup like 'sync in progress' would be helpful.

Otherwise: you just close the lid (put the laptop into suspend to RAM) while the sync is in progress, which might be a reason for the behaviour as described in bug 63353  (Disconnected IMAP wipes email).
After resume, the thread is still there and prevents KMAIL from downloading mail
Comment 1 Jaime Torres 2009-04-23 09:57:41 UTC
Even this is for kde3 and the dup is for kde4, the bug is the same.

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 185820, 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 185820 ***