[Okular-devel] [Bug 192405] Debugging information is output regardless of settings in kdebugdialog

[Pino Toscano]

https://bugs.kde.org/show_bug.cgi?id=192405





--- Comment #2 from Pino Toscano <pino kde org>  2009-05-12 10:39:09 ---
(In reply to comment #0)
> The console is polluted by debug information such as:
> 
> Calling appendChild() on a null node does nothing.
> 
> okular(3853) KToolInvocation::invokeBrowser: Using "/usr/bin/xdg-open" to open
> "http://bugs.kde.org/wizard.cgi?os=Linux%20%28i686%29%20release%202.6.28-11-generic&compiler=cc&kdeVersion=4.2.2%20%28KDE%204.2.2%29%2C%20Kubuntu%20packages&appVersion=0.8.2&package=okular&kbugreport=1"
> 
> kdeinit4: preparing to launch /usr/bin/kded4

All of those comes from kdelibs.

> This makes okular rather annoying to use from a console.

Ever heard of redirecting the standard error to /dev/null?
$ okular 2>/dev/null

> Another example is when you change from a page to another one:
> 
> GPL Ghostscript 8.64 (2009-02-03)
> [...]
> 
> and so forth. For every single page (!). I'm too scared to look at the source
> code to see whether you're really calling ghostscript for every page...

If you are reading a DVI file which embeds external .ps or .eps files, then
Ghostscript is called whenever needed (during the page rendering). Nothing
weird.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.