Bug 314759

Summary: KDM confused by large text files in root directory
Product: [Unmaintained] kdm Reporter: Ameretat Reith <ameretat.reith>
Component: generalAssignee: kdm bugs tracker <kdm-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: serhiy.int
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ameretat Reith 2013-02-09 14:10:02 UTC
I had a large text file (18MB) in root directory. After kdm-4.9.5 compilation, I noticed, it takes more time to show me text fields to login.

This is KDM's log:

------------ START OF FILE BLOCK ------------
20574206 "KConfigIni: In file /list, line 1: " Invalid entry (missing '=')
20574207 "KConfigIni: In file /list, line 2: " Invalid entry (missing '=')
20574208 "KConfigIni: In file /list, line 3: " Invalid entry (missing '=')
20574209 "KConfigIni: In file /list, line 4: " Invalid entry (missing '=')
.
.
.
20854985 "KConfigIni: In file /list, line 140390: " Invalid entry (missing '= ')
------------ END OF FILE BLOCK ------------

The file caused problem - which was named /sort but I've renamed it to check whether problem again occurs - has e syntax like this:

------------ START OF FILE BLOCK ------------
1 /usr/portage/media-plugins/gst-plugins-dv/gst-plugins-dv-0.10.31.ebuild
2 /usr/portage/metadata/md5-cache/dev-python/pydns-3.0.2
3 /usr/portage/media-sound/omptagger/omptagger-1.0.3.ebuild
4 /usr/portage/metadata/md5-cache/dev-java/netbeans-nb-7.1.2
------------ END OF FILE BLOCK ------------

I wonder why KDM should read these files.

Reproducible: Always

Steps to Reproduce:
1. make a text file like /item and put it in /.
2. make it large buy concatenating.
3. try to (re)start KDM.
Actual Results:  
KDM takes much time to load.

Expected Results:  
KDM start fast.

Delete the file and KDM starts fast.
Comment 1 Serhiy 2014-10-17 13:12:06 UTC
There is a duplicate for this bug: https://bugs.kde.org/show_bug.cgi?id=314759
Why are KDE bugs the slowest to get any developers attention?
Note to self: try getting rights to change bug status.
Comment 2 Christoph Feck 2014-10-25 17:18:32 UTC
> Why are KDE bugs the slowest to get any developers attention?

Bad luck. KDM does not have any maintainer, that's why you do not see replies. For areas where we have maintainers, you will usually get replies within two weeks.

You can certainly request bug triaging rights, but if you are just going to mark this bug as a duplicate of bug 314759, we will retract the rights ;)

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