Date: Wed, 31 Oct 2001 01:13:42 -0500 From: Zach Hartley <zhartley@linus.highpoint.edu> To: Questions FreeBSD <freebsd-questions@FreeBSD.ORG> Subject: Re: KDE DCOP Error Message-ID: <20011031011342.A22101@linus.highpoint.edu> In-Reply-To: <E15yhYy-0000VT-00@tungsten.btinternet.com>; from dominic_marks@btinternet.com on Tue, Oct 30, 2001 at 10:43:50PM %2B0000 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've been getting this problem for the past week too, but I never had it before... I usually just rm .DCOP* .ICE* .MCOP* and it magically goes away. Zach >Around Tue, Oct 30, 2001 at 10:43:50PM +0000, Dominic Marks said something to the effect of: > -----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 -- Zachary Todd Hartley "Attempted murder. Now honestly, what is that? Do they give a Nobel Prize for attempted chemistry?" --Sideshow Bob 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?20011031011342.A22101>