Date: 11 Apr 1998 01:11:08 -0500 From: stephen farrell <stephen@farrell.org> To: "Jason C. Wells" <jcwells@u.washington.edu> Cc: questions@FreeBSD.ORG, kde-user@fiwi02.wiwi.uni-tuebingen.de, se@FreeBSD.ORG Subject: Re: kde on 2.2.5 CDROM? Message-ID: <87yaxcj3b7.fsf@phaedrus.uchicago.edu> In-Reply-To: "Jason C. Wells"'s message of "Fri, 10 Apr 1998 21:55:38 -0700 (PDT)" References: <Pine.BSF.3.96.980410215409.242A-100000@s8-37-26.student.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
"Jason C. Wells" <jcwells@u.washington.edu> writes: > On 11 Apr 1998, stephen farrell wrote: > > > "Jason C. Wells" <jcwells@u.washington.edu> writes: > > > > > I personnaly like the latest and greatest kde. I would install it this > > > way. > > > > > > Hmm... whenever I try to build this, kfm doesn't work. I get > > > > A new kioslave has been started > > QSocketNotifier: Invalid socket specified > > QSocketNotifier: Internal error > > > > whenever trying to open a directory. I got this when the beta3 port > > first came out. yesterday i blew it away and reinstalled, and i still > > get the same thing (yes i've confirmed that the binaries have been > > updated). > > I dunno. Hmm.. Ok... I see what the problem is: it has something to do with nfs. my home directory is mounted over nfs from a sparc/solaris box. when it creates ~/.kde/share/apps/kfm/kfm_0.0 over nfs, it's a FIFO, but if I make the kfm directory a link to a local filesyste, it (correctly) makes a socket... and everything works ok. Anyone know more about why this might be/other work-arounds besides making the tmp a link?. uname -s -r => FreeBSD 2.2.6-STABLE -- Steve Farrell 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?87yaxcj3b7.fsf>