From owner-freebsd-questions@FreeBSD.ORG Mon Jul 28 11:17:15 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D81237B407 for ; Mon, 28 Jul 2003 11:17:15 -0700 (PDT) Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7008243F85 for ; Mon, 28 Jul 2003 11:17:14 -0700 (PDT) (envelope-from jeff+sender+e8ec28@jrpenn.demon.co.uk) Received: from jrpenn.demon.co.uk ([194.222.241.254]) by anchor-post-33.mail.demon.net with esmtp (Exim 3.35 #1) id 19hCYZ-000BQh-0X for freebsd-questions@freebsd.org; Mon, 28 Jul 2003 19:17:13 +0100 Received: from jrpenn.demon.co.uk (localhost [127.0.0.1]) by jrpenn.demon.co.uk (Postfix) with ESMTP id DF4E71F00 for ; Mon, 28 Jul 2003 19:13:51 +0100 (BST) Received: by jrpenn.demon.co.uk (tmda-sendmail, from uid 1001); Mon, 28 Jul 2003 19:13:51 +0100 (BST) Date: Mon, 28 Jul 2003 19:13:51 +0100 To: freebsd-questions@freebsd.org Message-ID: <20030728181351.GA1208@jrpenn.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.4.1i From: Jeff Penn Mail-Followup-To: freebsd-questions@freebsd.org X-Delivery-Agent: TMDA/0.80 (Determine) Content-Transfer-Encoding: quoted-printable Subject: Xfree86 debugging X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2003 18:17:15 -0000 I have been unable to run an X client+server on 4.8 release for several weeks due to what appears to be a known issue. The problem surfaced a=20 few days after my weekly port upgrade (none of the upgrades were X=20 related - the previous weeks upgrade did update an X port, but I'm not certain which). Google found two similar issues, one appears to be due to using -O2 optimisation with gcc3.3 to compile freetype on Debian. The other=20 message was in the xfree86 fonts mailing list archive: That's expected behaviour with current CVS, which is not internally consistent. Both the freetype and the type1 backends register for PostScript fonts; whichever you get depends on the order they=20 register. Could you please try again after applying http://www.pps.jussieu.fr/~jch/software/files/ xfree86-f=F8nts-=FEri=F8rit=FD-2002=B9025.=FE=E3tch Assuming it works today, it will cause the freetype backend to get Type 1 fonts, and the type1 backend to get CFF fonts. The patch is no longer available, & the author of the above email did=20 not respond to a request for more information. I emailed the maintainer of freetype2 a couple of weeks ago but have not yet had any response. Up to now I have used packages for XFree86. Last week I tried re- installing X using the ports in a desperate attempt to resolve the=20 issue. I have also tried disabling some of the modules loaded by /etc/XF86Config-4 to narrow down the problem. Any suggestions what I should do next?. Is there anything I can do to=20 be more pro-active in resolving this issue, or do I assume that the=20 problem is with freetype2 & a patch is in the pipeline?. thanks Jeff