From owner-freebsd-current Sat Dec 6 18:48:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA08552 for current-outgoing; Sat, 6 Dec 1997 18:48:31 -0800 (PST) (envelope-from owner-freebsd-current) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA08540 for ; Sat, 6 Dec 1997 18:48:21 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id VAA15918; Sat, 6 Dec 1997 21:48:19 -0500 (EST) Date: Sat, 6 Dec 1997 21:48:19 -0500 (EST) From: John Fieber To: Stephen Hocking cc: current@freebsd.org Subject: Re: Oddity with netscape and current In-Reply-To: <199712070237.MAA00763@zzshocki.dialin.uq.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 7 Dec 1997, Stephen Hocking wrote: > > Also from the archives, adding this: > > > > export XCMSDB; XCMSDB=/dev/null > > > > to the netscape startup script solved hang-on-start problem for [snip] > This appears to have done the trick. Nutscrape had been working fine > for me for ages though, which is why I was a little puzzled about it starting > to mess up after a src update. For the record, the problem which this solves/works-around exists in FreeBSD-2.2.5/XFree86-3.3.1 as well as (I gather) current (and what version of X?). I'm using a 16 bit display and have not tried it on 8 or 24. The reports on what works with what combinations of FreeBSD, Netscape, and X11 have been rather inconsistent--some curious methods of suppressing the symptoms have been discovered but does anyone have a clue about the problem? -john