Hello, what is the reason that many applications clutter the terminal with output that is obvisously debug output? Lets take digikam as an example:
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_klauncher.so Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(Q kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_kconf_update Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(Q Time elapsed: 29 ms close(34) in netlib_connectsock() Time elapsed: 9 ms Model: Time elapsed: 64 ms TextureColorizer: Time elapsed: 19 ms Time elapsed: 5 ms close(42) in netlib_connectsock() And about 50 more lines are following just to start the application. Or take iceweasel. After some time hundreds of gdk warnings are filling your terminal. What is the reason for this kind of output? A typical end user don't understand the output. Furthermore it shadows useful messages or edge them out of the history list. That behaviour puzzles me for some time now. It doesn't seem to be very unix-like. Regards hmw -- biff4emacsen - A biff-like tool for (X)Emacs http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html Flood - Your friendly network packet generator http://www.c0t0d0s0.de/flood/flood.html -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87y6c98489....@stella.c0t0d0s0.de
