KDE3 error - DCOPServer could not read network...

Message

stevenpharris · Post by **stevenpharris** » Sun May 05, 2002 10:14 pm

Goggle search / KDE list info didn't resolve, I guess my last resort is 'emerge unmerge kde' then an emerge...

After launching kdm and attempting a login to KDE3: 'There was some error setting up inter-process communication for KDE.

The message returned by the system was:' 'Could not read the network connection list. /root/DCOPserver_<hostname>_:0' 'Please check that the "dcopserver" program is running!'

Any advice would be greatly appreciated.

theanimal666 · Post by **theanimal666** » Mon May 06, 2002 10:35 am

add following line to the startkde script in /usr/kde/3/bin

export KDEDIR=/usr/kde/3/

and try again, that solved the problem for me...

elboricua · Post by **elboricua** » Fri May 31, 2002 7:01 am

export KDEDIR=/usr/kde/3/

That is already in the startkde script. I too am having the same error. Please post if you find a fix!!

Sivar · Post by **Sivar** » Thu Jul 04, 2002 10:22 pm

I can use KDE as root only. When I try to use KDE with any other user, I get this same error. When I was setting up KDE for the new user, every other screen KDE would complain that DcopServer wasn't running. Once KDE tried to start, it locked up at "Starting interprocess communication."

Sivar · Post by **Sivar** » Thu Jul 04, 2002 10:37 pm

Solution found:

- After logging on (or trying to) a second time, KDE complains that it cannot start "ksmserver"
- I executed dmsserver, which I found using "updatedb" then "locate ksmserver" (location is /usr/kde/3/bin/ksmserver)
- ksmserver complained about me not being able to open "/tmp"
- I changed the group of /tmp to "users" and then used "chmod g+w /tmp" to add write permission to /tmp for every user who is a member of the group "users" (who now owns /tmp)

Works fine now.