Kevin Krammer posted on Wed, 09 Nov 2011 09:17:48 +0100 as excerpted: > On Tuesday, 2011-11-08, Duncan wrote: > >> For some reason kde folks seem to believe developers are the only ones >> to run kde apps from a shell session to try to troubleshoot, and many >> kde apps have so many terrible looking messages even when they're >> running normally, that unless you've run them normally and know what >> the output looks like in ordered to be able to ignore the noise and >> pick out the differences (if you have a system that's working and one >> that's not, with the same version, you can diff the output and see >> what's different between them, thus getting something useful), it's >> virtually useless. > > All non-warning, non-error output should be controlled by KDE's debug > area mechanism, e.g. changable through kdebugdialog. > > Also globally by changing the kdebugrc at global level.
Thank you! =:^) I've not looked at it yet, but that sounds like what I've been looking for, for awhile. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___________________________________________________ This message is from the kde-linux mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde-linux. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
