Hi - With the new update to KDE, the applications appear to print much more debugging information to the console, most of which is useless to the user.
This is a problem when trying to run applications from the command line (e.g. okular when using LaTeX) as simple operations on the KDE application spawn reams of debugging on the user's console.
Is there some way of switching it off? I notice most of this goes to .xsession-errors anyway, so it doesn't seem worthwhile duplicating it all.
Thanks
Jeremy
On 3 March 2010 09:15, Jeremy Sanders jeremy@jeremysanders.net wrote:
Hi - With the new update to KDE, the applications appear to print much more debugging information to the console, most of which is useless to the user.
Run kdebugdialog and tick "disable all debug output", which in practice will actually only disable most of the debug output but still helps. :)
I think this is going to be made default in upcoming versions ...
MEF
On Wed 3 March 2010 2:58:14 am Mary Ellen Foster wrote:
I think this is going to be made default in upcoming versions ...
Boo, why is that? Most users don't give a cruft about the debug info, and if they file a bug report, we can ask them to turn on kdebudialog only for that application.
If the move to enable kdebug by default is an upstream move, I'm tempted to suggest that we override it.
Ryan
On 03/03/2010 12:06 PM, Ryan Rix wrote:
On Wed 3 March 2010 2:58:14 am Mary Ellen Foster wrote:
I think this is going to be made default in upcoming versions ...
Boo, why is that? Most users don't give a cruft about the debug info, and if they file a bug report, we can ask them to turn on kdebudialog only for that application.
If the move to enable kdebug by default is an upstream move, I'm tempted to suggest that we override it.
I interpreted that "disable all debug output" was going to be the default therefore working the way you describe it. I may be wrong though.
Ryan
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On Wed, Mar 03, 2010 at 03:23:32PM -0400, Patrick Boutilier wrote:
On 03/03/2010 12:06 PM, Ryan Rix wrote:
On Wed 3 March 2010 2:58:14 am Mary Ellen Foster wrote:
I think this is going to be made default in upcoming versions ...
Boo, why is that? Most users don't give a cruft about the debug info, and if they file a bug report, we can ask them to turn on kdebudialog only for that application.
If the move to enable kdebug by default is an upstream move, I'm tempted to suggest that we override it.
I interpreted that "disable all debug output" was going to be the default therefore working the way you describe it. I may be wrong though.
This is what I understood, too, because currently the debug output is not disabled by default. But please make this default.
Regards Till
On Wed 3 March 2010 12:23:32 pm Patrick Boutilier wrote:
I interpreted that "disable all debug output" was going to be the default therefore working the way you describe it. I may be wrong though.
Yeah, someone file a bug on my bad logic parser, apologies. :)
2010/3/4 Ryan Rix ry@n.rix.si
On Wed 3 March 2010 12:23:32 pm Patrick Boutilier wrote:
I interpreted that "disable all debug output" was going to be the default therefore working the way you describe it. I may be wrong though.
Yeah, someone file a bug on my bad logic parser, apologies. :)
-- Ryan Rix == http://hackersramblings.wordpress.com | http://rix.si/ ==
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Would the extra verbosity in the terminal output decrease performance?
-
Jeremy Sanders -
Mary Ellen Foster -
Mitchell Richters -
Patrick Boutilier -
Ryan Rix -
Till Maas