Bug 298638 - IMAP error flood and knotify4 CPU usage
Summary: IMAP error flood and knotify4 CPU usage
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-23 06:20 UTC by Brylie Christopher Oxley
Modified: 2017-01-07 21:47 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 Brylie Christopher Oxley 2012-04-23 06:20:18 UTC 
Ocasionally I will get a flood of messages (the same message over and over) saying that there is an error connecting to an IMAP server. There are usually 15 messages. I will cancel all of the messages and the flood will occurr again shortly thereafter.

Also, knotify4 CPU usage will shoot up when these errors happen.

When I terminate the knotify4 process, the file ~/.xsession-errors will grow to consume my /entire/ hard drive, unless I manually delete it.

Reproducible: Always

Steps to Reproduce:
1. Configure an IMAP account in Kontact/KMail
2. Use the IMAP account for a day or two
3. When a connection issue occurrs, a flood of errors are produced.
Comment 1 Laurent Montel 2012-04-23 06:37:36 UTC 
which message errors ?
Comment 2 Christophe Marin 2012-04-23 08:09:10 UTC 
Which kmail version ?
Comment 3 Brylie Christopher Oxley 2012-04-23 17:05:36 UTC 
(In reply to comment #2)
> Which kmail version ?

Kontact 4.8 rc2
Comment 4 Brylie Christopher Oxley 2012-04-25 18:45:15 UTC 
(In reply to comment #1)
> which message errors ?

"There is currently no session to the IMAP server available."
Comment 5 Brylie Christopher Oxley 2012-04-26 19:43:29 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > Which kmail version ?
> 
> Kontact 4.8 rc2

I just upgraded to 4.8.2 and still get the errors.
Comment 6 Denis Kurz 2016-09-24 18:20:23 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 7 Denis Kurz 2017-01-07 21:47:52 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.