What happened? KDE wouldn't start; works now though

**t048** · 04-20-2003, 06:42 AM

That was weird. The computer went to screen saver and hung. I don't know why and I didn't make any changes to my system. So I [tt]alt + sys rq[/tt]'ed my way to a reboot.

Everything seemed to be fine until I tried to log back into KDE. It stayed on the "starting interprocess communication" step (the first icon on the ksplashscreen). After several seconds it would give me a dialog box saying it could not connect to the DCOP server.

I was able to log in other GUIs and in the shell and I was able to log into KDE as root and other users with out a problem. So I backed up my [tt]Documents[/tt] and [tt].kde/[/tt] directories and deleted my entire home directory. Then when I started KDE it worked just fine, but all of my settings were gone (obviously). So I copied my backed up [tt].kde/[/tt] directory back to my home directory and started kde again. It worked just fine. All my settings are restored and everything seems to be working normally.

Has anyone experienced this before? What did I do that caused the DCOP server to malfunction? I'm glad my system is working (for now), but I don't understand what happened. Any ideas? Thanks.

**pbharris** · 04-22-2003, 12:06 AM

hello,
i have heard of this happening when the /tmp directory gets full - or if tmp has another problem, but thats about it.

04-22-2003, 01:59 AM

well my advice is scrap the screensaver. I have used them in the past but they inevitabley case all sorts of problems. they have caused trouble in linux, windows, and mac for me and across three or four very generic boxes.

i now just let the screen go blank after 10 minutes and the hardrive spin down after 15 or so minutes of in activity