Version: 3.4.91 (using KDE Devel) Installed from: Compiled sources Compiler: gcc 4.0.2 OS: Linux When deleting /var/tmp/kdecache-user, user cannot log into KDE anymore. The first attempt results in the message "Could not start process Cannot talk to klauncher" to be shown in a kdialog while loading the panel. The login process seems to hang from there on. The following attempts result in a xdialog saying "Could not start ksmserver. Check your installation". I ran into this problem because I used to have /var/tmp in a tmpfs, which worked fine for KDE 3.3 and 3.4.
I've seen this happen.
I had a similar symptom but only because I had remove the 2 syscoca files in /var/tmp/kdecache-user
Right, that's the symptom. If you run kbuildsycoca it works again.
SVN commit 465681 by lunakl: Don't try to indirectly cause launching of kbuildsycoca from a call that's supposed to launch kbuildsycoca. BUG: 113203 M +10 -7 klauncher.cpp --- branches/KDE/3.5/kdelibs/kinit/klauncher.cpp #465680:465681 @@ -1143,13 +1143,16 @@ request->startup_id = startup_id; #endif request->envs = envs; - // Find service, if any - strip path if needed - KService::Ptr service = KService::serviceByDesktopName( app.mid( app.findRev( '/' ) + 1 )); - if (service != NULL) - send_service_startup_info( request, service, - startup_id, QValueList< QCString >()); - else // no .desktop file, no startup info - cancel_service_startup_info( request, startup_id, envs ); + if( app != "kbuildsycoca" ) // avoid stupid loop + { + // Find service, if any - strip path if needed + KService::Ptr service = KService::serviceByDesktopName( app.mid( app.findRev( '/' ) + 1 )); + if (service != NULL) + send_service_startup_info( request, service, + startup_id, QValueList< QCString >()); + else // no .desktop file, no startup info + cancel_service_startup_info( request, startup_id, envs ); + } request->transaction = dcopClient()->beginTransaction(); queueRequest(request); return true;