Date: Tue, 26 Mar 2002 02:04:17 -0800 (PST) From: Annelise Anderson <andrsn@andrsn.stanford.edu> To: Mark Hummel <mhumm2@mchsi.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: What is a DCOPserver and What function Do They Serve??? Message-ID: <Pine.BSF.4.10.10203260150530.99653-100000@andrsn.stanford.edu> In-Reply-To: <20020325225125.CGFB1219.sccmmhc01.mchsi.com@there>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 25 Mar 2002, Mark Hummel wrote: > It took me 2 hours to even figure out how to pose this question because my > symptoms are so intermittent. I can't even find a man page about these files > nor can I find anything in my fbsd books. > > My desire is to boot directly to KDE, but I don't want to set that up until I > can get it to work manually the first time and every time. > > I have a cable modem set up with my LinkSys NIC which fbsd does recognize > quite well as dc0. > > mhumm2# dmesg|grep dc0 > dc0: <LC82C115 PNIC II 10/100BaseTX> port 0xe000-0xe0ff mem > 0xd5501000-0xd55010ff irq 11 at device 10.0 on pci0 > dc0: Ethernet address: xx:xx:xx:xx:xx:xx > miibus0: <MII bus> on dc0 > > Running startx begins to bring up the KDE start screen, but then > the error occurs: > > There was an error setting up inter-process > communication for KDE. The message returned > by the system was: > > /root/.DCOPserver_mhumm2_:0 > Please check that the "dcopserver" program is running! > > When I click on "ok", I'm sent back to terminal text mode. If I wait for > about 1 minute, I can startx again and stand a 50-50 chance of everything > working fine (except a fatal sound error, but that's another post). > > Sometimes it's 1 retry and sometimes it takes 3, but eventually, KDE does > come up without a dcopserver error. Here are my config files: I do not know the intricacies of these arrangments. My experience with X-4 and KDE is that the setup gets confused if startx is run as root when the user has used the su -m switch, thus keeping in place environment variables such as the user's home directory. The result is a bunch of authentication files of some sort (.Xauthority, .DCOP-this and .DCOP-that, plus some .MCops and some .ICE* stuff, that is owned by root (with group of the user) and all this is just confusing for KDE. There are maybe some sockets also created with "mixed ownership." Fixing the ownership does not seem to help, but deleting these files (as root) and then starting X with startx as a user does seem to work. Or X could be started as root with root environmental variables--echo $HOME should produce /root. In generally deleting all these files (.Xauth*, etc.) and letting X and KDE recreate them seems to work. Annelise -- Annelise Anderson Author of: FreeBSD: An Open-Source Operating System for Your PC Available from: BSDmall.com and amazon.com Book Website: http://www.bittreepress.com/FreeBSD/introbook/ 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?Pine.BSF.4.10.10203260150530.99653-100000>