From owner-freebsd-questions Tue Mar 3 06:37:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16674 for freebsd-questions-outgoing; Tue, 3 Mar 1998 06:37:31 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA16483 for ; Tue, 3 Mar 1998 06:36:17 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id PAA14654; Tue, 3 Mar 1998 15:30:53 +0100 Message-ID: <34FC13DC.7FDB3CF6@we.lc.ehu.es> Date: Tue, 03 Mar 1998 15:29:48 +0100 From: "Jose M. Alcaide" Organization: Universidad del País Vasco - Dep. de Electricidad y Electrónica X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.5.1 sun4u) MIME-Version: 1.0 To: Doug White CC: freebsd-questions@FreeBSD.ORG Subject: Re: KDE 3.1b compiles on 2.2.5, but it doesn't work References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > > On Wed, 25 Feb 1998, Jose M. Alcaide wrote: > > > BUT, my KDE 3.1b continues to fail at startup. KFM hangs, and I > > see the error messages > > > > QSocketNotifier: Invalid socket specified > > QSocketNotifier: Internal error > > > > whenever I try to start any application from the panel menu. > > Mine works fine, so I have absolutely no idea. > I have discovered some interesting facts about my KDE 3.1b problems: I can run KDE from any account that resides on a local disk, but it fails when it's run from NFS-mounted homedirs (we have a Solaris NFS server for user directories). Then, I thought that the problem could be related to the creation of named UNIX sockets in the NFS-mounted filesystem, so I searched for any socket in the .kde directory built by KDE when started from the local disk, and I found two sockets at ~/.kde/share/apps/kfm, named "kfm_0.0" and "kio_0.0". However, these same files are created as **named pipes** (!?!) when KDE is started from the NFS-mounted home directory. Then I wrote a tiny program that creates a named UNIX socket. I ran it, from both local and NFS-mounted directories, and it created named sockets in both cases without any problem. In summary, I think that the KDE problem is related to the NFS-mounting of the user account, but my little program creates sockets in the remote filesystem, so I don't know what happens. I would like to know if other people running FreeBSD boxes as NFS clients can reproduce this problem with KDE. Any ideas? -- JM ----------------------------------------------------------------------- Jose M. Alcaide | mailto:jose@we.lc.ehu.es Universidad del Pais Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electronica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-4-4647700 x2624 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-4-4858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message