Bug 322142 - kmail spams the desktop "mail dispatcher is offline" after sleep / resume cycle
Summary: kmail spams the desktop "mail dispatcher is offline" after sleep / resume cycle
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.10.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-09 06:58 UTC by davidblunkett
Modified: 2020-05-10 09:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description davidblunkett 2013-07-09 06:58:53 UTC
kmail spams the desktop "mail dispatcher is offline" after sleep / resume cycle

It sticks a dialogue up after resuming about the mail dispatcher being off line which seems entirely unnecessary since no one expects it to send mail while the computer is sleeping and in the fraction of a minute between sleep and being fully resumed (and the mail dispatcher being online again) it shouldn't throw this error.

Reproducible: Always

Steps to Reproduce:
1. send computer to sleep
2. resume
3. observe unnecessary error dialogue
Actual Results:  
Mail dispatcher error

Expected Results:  
kmail shouldn't produce this error - there is no error condition to report
Comment 1 Denis Kurz 2016-09-24 18:23:35 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 2 davidblunkett 2016-09-28 10:03:33 UTC
I believe this is working ok in 5.1.3 setting to resolved
Comment 3 Achim Bohnet 2020-05-10 09:24:30 UTC
After 4 years a similar bug appeared again in 5.14.  But the bug here was fixed
for the several years.  No need to 'wait for input'.  I mark it as 'Fixed'.

Similar new bug: https://bugs.kde.org/show_bug.cgi?id=421267