From owner-freebsd-ports Thu Aug 16 7: 1: 1 2001 Delivered-To: freebsd-ports@freebsd.org Received: from franklin.physics.purdue.edu (franklin.physics.purdue.edu [128.210.146.222]) by hub.freebsd.org (Postfix) with ESMTP id 2440837B408; Thu, 16 Aug 2001 07:00:58 -0700 (PDT) (envelope-from will@physics.purdue.edu) Received: from physics.purdue.edu (bohr.physics.purdue.edu [128.210.67.12]) by franklin.physics.purdue.edu (Postfix) with ESMTP id 7A73520F0A; Thu, 16 Aug 2001 09:02:06 -0500 (EST) Received: by physics.purdue.edu (Postfix, from userid 12409) id B6F705BC1; Thu, 16 Aug 2001 09:02:58 -0500 (EST) Date: Thu, 16 Aug 2001 09:02:58 -0500 From: Will Andrews To: Michael Collette Cc: will@FreeBSD.org, ports@FreeBSD.org Subject: Re: KDE2 DCOP problems Message-ID: <20010816090258.B28993@bohr.physics.purdue.edu> Reply-To: Will Andrews Mail-Followup-To: Michael Collette , will@FreeBSD.org, ports@FreeBSD.org References: <3B7B4AD6.E55E0AF7@metrol.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <3B7B4AD6.E55E0AF7@metrol.net>; from metrol@metrol.net on Wed, Aug 15, 2001 at 09:23:50PM -0700 X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Aug 15, 2001 at 09:23:50PM -0700, Michael Collette (metrol@metrol.net) wrote: > At this point I'm having a heck of a time getting KDE 2.2 to play > nice. The compile appears to have gone well, but whenever I try > launching a KDE application I'm getting DCOP communication errors. > I went in and renamed/deleted the following from my home directory... > > .DCOP* > .MCOP* > .kde > .kderc > .mcoprc > .mcop > > I also went and made sure that I didn't have anything in /tmp related > to that user. Stuff like ksocket-user and such. After doing all that, > still getting DCOP errors. Seems to be doing the exact same thing when > logged in as root. Where do you see DCOP errors? Since I use a *dm, I never see any errors printed on the console etc... XFree86.0.log provides no clues either. > I noticed that KDE 2.2 now does some stuff with FAM. I'm seeing some > errors as KDE gets going stating that various apps are unable to read > FAM. From what I read in the man page, FAM should be getting started > within inetd, though I haven't a clue what the config line in there > should look like. I tried running FAM as root manually, then launching > KDE as a regular user, but I still see errors relating to FAM not being > found. Might DCOP be dumping out because FAM isn't properly running as > an inetd service? FAM can run standalone too. I don't always use it and things work perfectly fine. Running konqueror in an aterm yields (after starting fam as root): kio (KDirWatch): KDirWatch processing FAM event (FAMChanged, .xwm.msgs, Req 1) kio (KDirWatch): KDirWatch emitting fileDirty /home/will/.xwm.msgs -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message