Bug 321980 - With imap account, if network is coming down while doing something, notification flood appears
Summary: With imap account, if network is coming down while doing something, notificat...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.10.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-05 08:14 UTC by Mike Krutov
Modified: 2017-01-07 22:00 UTC (History)
0 users

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 Mike Krutov 2013-07-05 08:14:35 UTC
I've noticed this when performed restart of dbus subsystem with updates.
Dbus, while restarting, shutted down wicd, getting network down.
Then dbus came up & wicd came up, too.
Then KMail started notification flood (3 notifications/sec) with "IMAP: can not <something> offline" (I couldn't read the notification due to its speed of disappearence)
Exact steps to reproduce were found later, however, when my wicd lost connectivity with my wifi. 

Reproducible: Always

Steps to Reproduce:
1. Launch KMail with IMAP (only google imap tested)
2. Select huge mailbox (I have had > 500 unread messages), press right button, press mark unread
3. Shut down network
Actual Results:  
Notifications flood you.
(seem that 1 notification per object/piece of mail)

Expected Results:  
One notification shows up for the whole event.

Very annoying, actually. 
Notifications flooding stops either if you restart your kde session either if you wait for them to finish (which takes ages).
Comment 1 Denis Kurz 2016-09-24 18:19:51 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 Mike Krutov 2016-09-24 18:52:46 UTC
I'm not using KDE for more then 2 years already so can not confirm.
Comment 3 Denis Kurz 2017-01-07 22:00:42 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.