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 296

Summary:	[stdout/stderr] New Trinity Profile Error Messages
Product:	TDE	Reporter:	Darrell <darrella>
Component:	system	Assignee:	Timothy Pearson <kb9vqf>
Status:	NEW ---
Severity:	normal	CC:	bugwatch, darrella
Priority:	P3
Version:	R14.0.x [Trinity]
Hardware:	All
OS:	All
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Bug Depends on:
Bug Blocks:	2968

Description Darrell 2010-10-01 16:52:22 CDT

When starting Trinity for the first time, which creates a new profile, the following messages appear in the xsession-error log:

Invalid entry (missing '=') at /tmp/kde-root/kconf_updateDxWEba.tmp:1
Invalid entry (missing '=') at /tmp/kde-root/kconf_updateVC8cVa.tmp:1

Occurs for both root and non-root users.

The messages seem to occur only with a new Trinity profile and only with the first run of Trinity.

The messages likely are caused because the cache, socket, and tmp profile directories used by Trinity do not yet exist and the underlying code is trying to create those directories. That part makes sense, but the error message indicates something like a typo or something similar in the code. That is, the missing profile directories should get created without any error messages.

Comment 1 Darrell 2011-11-19 01:19:20 CST

This bug still exists in 3.5.13.

Paper cut candidate.

Comment 2 Darrell 2011-11-30 15:06:54 CST

Looking in /tmp/kde-root there are many tmp files created by kconf_update. Those files will match the temp names seen in the oddball stdout message. Looking at the contents of those files reveals one of the suspect files causing the error message is kopete_pluginloader.pl.

I don't know if this is a parsing error with kconf_update or a syntax error in kopete_pluginloader.pl.

Comment 3 Darrell 2012-01-27 14:50:50 CST

These messages appear when using the tdm login manager because kconf_update runs then. Therefore the tdm.log will always contains these obtuse errors.

Comment 4 Darrell 2013-11-25 12:01:00 CST

This bug still exists in R14.