[Gllug] DCOP problem in Etch

[john gennard]

I've asked for help on Debian User and Kde lists - have had
some help, but things are quiet at the moment.

Just under two weeks ago I got Etch CD1 with Kde, and
installed this on three boxes and a laptop. All partitions
were formatted before installations which went fine. Then, I 
performed upgrades and updates. Three upgrades worked perfectly,
but one stalls at the commencement of the Kde initialisation
with this error message:-

------------
There was an error setting up inter-process communications
for Kde. The message returned by the system was:-
"Could not read network connection list 
/home/john/.DCOPserver_leary.clara.co.uk__0
Please check that the dcopserver program is running"
------------

It was suggested that running 'dist-upgrade' might help,
but it did not. (My '/etc/apt/sources.list' entries all
point to 'Etch' and not 'testing')

#ls -ld /tmp shows 'drwxrwxrwt 6 root  root  4096 etc' on
the problem box and 'drwxrwxrwt 7 root  root 4096 etc' on
all the other three installs. I think that means there is a
missing hard link on the problem box, but I don't know what
to do about correcting that (assuming my assumption is correct.

If I try to run 'kdeinit' from single user mode, I get:-

------------
Xsession: X session started for john at Tue Feb 20 15:17:57 GMT 2007
Link points to "/tmp/ksocket-john"
/usr/bin/iceauth: /tmp/dcopPfMg8b:1:  bad "add" command line
/usr/bin/iceauth: /tmp/dcopPfMg8b:2:  bad "add" command line
DCOPClient::attachInternal. Attach failed Authentication Rejected, 
reason : None of the authentication protocols specified are supported 
and host-based authentication failed
ICE Connection rejected!

DCOPClient::attachInternal. Attach failed Authentication Rejected, 
reason : None of the authentication protocols specified are supported 
and host-based authentication failed
DCOPServer self-test failed.
ICE Connection rejected!

kdeinit: DCOPServer could not be started, aborting.
------------

I've blundered around, googling, ensuring all relevant files
from 'kdelibs4c2a' appear where they should and trying to
find a visible difference between a working box and the problem
one but nothing appears to me. Frankly, I don't understand
how the Debian boot procedure works, so this precludes me
from going further.

Any ideas how I should continue. I don't want to reinstall if
I can help it.

Regards,

John.

-------------- next part --------------
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug