From owner-freebsd-x11@FreeBSD.ORG Mon May 17 21:54:13 2010 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22D05106564A for ; Mon, 17 May 2010 21:54:13 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id D28E98FC0C for ; Mon, 17 May 2010 21:54:12 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o4HLsBDe072680; Mon, 17 May 2010 15:54:11 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id o4HLsBfW072677; Mon, 17 May 2010 15:54:11 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 17 May 2010 15:54:11 -0600 (MDT) From: Warren Block To: "J. Altman" In-Reply-To: <20100517211520.GA99190@chanas.pair.com> Message-ID: References: <20100517004537.GA91382@chanas.pair.com> <20100517200412.GB52057@server.vk2pj.dyndns.org> <20100517211520.GA99190@chanas.pair.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.5 (wonkity.com [127.0.0.1]); Mon, 17 May 2010 15:54:11 -0600 (MDT) Cc: freebsd-x11@freebsd.org Subject: Re: I am...unimpressed with this newest upgrade of X X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2010 21:54:13 -0000 On Mon, 17 May 2010, J. Altman wrote: > I only know that suddenly, at least two applications are crashing. My > post to -questions basically asks if anyone else is seeing the same > issue; so far, no one else seems to be seeing the issue with > Seamonkey. > > I have no idea if it's an issue for the FreeBSD maintainers; the > Seamonkey maintainers; or the X maintainers. Seamonkey has not changed > in some time; X has. So I suspect it's the X maintainers, most likely, > that will need to investigate and push relevant changes downstream to > FreeBSD. Seeing as how there have been recent sweeping changes to jpeg, xorg, and now GNOME and KDE, it would be nice to verify exactly where the problem lies. A failed upgrade might be at fault, or even a successful one. pkg_libchk from the sysutils/bsdadminscripts port is worth running. >> Note that there was a "call for testing" for Xorg 7.5 in mid-March >> which allowed some of the rough edges to be corrected before it was >> actually committed. >> >> You might like to consider taking part in similar testing in future. > > Doubtful. That would require multiple machines. Or multiple hard drives. Or even just an additional partition for a test install. The nice thing about prerelease testing is that it gives you an early warning if there's a compatibility issue with your actual hardware. -Warren Block * Rapid City, South Dakota USA