Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Oct 2001 21:35:31 -0600
From:      Rob Zietlow <zietlow@berbee.com>
To:        Dominic Marks <dominic_marks@btinternet.com>, "Mark" <meinreinhof@mep.nist.gov>, "Questions FreeBSD" <freebsd-questions@FreeBSD.ORG>
Subject:   Re: KDE DCOP Error
Message-ID:  <200110310335.f9V3Zdf21292@berbee.com>
In-Reply-To: <E15yhYy-0000VT-00@tungsten.btinternet.com>
References:  <JPEELEKOHJAADFDHOEOFOECPCBAA.meinreinhof@mep.nist.gov> <E15yhYy-0000VT-00@tungsten.btinternet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I have experienced this ever since I upgraded to kde 2.2.1  I get it whenever 
I reboot my lappy

On Tuesday 30 October 2001 04:43 pm, Dominic Marks wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tuesday 30 October 2001 8:55 pm, Mark wrote:
> > "There was an error setting up inter-process communications for KDE. The
> > message returned by system was:
> >
> > Could not read network connection list.
> > /home/h43euf/.DCOPserver_tester.mep.nist.gov_:1
> >
> > Please check that the 'dcopserver' program is running!"
> >
> > I get this error after first bootup and typing startx for the first time.
> > I click ok, wait a few, type startx and KDE runs normally.
> >
> > FreeBSD 4.4
> > KDE - what comes with above.
> >
> >
> > ****************************
> > LT Mark Einreinhof
> >
> > US Air Force
> > Peterson AFB, CO
> > Communications Officer
> > mark.einreinhof@cisf.af.mil
> > (W)719-556-2209
> >
> > Dept of Commerce, NIST/MEP
> > Gaithersburg, MD
> > Guest Researcher
> > meinreinhof@mep.nist.gov
> > (W)301-975-3591
> > (C)240-793-0024
> > ****************************
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message
>
> I get the same problem, as do another 3 people I've spoken to. Its
> intermitant however. I've spoken to Will Andrews about it, but as he has
> never experienced such a problem so he doesn't have any ideas. I normally
> find that when this does occur I can fix it by deleting the socket and
> retrying, alternatively I have tried deleting /tmp/.ICE_unix/ (IIRC thats
> the name of the directory) with limited success.
>
> - --
> Dominic
> Need a Unix Admin/Programmer? I'm cheap, mail me.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (FreeBSD)
> Comment: For info see http://www.gnupg.org
>
> iD8DBQE73y0qu6vC63o8YzERAmCXAKCYPGXsfPgAkzgNaf/VgNGO+AOvQACgjh5J
> JF5SThelG4NpHlcCgPks1iY=
> =XYxj
> -----END PGP SIGNATURE-----
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110310335.f9V3Zdf21292>