dcopserver error when starting kde via kdm

[NicZak]

I just (finally) finished emerging kde (and all its dependencies), configuring my xf config, and emerging the nvidia drivers. I logged out, started kdm, which worked fine and when I entered my l/p and choose kde3 for the xserver, it popped a box with a dcopserver error, and exited... All it told me was to check and see if my software was installed properly. Anyone have any suggestions on how to remedy this, as well as why I would get that error? Thanks -

NicZak

[andee]

Hi

Does it happen for root too?
Try to clear /tmp,
maybe reboot

[NicZak]

I tried removing everything in my /tmp dir and that didn't prove to be the solution. I am trying to login to kdm as root but still no luck. The exact errors that I am recieving are the following - When I try to login (after kdm starts) as root (or any user) I get this: "Could not read network connection list. /root/.DCOPserver_# compname.domain.net__0 Please check that the "dcopserver" program is running!" After I click the 'OK' button on this dialog, I get another error which says: "Couldn't start ksmserver. Check your installation." After I click 'okay' on this window, the X server (kdm) restarts and I am back to the login screen. I am completely lost here, I don't have any .DCOPxxxx files in my /root or /tmp dir and I don't get any errors when just doing 'startx' and using the standard wm. Any help would be most appriciated! Thanks -
NicZak

[andee]

Hi
Check if /usr/kde/3/bin is in your path,
check if /tmp has sticky bit set, should be like that: drwxrwxrwt
check if there is /usr/kde/3/bin/startkde,
try start kde from text console like this: startx /usr/kde/3/bin/startkde.

[art]

I have installed Gentoo on 6 machines with very few problems(I use the 1.3b
stage3-Athlon). Last install went ok except kde has same error as NicZak.
Also when boot get message can't calculate dependencies.

[andee]

Try to move dot files in your home directory to another place
Maybe that helps

[Jason]

this seems a viable solution for my boxes... so i'll share it, but no promises. the issue seems to be with ownership of the home directory. first make sure you have a home directory, then chown -R it to the proper username. ie: for home directory /home/jason:

as root, cd /home
mkdir jason
chown jason jason

if you have stuff in the directory already you may want to chown -R

this worked for me, hopefully it helps somebody out

[Cleotis]

Well, i've encountered the same prob...

A solution proposed on the KDE-linux mailing list worked for me:

In your /etc/hosts and /etc/hostname files change mymachine.blahblah to just mymachine. And everything *should* be jiffy...