Bug 199781

Summary:	Excessive log-in times, > 20 seconds
Product:	[I don't know] kde	Reporter:	Freddie Witherden <freddie>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	kneczaj, nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Freddie Witherden 2009-07-11 15:52:15 UTC

Version:            (using KDE 4.2.4)
Compiler:          GCC 4.3 -O2
OS:                Linux
Installed from:    Gentoo Packages

When I log in the 'splash' screen appears almost instantly but it remains on the first icon (that of a hard disk) in excess of 20 seconds. There is a small amount of disk activity. After this the remaining icons appear very quickly and the login proceeds as expected.

I am unsure what is causing this delay, but would be happy to help in tracking down the cause in the hope of finding a solution. I suspect it could be some kind of I/O timeout, but am not sure.

Comment 1 Oswald Buddenhagen 2009-07-11 16:05:12 UTC

this might be due to some network timeout (e.g., failing dns lookup).

it's definitely no kdm problem, though.

Comment 2 Christoph Feck 2009-12-31 01:58:05 UTC

*** Bug 211115 has been marked as a duplicate of this bug. ***

Comment 3 Andrew Crouthamel 2018-11-02 22:55:40 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Andrew Crouthamel 2018-11-16 05:27:51 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!

Comment 5 Nate Graham 2020-09-28 23:35:54 UTC

No response; assuming it was fixed since then.