You are not logged in.

DcopClient is gone!

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

kdepadiwan009

Beginner

  • "kdepadiwan009" started this thread

Posts: 1

  • Send private message

1

Friday, December 16th 2005, 3:37pm

DcopClient is gone!

I am using Suse 9 with KDE. I have tried to start applications but I keep getting the same error: "Klauncher could not be reached via DCOP"

I am unable to start hardly anything. If anybody has a thread that can help me or know what files to copy over from a Suse Install Disc, please let me know.

Here is the full error message when i try to start Kopete through a shell:

@linux:/> kopete
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/tom/.DCOPserver_linux__0
and start dcopserver again.
---------------------------------

DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
WARNING: DCOP communication problem!
kdeinit: Communication error with launcher. Exiting!
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
kopete: ERROR: KUniqueApplication: Can't setup DCOP communication.