By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1202 - tdelibs: Reduce xsession log spew
Summary: tdelibs: Reduce xsession log spew
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdelibs (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: Other All
: P1 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2012-09-05 20:46 CDT by Darrell
Modified: 2013-11-24 15:07 CST (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments
Partial patch to reduce xsession noise (6.94 KB, patch)
2012-09-05 20:47 CDT, Darrell
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2012-09-05 20:46:43 CDT
tdeinit (kinit.cpp) creates a lot of noise in the xsession log. Currently there is no mechanism to disable those messages. The biggest cuplrits are the following message types:

[tdeinit] Got EXEC_NEW....

[tdeinit] PID xxxx terminated.

[tdeinit] Got SETENV....

[tdeinit] xxxx is executable and not a library. Launching with exec.

The messages should be disabled by default and enabled only for debugging.

Attached is a partial patch. The patch attempts to convert the fprintf messages to kdDebug and creates a new kdDebug area: 182 tdecore (tdeinit). Although the patch builds without error, the new 182 messages do not appear in the xsession log even when explicitly enabled through kdebugdialog. There probably is something missing that the patch does not contain that prevents the messages from appearing.

This is a paper cut candidate.
Comment 1 Darrell 2012-09-05 20:47:21 CDT
Created attachment 809 [details]
Partial patch to reduce xsession noise
Comment 2 Darrell 2013-11-24 15:07:07 CST
I am closing this bug report. Bug 1710 is an appropriate place to handle this report because the output spew complaints are debugging messages.