Version: 0.8.2 (using 4.2.2 (KDE 4.2.2), Kubuntu packages) Compiler: cc OS: Linux (i686) release 2.6.28-11-generic Steps: 1- Disable all okular debug output in kdebugdialog 2- Launch okular 3a- Open a png file 3b- Open a dvi file 3c- Open the bug report dialog Expected behaviour: No console output should be generated by actions 3a, b and c. Current behaviour: 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 etc. This makes okular rather annoying to use from a console.
Another example is when you change from a page to another one: GPL Ghostscript 8.64 (2009-02-03) Copyright (C) 2009 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Loading NimbusSanL-Regu font from /var/lib/defoma/gs.d/dirs/fonts/n019003l.pfb... 2579440 1075042 12354060 11022511 5 done. Loading StandardSymL font from /var/lib/defoma/gs.d/dirs/fonts/s050000l.pfb... 2579440 1123936 12374156 11044435 5 done.GPL Ghostscript 8.64 (2009-02-03) Copyright (C) 2009 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Loading NimbusSanL-Regu font from /var/lib/defoma/gs.d/dirs/fonts/n019003l.pfb... 2579440 1075042 12354060 11022511 5 done. Loading StandardSymL font from /var/lib/defoma/gs.d/dirs/fonts/s050000l.pfb... 2579440 1123936 12374156 11044435 5 done. 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...
(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.
(In reply to comment #2) > (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. The observation still holds - I don't have anything selected in kdebugdialog. I guess I'll report it as a kdelibs bug. > > > This makes okular rather annoying to use from a console. > > Ever heard of redirecting the standard error to /dev/null? > $ okular 2>/dev/null I shouldn't have to do that when the verbosity level has explicitly been set to the lowest possible. > > > 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. Interesting.
*** Bug 201926 has been marked as a duplicate of this bug. ***
SVN commit 1005981 by pino: make the gs kprocess collecct its output; disable an error message box (not doable in threads) BUG: 192405 M +5 -0 psgs.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1005981
SVN commit 1005983 by pino: make the gs kprocess collecct its output; disable an error message box (not doable in threads) will be in kde 4.3.1 CCBUG: 192405 M +5 -0 psgs.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1005983