mozilla hanging on gconfd2 startup?

Kris Kennaway kris at obsecurity.org
Sun Feb 29 21:05:17 PST 2004


On Sun, Feb 29, 2004 at 05:07:42PM -0800, Nate Lawson wrote:

> > > So it does appear that the hostname is the issue.  However, on a mozilla
> > > 1.5 and a -current of a few weeks ago, this was not a problem.  So what
> > > changed?
> >
> > The gconf "dependency" was most likely added in 1.6.  The solution to
> > this is to add your local hostname to /etc/hosts (that's the common
> > answer to GNOME users encountering this lock in gconfd).  If you don't
> > want to do that, the pref trick is another valid workaround, but I think
> > the hostname thing makes more sense.
> 
> Attempts to add the hostname as 127.0.0.1 and the actual IP resulted in a
> hang in the same place.  A tcpdump of both lo0 and fxp0 show no more DNS
> queries so the hosts entry was definitely being used.  A telnet to the
> hostname also shows that the lookup succeeds.  Since there were no
> segments of TCP or UDP, I'm at a loss why it is blocking still.

I came into the thread late, but is this related to green's recent
commits breaking binary compatibility of the libc DNS resolver?

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040229/c22e08c2/attachment-0001.bin


More information about the freebsd-current mailing list