From owner-freebsd-current@FreeBSD.ORG  Sat Feb 28 18:08:21 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 10B2816A4CE
	for <current@freebsd.org>; Sat, 28 Feb 2004 18:08:21 -0800 (PST)
Received: from root.org (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id D1F6D43D1F
	for <current@freebsd.org>; Sat, 28 Feb 2004 18:08:20 -0800 (PST)
	(envelope-from nate@root.org)
Received: (qmail 99354 invoked by uid 1000); 29 Feb 2004 02:08:22 -0000
Date: Sat, 28 Feb 2004 18:08:22 -0800 (PST)
From: Nate Lawson <nate@root.org>
To: Joe Marcus Clarke <marcus@marcuscom.com>
In-Reply-To: <1078019158.18071.12.camel@shumai.marcuscom.com>
Message-ID: <20040228180719.W99350@root.org>
References: <20040228152618.C98870@root.org>
	<1078019158.18071.12.camel@shumai.marcuscom.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: mozilla hanging on gconfd2 startup?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Feb 2004 02:08:21 -0000

On Sat, 28 Feb 2004, Joe Marcus Clarke wrote:
> On Sat, 2004-02-28 at 18:27, Nate Lawson wrote:
> > I can't seem to start mozilla after upgrading the port today.  It
> > starts a process called gconfd2 which never completes.  I'm running
> > a current as of Friday.
>
> Weird.  Seems Mozilla will try to use gconf2 if found (this is neither a
> compile-time nor runtime dependency).  However, all of the GConf methods
> are unimplemented.  The gconf hang problem may be related to the recent
> reentrant resolver patches so rebuilding devel/gconf2 should fix the
> problem.

This doesn't work.

> Another solution would be to set
>
> user_pref("accessibility.unix.gconf2.shared-library", "xxx_goaway");
>
> in your Mozilla prefs.js file.  This will stop Mozilla from loading
> gconfd in the future.

This worked fine.

-Nate