From owner-freebsd-x11@FreeBSD.ORG Wed Jan 23 17:49:56 2008 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE09616A419 for ; Wed, 23 Jan 2008 17:49:56 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from QMTA05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 8DA7713C46A for ; Wed, 23 Jan 2008 17:49:56 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA05.westchester.pa.mail.comcast.net with comcast id ggGA1Y0050mv7h0050Bl00; Wed, 23 Jan 2008 17:49:55 +0000 Received: from discordia ([24.60.136.97]) by OMTA11.westchester.pa.mail.comcast.net with comcast id ghpv1Y00526FYqY3X00000; Wed, 23 Jan 2008 17:49:55 +0000 X-Authority-Analysis: v=1.0 c=1 a=IRfY8P9jjPKBxe9fpjIA:9 a=xSp1FqRu-TF5y6CMa68A:7 a=CP00uzoHDdrWdeHVd1nKGUBwn3YA:4 a=pt045V2O6wwA:10 Received: by discordia (Postfix, from userid 103) id 351CA16B55B; Wed, 23 Jan 2008 12:49:55 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.20.1.3] (erwin.int.cokane.org [172.20.1.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by discordia (Postfix) with ESMTP id EBC3416B557; Wed, 23 Jan 2008 12:49:39 -0500 (EST) Message-ID: <47977DC2.7090907@FreeBSD.org> Date: Wed, 23 Jan 2008 12:47:46 -0500 From: Coleman Kane Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071116) MIME-Version: 1.0 To: "Aryeh M. Friedman" References: <478BA1CE.7020101@gmail.com> <478BCD2A.4040405@gmail.com> <478C1522.6010108@FreeBSD.org> <478C305E.6050900@paradise.net.nz> <478C7A24.2030104@gmail.com> In-Reply-To: <478C7A24.2030104@gmail.com> X-Enigmail-Version: 0.96a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-x11@FreeBSD.org Subject: Re: fonts have gone insane X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@FreeBSD.org List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2008 17:49:57 -0000 Aryeh M. Friedman wrote: > Mark Kirkwood wrote: > > Coleman Kane wrote: > >> > >> I'm in the same boat here. It would seem that all of the fonts in my > >> GTK/GNOME apps are messed up now and I am left with replacements of > >> some > >> core fonts. Seems to have coincided with some recent portupgrade, > >> but I > >> can't figure out what has done it. I recently upgraded > >> x11-toolkits/gtk20 but the original poster mentions xfce... > >> > >> Trying to rebuild/install fontconfig... > >> > >> I tried the above removal of the /var/db/fontconfig directory which > >> helped out none. > >> > >> > > I ran into this with the Gnome 2.20 upgrade. I believe it has > > something to do with anti-aliased fonts being used instead of bitmap > > ones. I *think* it is to do with Xorg 7.3 rather than Gnome.... but > > there is Gnome stuff you can do that sorts it if Gnome is your > > window manager (see thread "Fonts, windows too large after 2.20 > > upgrade" in freebsd-gnome list). > > > For other window managers I'm not sure what you need to do (there > > must be some xorg.conf magic - surely???). Maybe ask on the Xorg > > mailing lists? (and enlighten us when you discover the answer!) > > After redoing a buildworld on sources that have been updated by new > stuff committed during th portupgrade -afk the problem has cleared it > self (I need to undo some changes I made to my settings) I also took your suggestion, and performed a csup and then rebuilt world/kernel and installed. Now my fonts seem to be back to normal in my GNOME apps. Any idea wtf caused this? I am guessing that these apps needed to communicate with gconfd in order to get their run-time-configured font information... maybe the changes in the tree prevented this from happening? -- Coleman Kane