Upgrade of Etch fails - no inter-process communications
I obtained Etch Kde-CD-1 (i386), snapshot dated 20070205.
and installed this on three boxes and a laptop. All partitions
were formatted before installation which all went fine. Then, I
performed updates and upgrades. 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.
All boxes are self built and substantially the same as regards
hardware.
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 ensured from 'kdelibs4c2a' that all relevant packages
appear where they should and I failed to find a visible difference
between a working box and the problem one but nothing occurs to me.
Frankly, I don't understand how the Debian boot procedure works and
I don't know how or from where DCOP is started, so this precludes
me from going further.
However,I ensured that all packages on the running boxes are
on the broken box and that there are no left over packages on
the broken box.
Debian - Installer RC1 was broken on 20070210, but as upgrades
before and after the problem arose were fine I can't understand
how that can be relevant.
I could reinstall using the latest snapshot, but I'd prefer to
have this problem solved if possible.
My basic knowledge is very shallow and I've now done all the
blundering around that I can. Can anyone tell me how to get
the inter-process communications working, please.
John.
Reply to: