I managed to set up dual boot suse 8.2 and Win2k using grub. Got online using an adsl Brouter. I decided to download updates. Having done this things stop working and I cant log out so I have to switch off the power.
Things go fine until I try to run KDE i get the following message:
error setting up interprocess communications.
coul not read network connection list
/home/petercound/dcopserver_linux_0
please check that dcopserver program is running
It then refused to go any futher.

I can get into fwm and fwm2 and all the others. I dont seem to have Gnome loaded.Suse did give me a hint saying that I had shut down with out logging out and that I should delete "~/.dcop". Eh? I have no Idea.
Many thanks
Pete

Well "~/.dcop" refers to a file in your home directory called .dcop (with a dot). Just delete it with 'rm ~/.dcop' and see if it solves your problem.

You can check for the dcopserver running with command 'ps aux | grep dcop'. If no result, not running.

It's just possible your updates screwed up the KDE configuration, although the package system is supposed to protect you from things like that. N.B. dcopserver is the program that allows KDE applications to communicate with each other.

I got the exact same problem (in debian SID). The deleting solution doesn't work (no such file) Creating another user gives the same problem. Only root functions like it should in KDE.
I found a lot of post on other forums about this problem using google. Problem is, it doesn't get solved anywhere! Any clues?

Regards

Thanks.It did not work for me either, I have run out of disk space ( I dual boot with win 2k) I am going to allocate more space and reinstall suse.
Pete

i have the same problem, and unfortunately i havent found an answer either.
I created a new user to see if the problem stemmed from something i'd changed accidentally (or from just being a n00b) and it worked for a while, everything ran... then stupid me upgraded to the lastest KDE3.1.4 (i think thats the version number) and i had the same problem again!
Its driving me mad because i can't use and k apps unless im in root.

i formatted, and re installed debian get it all up and running and once again... i get the error... ps aux | grep dcop results come back... and then.. sometimes they dont.

the results that i go were these:

eviltama 645 0.0 0.1 1336 428 pts/0 S 19:21 0:00 grep dcop

not that they mean anything to me.

also something i noticed is an error abt a .ICE needing to be owned by root... i saw this a few times before i got the DCOP error.... any thoughts?

I have the same problem.. after "trying" to upgrade to KDE 3.1.5 from 3.1.0. Strange thing about it ... is that I didn't have this problem until AFTER I added the new directory for KDE into my PATH (/etc/profile)

But even after using vi within ICEwm and removing what I previously added to see if the error would go away, of course it didn't. It's still there.

But I also did add the PATH into my bash_profile (or bashrc- cant remember which it is).. in my Home directory. It didn't work when I added it into those Bash files, that's why I added it into the 'profile' file.

Also found the actual error message in my home directory, in a file called ".xsession-errors".

DCOP::AttatchInternal. Attatch failed Authentication Rejected, Reason: None of the Authentication Protocols specified are supported and host-based Authentication Failed.
Authentication Failed.

(as someone said before.. something about ICE, I have it too)
ICE Connection Rejected!
DCOPServer self-test failed.
sh: line 1 : iceauth : command not found.
kdeinit : DCOPServer could not be started, aborting.


UPDATE TO PREVIOUS
Someone mentioned just deleting the DCOP file in the home directory, but when I checked for it while in ICEwm using Terminal, it wasn't there. But I DO remember it being there previously to having the problem. Strange?

i came up with a solution... well actually i read it somewhere ages ago and it worked and i forgot to post it.. then when i happened again i was like *tearing hair out* so yeh..

the solution as i remember it was to delete .ICEauthority, .mcop , .mcoprc and the symbolic links between the kde files in /tmp. it was somethign like that anyway. The explaination i originally found went something along the lines of 'broken symbolic links' and 'it regenerates the files after a restart'... so yeh hope it helps someone else.

Brilliant! Months later and this post just saved me! Nice to have this forum around, I can login to root just fine again. (DCOP problem starting root after sudden power shut off, user worked fine root not, now aal is back to normal)

Regards

I tried this, but I'm still having trouble getting into KDE - I still get the same error about "couldn't start the .DCOPserver ... make sure it is running ..."