Bug 280178

Summary:	KIO should not display console output when it is disabled in kdebugdialog (and preferably by default).
Product:	[Unmaintained] kdelibs	Reporter:	Peter Lewis <pete>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	cubranic, faure, kdelibs-bugs-null
Priority:	NOR
Version First Reported In:	4.7
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Peter Lewis 2011-08-16 10:24:57 UTC

Version:           4.7 (using KDE 4.7.0) 
OS:                Linux

As discussed in bug report 280123, KIO produces lots of output on the console in some circumstances. A specific example is when trying to refresh a PDF file in Okular, if that file does not exist:

% okular ~/work/file.pdf
okular(15885)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know
"/home/pete/work"
okular(15885)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know
"/home/pete/work"
okular(15885)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know
"/home/pete/work"
okular(15885)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know
"/home/pete/work"
...

and so on.

I have disabled all output in kdebugdialog.



Reproducible: Always

Steps to Reproduce:
Open okular from the terminal. Remove the PDF it is viewing.

(While this might sound an odd thing to do, it's what happens when you're
generating a PDF file using latex. If I'm in vim on the console, then all the
output gets spewed all over my vim session if it fails to compile.)

Actual Results:  
There is text on the console.


Expected Results:  
There should be no text output.

Comment 1 David Faure 2012-01-19 23:28:48 UTC

This isn't related to kdebugdialog, it's a warning. kdebugdialog's checkbox only disables all *debug* statements, which is one level below warnings.

So either okular shouldn't call removeEntry wrongly, or kdirwatch is confused somehow.

Hmm, I can't reproduce this warning with okular 0.13.80 / KDE 4.7.97. This must have been fixed by now. Please reopen if it's not.

Comment 2 Peter Lewis 2012-01-19 23:35:21 UTC

Yes, this seems to have been fixed now. Thanks :-)