Kolja Kauder writes:
I'm having the same problems. I've submitted a report to SuSE some weeks ago without reaction. The only "useful" thing I found on the web was a comment along the lines of "You're having NFS-timeout problems" which didn't help very much.
Well in my case it's not NFS timeout. While on one machine my home directory is mounted over NFS, but if I log in to the NFS server's console where my home directory is local, the same thing happened. There is no NFS problem that I could detect either, everything is working over NFS as it should, and there are no NFS error messages in any log files.
I can't say exactly what kcminit does but killall'ing it continues the login process.
Yes, in my case killing the hung kcminit also makes the login work.
Some kde-services are then not activated, so that seems to be kcminit's function.
What kde services are not activated when you kill kcminit? I didn't notice anything missing...
Best rescue is to shutdown the X server (via killall startkde or Ctrl-Alt-Backspace while X is still reponding) and delete ~/.qt/.qtrc.lock . After that the problem disappears for some time.
I haven't tried that. Didn't think to look under ~/.qt. However by commenting out kcminit in the startkde script I am able to log in fine again for now. I am just curious what kcminit does and what I'm missing by not running it.
It usually reappears after unclean shutdowns (power outage, reset button,...) or sometimes for no reason at all. BTW, I subscribed to this mailing list uniquely to find a solution for this problem.
Yup, in my case it's for no apparent reason at all.
Ti Kan: The "again" suggests some history to this problem. Could you point me there?
I experienced this problem before when I was still running KDE 3.2.1, and not knowing that kcminit was the culprit I tried all sorts of things to try to "fix" it, like removing ~/.kde, /tmp/*-ti and /var/tmp/*-ti etc., all to no avail. I eventually "fixed" it by creating a whole new account, and then moving only the files I want over from the old account to it. I didn't see a problem again for a while, and then upgraded to KDE 3.3.0, thinking that perhaps it was due to a bug that is now fixed. However the problem recurred under KDE 3.3.0. I had posted a couple of questions on this list before and got a few answers, but none provided a workable fix.
-----Original Message----- From: Ti Kan [mailto:ti@amb.org] Sent: Saturday, August 21, 2004 6:24 PM To: suse-kde@suse.com; suse-linux-e@suse.com Subject: [suse-kde] KDE login hang again
KDE 3.3.0 on SuSE 9.1 here.
I am experiencing a hang at the splash screen again after logging in to KDE. This time, I've done a bit of debugging and found that the culprit is kcminit. In the /opt/kde3/bin/startkde script, there is a line:
LD_BIND_NOW=true kdeinit +kcminit +knotify
If I change this line to skip kcminit as follows, then I can log in just fine:
LD_BIND_NOW=true kdeinit +knotify