Bug 141586

Summary:	floods .xsession-errors with KIOConnection errors
Product:	[Unmaintained] kmail	Reporter:	Marcus Better <marcus>
Component:	disconnected IMAP	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WAITINGFORINFO
Severity:	normal	CC:	bjoern
Priority:	NOR
Version:	1.9.5
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Marcus Better 2007-02-12 11:21:21 UTC

Version:           1.9.5 (using KDE KDE 3.5.6)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I frequently notice that kmail starts flooding ~/.xsession-errors at a rate of 1 MB/s. I'm using disconnected IMAP accounts.

The messages say:
  kio (KIOConnection): ERROR: Could not write data

The flooding continues until the disk is full. I had over two gigabytes of these messages recently. Shutting down kmail and killing all the kio_imap4 processes stopped the spamming.

This report was forwarded from the Debian bug tracking system:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406984

Comment 1 Christine McGavran 2007-07-31 18:41:51 UTC

This has happened to me twice. It's quite frustrating.

Comment 2 Marcus Better 2007-08-13 22:57:32 UTC

The workaround is to use "kdebugdialog --fullmode" and turn off logging of messages of severity Error for area 7017. That stops the messages, but I don't know if the mail account continues to work when the bug happens.

The messages are generated in kdelibs/kio/kio/connection.cpp, which seems to have been completely rewritten for KDE4 and at least the error messages have been removed.

Comment 3 Thomas McGuire 2007-08-14 17:09:51 UTC

>The messages are generated in kdelibs/kio/kio/connection.cpp, which seems to have been completely rewritten for KDE4 and at least the error messages have been removed. 
Thanks for the info, I'll close this bug then.

Everybody using KDE 3.5x can use kdebugdialog to turn off the messages.

Comment 4 Marcus Better 2007-08-15 07:54:20 UTC

> Thanks for the info, I'll close this bug then.


You must be kidding! That does nothing to fix the bug, it just hides it. There 
is clearly an infinite loop here. It will probably cause large CPU usage and 
perhaps prevent the app from running normally. Why don't you try to track 
down the reason for the problem instead?

> Everybody using KDE 3.5x can use kdebugdialog to turn off the messages.


And I don't see how you can close a bug that is still present in the released 
code. How do you think the majority of non-technical users will know where to 
look for the band-aid?

Marcus

Comment 5 Thomas McGuire 2007-08-15 13:56:07 UTC

>That does nothing to fix the bug, it just hides it. There is clearly an infinite loop here. It will probably cause large CPU usage and perhaps prevent the app from running normally.
Then I misunderstood you, I thought the cause for the problem was gone by the rewrite. Reopening then.

>And I don't see how you can close a bug that is still present in the released code.
Sorry, but that is the way bugs are handled. They are closed as soon as the bug is fixed in SVN. Everything else is just impractical for developers.

Comment 6 Marcus Better 2007-08-15 20:53:48 UTC

> Sorry, but that is the way bugs are handled. They are closed as soon as the
> bug is fixed in SVN. Everything else is just impractical for developers.


Ok, I guess you are right then. However it would be good to check that the bug 
was indeed fixed by the rewrite. (The messages were certainly removed but the 
question is if the underlying problem remains.)

(What bothers me a bit is that core applications in KDE are too often allowed 
to carry serious bugs until they are rewritten from scratch, and the bugs are 
replaced with a set of new ones. But this is not the place to complain about 
that...)

Thanks for your work,

Marcus

Comment 7 Björn Ruberg 2010-01-03 11:26:19 UTC

My .xsessions-errors is always clean now. Can this be closed?