From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Iky2I-0007Pp-FQ for garchives@archives.gentoo.org; Thu, 25 Oct 2007 08:25:50 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.1/8.14.0) with SMTP id l9P8OUKq032039; Thu, 25 Oct 2007 08:24:30 GMT Received: from alnrmhc14.comcast.net (alnrmhc14.comcast.net [204.127.225.94]) by robin.gentoo.org (8.14.1/8.14.0) with ESMTP id l9P8JxHp026893 for ; Thu, 25 Oct 2007 08:19:59 GMT Received: from spore.ath.cx ([24.245.14.14]) by comcast.net (alnrmhc14) with ESMTP id <20071025081958b1400e9laae>; Thu, 25 Oct 2007 08:19:58 +0000 Received: from pascal.spore.ath.cx (pascal.spore.ath.cx [192.168.1.100]) by spore.ath.cx (Postfix) with ESMTP id 8167B17E8 for ; Thu, 25 Oct 2007 03:19:57 -0500 (CDT) Date: Thu, 25 Oct 2007 03:19:57 -0500 From: Dan Farrell To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Emerge firefox 2.0.0.8 and now printing is hosed Message-ID: <20071025031957.1419bfe2@pascal.spore.ath.cx> In-Reply-To: <9acccfe50710242100s2c390bcdx975fc8426bc6f67f@mail.gmail.com> References: <9acccfe50710242005s41d1d8f8q9c63bbfd8af4eaf0@mail.gmail.com> <4ef07b8c0710242023y37071393xbd25331d71eb4f1@mail.gmail.com> <9acccfe50710242100s2c390bcdx975fc8426bc6f67f@mail.gmail.com> Organization: Spore, Ltd. X-Mailer: Claws Mail 3.0.0 (GTK+ 2.10.14; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 4c35644c-fd82-4b48-8e6c-cdc422ef5528 X-Archives-Hash: 0cc2a64fe2d9fe4a6b024ddb3b87f13a On Wed, 24 Oct 2007 21:00:14 -0700 "Kevin O'Gorman" wrote: > It's a gentoo ebuild, so I start here. For all I know, it was > something that happened here. I agree with you there. Besides, I just upgraded to firefox-2.0.0.8 as well, and I have no such problems... although it was firefox-bin i686, I still feel relatively confident that it's not firefox's fault, at least not completely. -- gentoo-user@gentoo.org mailing list