Re: DCOP problem after Etch with Kde upgrade
On Thu, Feb 15, 2007 at 16:03:37 +0000, john gennard wrote:
> About a week ago I obtained the latest Etch (Kde version)
> from Debian.org and installed it without any problems.
>
> Yesterday I updated and upgraded the installation - took
> many hours on a dialup connection (60 Mb, 58 packages,
> mainly Kde - no packages were deleted). There were no
> problems reported with the upgrading.
>
> At the next boot, the Kde Desktop starts to come up and
> then stops with the following 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/.DCOPserverleary_clara.co.uk__0.
> Please check that the dcopserver program is running."
> ------------
>
> I don't understand DCOP, but have ascertained there is no
> .DCOPsever file in /home/john as there is on two other boxes
> running Etch (these need upgrading, but I'm hesitant to do
> so as I feel this problem can be due only to the upgrade).
>
> How is the file created and how do I find out if the DCOPserver
> is running?
The DCOP server should be started directly by kdeinit; DCOP is the
communication protocol of the various KDE components and programs (see
http://en.wikipedia.org/wiki/Dcop). If KDE is running you should see
something like this:
$ ps -ef | grep [d]cop
florian 18725 1 0 19:10 ? 00:00:00 dcopserver [kdeinit] --nosid
(This command does not help you at the moment since your KDE does not
start up at all if I understand you correctly.)
The DCOP server itself is responsible for creating the file that is
mentioned in your error message (as far as I know).
Something fundamental seems to be wrong with your KDE. With Etch being
frozen I would not expect that a dist-upgrade can make a difference, but
I would try it nevertheless. You might simply have an inconsistent
combination of KDE packages right now, with some old packages still
hanging around. (Upgrading at the wrong moment could also cause a
situation like this; in such a case another upgrade at a later time
might be enough to fix everything.)
--
Regards,
Florian
Reply to: