Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Aug 2001 02:04:10 -0700
From:      Michael Collette <metrol@metrol.net>
To:        will@FreeBSD.org
Cc:        ports@FreeBSD.org
Subject:   Re: KDE2 DCOP problems [Update]
Message-ID:  <3B7B8C8A.8AA20B43@metrol.net>
References:  <9lfhpg$27sh$1@FreeBSD.csie.NCTU.edu.tw>

next in thread | previous in thread | raw e-mail | index | archive | help
Due to the kind help of Jeremy Norris and John Cooper in private E-Mails
I now have FAM running properly out of inetd.  This has solved many of
the error messages that I was seeing at the initial run up of KDE, but
the DCOP problem remains.  Apparently the two problems are unrelated.
Before I get into the DCOP thing, here's the basic fix for FAM.

Add the following to /etc/rpc
sgi_fam         391002

Add the following to /etc/inetd.conf
sgi_fam/1-2     stream  rpc/tcp wait    root    /usr/local/bin/fam
fam

Then type...
killall -HUP inetd

This gets FAM working very nicely and all, but I'm still getting the
following DCOP error as I type in kcontrol.

# kcontrol
kcontrol: Found basegroup = Settings/
ERROR: KUniqueApplication: DCOP communication error!

  Still dead in the water over here so far as KDE is concerned.  I'm
still mucking around with it, but not seeing any effect to the errors
described.  Been asking folks on IRC about this, but nobody seems to be
having this problem on the Linux side of the house.

  BTW, are there any plans for adding to the default config files for
FreeBSD to account for these FAM changes that I had to do?  Even when I
finally get my copy of KDE going here, having to do all these file edits
is really going to suck for the next guy.  It seems there's some changes
needed for a more elegant solution that goes beyond the scope of the
ports tree, and certainly over my head.  Ideally a user should be able
to simply do a "make install" for kde2 and not have to worry about
configuring what is sure to be a rather obscure dependancy for most
folks.  I haven't a clue how something like this would be properly dealt
with, but I thought I'd mention it as a fairly major usability issue.

Later on,
--
----------------------------
Metrol
- metrol@metrol.net
-- http://www.metrol.net/
----------------------------
Off the keyboard, thru the router, over the bridge, nothing but net!



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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B7B8C8A.8AA20B43>