From owner-freebsd-questions Wed Jun 16 12:43:12 1999 Delivered-To: freebsd-questions@freebsd.org Received: from neuman.interaccess.com (neuman.interaccess.com [207.70.126.130]) by hub.freebsd.org (Postfix) with ESMTP id CCABB1526E for ; Wed, 16 Jun 1999 12:43:07 -0700 (PDT) (envelope-from fordp@guide.chi.il.us) Received: from prefect (d149.focal8.interaccess.com [207.208.189.149]) by neuman.interaccess.com (8.9.0/8.9.0) with SMTP id OAA04399 for ; Wed, 16 Jun 1999 14:43:05 -0500 (CDT) Message-Id: <3.0.3.32.19990616144209.00712cf8@pop.interaccess.com> X-Sender: fordp@pop.interaccess.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 16 Jun 1999 14:42:09 -0500 To: freebsd-questions@freebsd.org From: Ford Prefect Subject: gnome-session on FreeBSD 3.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've recently loaded FreeBSD 3.2 on my machine and found I have a problem using gnome-session. Under FreeBSD 3.0 (The last version I've tried this on) I've had my xinitrc simply exec gnome-session and had gnome handle, loading of my window manager, panel and whatever else. Under FreeBSD 3.2 that isnt' working, infact, if I do the following in an xterm: gnome-session & gnome-smproxy the gnome-smproxy fails because it cannot connect to the session manager. I've checked all the config files I know of for X and gnome and can't find any problems, I also checked it against My Redhat 6.0 setup and didn't find any noteable differences. so my question is: is this a known problem? if yes, is there a fix? if no, are there any ideas why it is not working for me? Thanks -Steve *=====================================================* \ Ford Prefect Ahead of my time. \ \ fordp@guide.chi.il.us but only by a week. \ \ homepage.interaccess.com/~fordp \ \ \ \ ((In esperanto where available)) \ *=====================================================* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message