I also had this problem.
Do this...
check in your /tmp directory for three directories:
mcop-<username>
ksocket-<username>
kde-<username>
where username is your login id.
If those exist, move them to something like
dirname.backup or whatever. Or just delete them.
They get created when you start KDE2.
Then try starting KDE2.1.1
Apparently KDE2 leaves those directories in /tmp and
doesn't clean them up. Once you move them or delete
them, kde2.1.1 will automatically create new ones.
Write back if you have any questions...
CD
--- Sterling Anderson
I get an error message when trying to start up KDE after upgrading to 2.1.1. I'm running SuSE 7.1 and was wondering if anyone else has experienced this. Installing the RPMs goes fine. Then I reboot hoping to load the new KDE but instead the GUI starts to load then I get dropped into a text logon prompt. If I type "startx" I get the following message box:
"error setting up inter-process communication for KDE. could not read network connection list. /root/.DCOPserver_[host name]_:0 check that dcopserver is running!"
If I go back to the text shell and try starting dcopserver by typing "dcopserver" it says "$DISPLAY not set". I have tried the bug database at kde.org but all I have found are people with the same problem who seem to fix it on their own and there are no solutions listed. Any other SuSe users have this problem? Thanks,
__________________________________ Sterling Anderson sterling@sterlinganderson.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
__________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/?.refer=text