adept manager produces an error DCOP Communicationss error "there was an error s

[odindio]

adept manager produces an error DCOP Communicationss error "there was an error setting up inter process communications for KDE. The Message returned by the system was: could not open Network Socket.

Please check to see that DCOP server program is running!

[Rog131]

Re: adept manager produces an error DCOP Communicationss error "there was an err

Is there dcopserver running ?

K > System > KSysGuard: Search - dcopserver
or in the konsole:

:~$ ps -e | grep dcopserver

man dcopserver tells:

DCOPSERVER(1) DCOPSERVER(1)

NAME
dcopserver — KDE DCOP server

SYNOPSIS
dcopserver [--nofork] [--nolocal] [--nosid] [--suicide]

dcopserver [--serverid]

DESCRIPTION
This manual page documents briefly the dcopserver command.

dcopserver is the server for KDE’s Desktop Communications Protocol.

OPTIONS
This program follows the usual GNU command line syntax, with long
options starting with two dashes (‘-’). A summary of options is
included below.

--nofork Causes dcopserver not to fork off like a daemon, but run in
the current process.

LinuxQuestions.org > Linux Wiki > DCOPserver has couple solutions:
http://wiki.linuxquestions.org/wiki/DCOPserver

"There was an error setting up inter-process communication for KDE. The message returned by the server was: Could not read network connection list. /home/user/.DCOPserver_machine__0 Please check that the "dcopserver" program is running!"

If you just installed your distro or KDE, then probably some libraries were not correctly installed and a new installation might be necessary.

If your machine has been shut down uncleanly while you were logged in as a user, and can no longer log in as that user (other users working well), then log in as another user, copy its .DCOPserver file to the home of the broken user (note that the number at the end of the file name refers to the KDE session, first being 0, second being 1 etc... so in this situation, put a 1 instead of a 0 at the end), open a new session and log in as that user. This time it should work. Note that the .DCOPserver file contains a PID so the other user should still be logged in when you are doing this.

If you previously messed up your home directory, this problem might arise because the .DCOPserver file cannot be written (check permissions of the file and the parent directory). In some cases, the problem was solved by deleting the .DCOPserver file.

Resetting all files to your user in your home folder:

sudo chown -Rv <user>.<user> /home/<user>

<user> is your login name.

man chown:

CHOWN(1) User Commands CHOWN(1)

NAME
chown - change file owner and group

SYNOPSIS
chown [OPTION]... [OWNER][:[GROUP]] FILE...
chown [OPTION]... --reference=RFILE FILE...

DESCRIPTION
This manual page documents the GNU version of chown. chown changes the
user and/or group ownership of each given file. If only an owner (a
user name or numeric user ID) is given, that user is made the owner of
each given file, and the files’ group is not changed. If the owner is
followed by a colon and a group name (or numeric group ID), with no
spaces between them, the group ownership of the files is changed as
well. If a colon but no group name follows the user name, that user is
made the owner of the files and the group of the files is changed to
that user’s login group. If the colon and group are given, but the
owner is omitted, only the group of the files is changed; in this case,
chown performs the same function as chgrp. If only a colon is given,
or if the entire operand is empty, neither the owner nor the group is
changed.

Links:

Topic: Konqueror Browser Can Browse Only as ROOT
http://kubuntuforums.net/forums/inde...opic=3084031.0

[Guest]

Re: adept manager produces an error DCOP Communicationss error &quot;there was an error s

I had the same problem plus the Alt+F2 window was invisible. Deleting the .DCOPserver* files solved the problems! Thank you!