From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 25 22:48:53 2010 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D8C5106568B for ; Mon, 25 Jan 2010 22:48:53 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id B4C1E8FC18 for ; Mon, 25 Jan 2010 22:48:51 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 4FABABDC43 for ; Mon, 25 Jan 2010 14:48:50 -0800 (PST) To: freebsd-gnome@freebsd.org Date: Mon, 25 Jan 2010 14:48:50 -0800 Message-ID: <37358.1264459730@tristatelogic.com> From: "Ronald F. Guilmette" Subject: Firefox3 printing woes X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 22:48:53 -0000 Hello, Would any of you chaps happen to have any suggestions for solving the firefox3 garbled fonts printing problem? I've been living with this problem for quite a long time now... probably more than a year... just by continuing to have both firefox3 _and_ firefox2 installed on my system. (I use the latter whenever I know I'm going to need to print something.) It appears that I'm not the only one who has ever experienced this problem. (Far from it, apparently.) It's been discussed at length and was the subject of PR #ports/128694, and also, apparently, Mozillia bug #411831. I've tried the various suggested fixes, to wit: 1) Adding: Option "XaaNoOffscreenPiaxmaps" "True" to my xorg.conf file 2) setting my LANG environment variable to en_US.ISO8859-1 (it had been defaulted to the value "C") 3) performing a print-preview first, before actually printing None of these things actually helped any. :-( I'm very eager to find a solution for this problem, so any suggestions would be appreciated. (I'm not even sure why ports/128694 was closed. It's not at all clear, since there appears to have been no definitive resolution to the issue.) Please reply on-list, elsewise my dumb spam filtering may not allow me to see your reply. Thanks. Regards, rfg