From owner-freebsd-questions Tue Oct 30 14:41: 3 2001 Delivered-To: freebsd-questions@freebsd.org Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81]) by hub.freebsd.org (Postfix) with ESMTP id 3C0D937B401 for ; Tue, 30 Oct 2001 14:40:59 -0800 (PST) Received: from [213.123.131.130] (helo=there) by tungsten.btinternet.com with smtp (Exim 3.22 #6) id 15yhYy-0000VT-00; Tue, 30 Oct 2001 22:40:52 +0000 Content-Type: text/plain; charset="iso-8859-1" From: Dominic Marks To: "Mark" , "Questions FreeBSD" Subject: Re: KDE DCOP Error Date: Tue, 30 Oct 2001 22:43:50 +0000 X-Mailer: KMail [version 1.3] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -----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