John, start with deleting all kinds of kde related files/directories, like; .DCOP*, .mcop*, .MCOP*, .kxmlrpcd, perhaps move the .kde* directories to a save place... It might help...., not sure though. Did you search the kde-user, and kdevel mailinglists at http://lists.kde.org? Op vrijdag 7 september 2001 22:00, schreef John Griffin:
During startup of X (KDE2 and SuSE7.1) I get the KDE2 splash screen with the message 'Setting up interprocess communication'.
Then I get an error pop-up window, with the following:
--------------------------------------------------------
| There was some error setting up inter-process | | communication for KDE. The message returned | | by the system was: | | | Could not read network connection list. | | | Please check that the "dcopserver" program is running! |
--------------------------------------------------------
Then KDE stops the startup process and the initial 'Setting Up Interprocess Communication' window goes away. I am left with a blank X screen no apps and no GUI capabilities.
I have another SuSE 7.1 machine that works fine in KDE2 and it does NOT have dcopserver running on it. So obviously it is not needed.
I cannot find any documentation on either machine via: $ man dcopserver $ man -k dcopserver $ find / -name "dcop*" (Only found document on the dcopserver.h include file).
Nothing in the SuSE Linux 7.1 Configuration Manual Nothing in the SuSE Linux 7.1 'The Handbook'
I executed the dcopserver command with the '--help' option and got the following: =========================================================================== === $ /opt/kde2/bin/dcopserver --help Usage: dcopserver [--nofork] [--nosid] [--nolocal] [--help]
DCOP is KDE's Desktop Communications Protocol. It is a lightweight IPC/RPC mechanism built on top of the X Consortium's Inter Client Exchange protocol. It enables desktop applications to communicate reliably with low overhead.
Copyright (C) 1999-2000, The KDE Developers http://www.kde.org =========================================================================== === No help here.
I searched the suse-linux-e database at geocrawler. about this mysterious dcopserver failure. There were a few people that had the exact same problem but no resolutions. One suggestion was to re-install the KDE2 apps again, which I did with no success.
Is this going to be another one of those fdisk,format, re-install (Nuke and Pave) solutions for SuSE? Or has somebody found a cure?
TIA, -jpg
-- Richard Bos For those who have no home the journey is endless