Bug 216627

Summary:	kdm.log gets filled with lots of KConfigIni errors, trying to read files in "/"-dir as config files.
Product:	[Unmaintained] kdm	Reporter:	Stephan Wezel <s.wezel>
Component:	general	Assignee:	kdm bugs tracker <kdm-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	mpyne
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Stephan Wezel 2009-11-29 11:46:27 UTC

Version:            (using Devel)
Compiler:          gcc (Gentoo 4.3.4 p1.0, pie-10.1.5) 4.3.4 
OS:                Linux
Installed from:    Compiled sources

Yesterday (28.Nov 2009) i updated my live build of kde4. (revision 1056015 of kdebase/workspaces) Since then kdm hangs on start and the kdm.log gets big (file size several MBs).
Most lines in kdm.log are as follows:

"KConfigIni: In file /linuxrc, line 42: " Invalid entry (missing '=') 
"KConfigIni: In file /linuxrc, line 43: " Invalid entry (missing '=') 
"KConfigIni: In file /swapfile, line 1: " Invalid entry (missing '=') 
"KConfigIni: In file /swapfile, line 2: " Invalid entry (missing '=') 
"KConfigIni: In file /swapfile, line 4: " Invalid entry (missing '=') 
"KConfigIni: In file /swapfile, line 5: " Invalid entry (missing '=') 
"KConfigIni: In file /swapfile, line 7: " Invalid entry (missing '=') 
"KConfigIni: In file /swapfile, line 8: " Invalid entry (missing '=') 

As you can see KConfigIni tries to open files in the /-dir as a config file. The strange thing is, that this ony happens when kdm gets started via the start-stop-daemon executable used bye the xdm start-script in gentoo.
When i start kdm directly as root the problem is gone. But the package which has the start-stop-daemon was last updated on 16. Nov. 2009. So it can't be the source of the problem, because previouse version of kdm/kdelibs (installed on 22. Nov. 2009) worked without problems.

The question is why does KConfigIni tries to load files in the /-dir as a config file.

Comment 1 Oswald Buddenhagen 2009-12-19 10:33:52 UTC

these messages don't come from kdm, but from one of the programs started by it, possibly by Xstartup or Xsetup, or maybe krootimage (kdm's "built-in" background in unthemed mode).
the problem as such looks like a wildcard gone wild - e.g., something to the effect of $CONFIGDIR/* with an empty variable. that could be caused by a broken build => wipe build dir and retry.

Comment 2 Michael Pyne 2015-08-30 23:26:53 UTC


*** This bug has been marked as a duplicate of bug 334845 ***