From owner-freebsd-gnome@FreeBSD.ORG Mon Jun 21 03:19:55 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 EC65016A4CE for ; Mon, 21 Jun 2004 03:19:55 +0000 (GMT) Received: from lightandmatter.com (lightandmatter.com [64.246.48.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE61743D41 for ; Mon, 21 Jun 2004 03:19:55 +0000 (GMT) (envelope-from bcrowell@lightandmatter.com) Received: (from bcrowell@localhost) by lightandmatter.com (8.11.6/8.11.6) id i5L3OXo14694 for gnome@FreeBSD.org; Sun, 20 Jun 2004 22:24:33 -0500 Date: Sun, 20 Jun 2004 22:24:33 -0500 From: Ben Crowell To: gnome@FreeBSD.org Message-ID: <20040620222433.A14633@lightandmatter.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: bug in pango port 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: Mon, 21 Jun 2004 03:19:56 -0000 Hi, There seems to be a serious bug in the current version of the pango port. Presently, I find that if I do a `make deinstall ; make reinstall' of pango (as demanded by various ports that want the new version of pango), the result is a broken version of pango. Attempting to run any app that uses pango then gives something like this: Error reading modules file ** (audacity:41939): WARNING **: No builtin or dynamically loaded modules were found. Pango will not work correctly. This probably means there was an error in the creation of: '/usr/X11R6/etc/pango/pango.modules' You may be able to recreate this file by running pango-querymodules. All the text in these applications then shows up as dots rather than text. Following the advice in the error message does not fix the problem, and in fact the file already exists, and points to a directory full of modules. To fix a system that's been bitten by this bug, the only solution I've found is to restore /usr/X11R6/lib, /usr/local/lib, and /usr/X11R6/etc from backup. The /usr/X11R6/etc directory seems to be the one containing the data files that pango is upset about. All of this is on a FreeBSD 5.2 system that's been cvsup-ed recently. Thanks in advance for anything you can do to fix this problem! Ben Crowell