From owner-freebsd-gnome@FreeBSD.ORG Fri Jan 23 14:37:35 2004 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6522816A4CF for ; Fri, 23 Jan 2004 14:37:35 -0800 (PST) Received: from bgruber.isa-geek.com (pool-68-161-159-30.ny325.east.verizon.net [68.161.159.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DD9943D1D for ; Fri, 23 Jan 2004 14:37:04 -0800 (PST) (envelope-from lists@bgruber.isa-geek.com) Received: from bgruber.isa-geek.com (bgruber.isa-geek.com [127.0.0.1]) by bgruber.isa-geek.com (8.12.10/8.12.10) with ESMTP id i0NMf43m017628 for ; Fri, 23 Jan 2004 17:41:04 -0500 (EST) (envelope-from lists@bgruber.isa-geek.com) Received: (from lists@localhost) by bgruber.isa-geek.com (8.12.10/8.12.10/Submit) id i0NMf460017627 for freebsd-gnome@freebsd.org; Fri, 23 Jan 2004 17:41:04 -0500 (EST) (envelope-from lists) Date: Fri, 23 Jan 2004 17:41:04 -0500 From: Brian Gruber To: freebsd-gnome@freebsd.org Message-ID: <20040123224104.GA17607@bgruber.isa-geek.com> Mail-Followup-To: freebsd-gnome@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Received: from bgruber.isa-geek.com (bgruber.isa-geek.com [127.0.0.1]) by bgruber.isa-geek.com (8.12.10/8.12.10) with ESMTP id i0NKhZ3D017112 for ; Fri, 23 Jan 2004 15:43:35 -0500 (EST) (envelope-from lists@bgruber.isa-geek.com) Received: (from lists@localhost) by bgruber.isa-geek.com (8.12.10/8.12.10/Submit) id i0NKhZ9D017111 for freebsd-gnome@freebsd.org; Fri, 23 Jan 2004 15:43:35 -0500 (EST) (envelope-from lists) Subject: mozilla dns bug returned? X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2004 22:37:35 -0000 Hiya, Does anyone remember mozilla bug 70213, where one bad dns lookup locked everything up? It hasn't bugged me in a long time, but from the looks of it, it seems to have returned w/ moz 1.6. Which is odd, since according to the bug page it was fixed in 1.6alpha. Anyone else seen this? /brian