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 645

Summary:	reading '.kompmgr.pid' as kompmgr pidfile
Product:	TDE	Reporter:	Darrell <darrella>
Component:	tdebase	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	minor	CC:	bugwatch, darrella, kb9vqf, michele.calgaro
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Other
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Attachments:	tdelibs: Change when output message appears and add module identifier for logs tdebase: Change when output message appears and add module identifier for logs

Description Darrell 2011-11-19 12:22:31 CST

TDE provides its own compositor. When the feature is disabled, the following error message nonetheless appears when starting TDE:

reading '/home/users/tester/.kompmgr.pid' as kompmgr pidfile

The message should not appear when the compositor is disabled.

Second, the message is inconsistently formatted compared to other TDE xsession messages. There is no prefix in the message disclosing what process generated the message.

Paper cut candidate.

Comment 1 Darrell 2012-02-29 21:46:57 CST

Created attachment 448 [details]
tdelibs: Change when output message appears and add module identifier for logs

Comment 2 Darrell 2012-02-29 21:48:22 CST

Created attachment 449 [details]
tdebase: Change when output message appears and add module identifier for logs

Both of these patches should avoid sending the message when kcomp is disabled.

Comment 3 Darrell 2013-03-02 18:31:44 CST

Patch in attachment 448 [details] pushed in GIT commit b2f40800.

Comment 4 Darrell 2013-03-02 20:27:18 CST

Patch in attachment 449 [details] pushed in GIT commit febcc863.

Comment 5 Michele Calgaro 2014-03-04 22:05:03 CST

Darrell, I see you pushed a couple of patches about a year ago. Do them resolve this bug (i.e. can we close it)?

Comment 6 Darrell 2014-03-05 12:56:59 CST

I don't use compositing and never have, which, if I remember correctly, is when the messages were occuring. I don't recall seeing the messages in my xsession-errors log for a long time, but I haven't looked for that message either.

Whether the message appears when compositing is enabled is another question.

I don't remember how to create the required environment to test the bug report.

There are two related bug reports: bug 880 and bug 887.

This is a problem with the current bug reporting system --- we ignore bug reports for months and years. After excessively long periods even the original bug reporter struggles to remember the details.

Comment 7 Timothy Pearson 2014-11-18 16:03:09 CST

(In reply to Darrell from comment #6)
> I don't use compositing and never have, which, if I remember correctly, is
> when the messages were occuring. I don't recall seeing the messages in my
> xsession-errors log for a long time, but I haven't looked for that message
> either.
> 
> Whether the message appears when compositing is enabled is another question.
> 
> I don't remember how to create the required environment to test the bug
> report.
> 
> There are two related bug reports: bug 880 and bug 887.
> 
> This is a problem with the current bug reporting system --- we ignore bug
> reports for months and years. After excessively long periods even the
> original bug reporter struggles to remember the details.

Ignoring the reports is not intentional or really a decision on any of the developers' part--real life gets in the way; none of us are pulling anything resembling a paycheck from this project. ;-)

Remaining spurious messages removed in GIT hash 586eb3b.

Tim