From owner-freebsd-current@FreeBSD.ORG Tue Apr 8 11:33:03 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E92737B401; Tue, 8 Apr 2003 11:33:03 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77E3743FCB; Tue, 8 Apr 2003 11:32:59 -0700 (PDT) (envelope-from adam@blacktabby.org) Received: from emmenthaler.blacktabby.org (12-240-109-159.client.attbi.com[12.240.109.159]) by sccrmhc03.attbi.com (sccrmhc03) with ESMTP id <2003040818325800300sdp8de>; Tue, 8 Apr 2003 18:32:58 +0000 Received: from cheshire.blacktabby.org (cheshire.blacktabby.org [192.168.1.198]) by emmenthaler.blacktabby.org (Postfix) with SMTP id 360473A91; Tue, 8 Apr 2003 11:32:58 -0700 (PDT) Date: Tue, 8 Apr 2003 11:32:57 -0700 From: Adam Kranzel To: Joe Marcus Clarke Message-Id: <20030408113257.31f29844.adam@blacktabby.org> In-Reply-To: <1049824834.360.17.camel@gyros> References: <20030408173003.84783.qmail@web11404.mail.yahoo.com> <1049824834.360.17.camel@gyros> X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: markus@freebsd.org cc: current@freebsd.org Subject: Re: fontconfig-2.1.92 considered harmful X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2003 18:33:03 -0000 On 08 Apr 2003 14:00:34 -0400 Joe Marcus Clarke wrote: > On Tue, 2003-04-08 at 13:30, Shizuka Kudo wrote: > > --- Ruslan Ermilov wrote: > > > On Tue, Apr 08, 2003 at 02:46:39PM +0200, CARTER Anthony wrote: > > > > I had this bug, but now it is over...It has been fixed. Do a CVSUP and all > > > > should now be ok. > > > > > > > No. This is with the latest port. Where specifically it > > > was fixed? > > > > > > > The exact cvs message is as follows. Having you tried 'fc-cache -f' to rebuild font cache as root > > in a text console and delete the fontcache in your home directory (This solved my problem when > > starting a KDE session)? > > But Ruslan is reporting the bug in 2.1.92 which incorporates this fix. > Besides, what Ruslan is seeing is a different crash. I'm wondering if > it is indeed an issue with not having enough memory. All my machines > have at least 512 MB of RAM, and I've never encountered this error. > Anyone have a machine with < 200 MB of RAM and is _not_ having a problem > with fontconfig? > > Joe I'm having no obvious trouble with it here (on a k6-2/500MHz with 192MB ram), I just updated to the latest version from ports this morning. All my programs seem to be working properly. -Adam