https://bugs.kde.org/show_bug.cgi?id=192405
--- Comment #3 from Pierre-Francois Laquerre <pierre francois gmail com> 2009-05-12 11:51:06 --- (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. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
