FS#4712 - font cache must be refreshed for font config changes to take effect

Attached to Project: Arch Linux
Opened by name withheld (Gullible Jones) - Saturday, 27 May 2006, 02:47 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 27 May 2006, 05:41 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I discovered this when enabling bitmap fonts so that I could use the artwiz-fonts package... After linking 10-bitmaps.conf to yes-bitmaps.conf in /etc/fonts/conf.d, you have to rebuild your font cache. Until the font cache is rebuilt, changes in /etc/fonts/conf.d will fail to take effect. This isn't a huge thing, but it's definitely of some annoyance value.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 13 October 2006, 19:51 GMT
Reason for closing:  Fixed
Additional comments about closing:  Bitmap fonts are enabled by default again now.
The "bug" you were seeing was a result of the fact that fc-cache skips bitmap fonts while scanning for them when they are disabled. Hinting differences are applied after an application restart, or when applied using xsettings instantly where possible.
Comment by name withheld (Gullible Jones) - Saturday, 27 May 2006, 03:04 GMT
My bad, just refreshing the font cache doesn't do it. In order for font config changes to take effect, YOU MUST REINSTALL THE FONTCONFIG PACKAGE. Yes, I am completely serious.
Comment by name withheld (Gullible Jones) - Wednesday, 31 May 2006, 11:00 GMT
It looks like the xset thing is the one that does the trick... Problem is it only works when X is running, other than in the install script, as far as I can tell.

Also, with this last install I tried installing fontconfig first, then turning on bitmap fonts and reinstalling it... Still doesn't work, you need to have X installed when you reinstall fontconfig.

Really, why did this behavior change? There's no way that it's supposed to be this way...
Comment by name withheld (Gullible Jones) - Saturday, 17 June 2006, 20:31 GMT
Update: this bug can only be reproduced when Gnome is installed. It appears that some part of Gnome really messes up some part of XOrg.
Comment by name withheld (Gullible Jones) - Sunday, 18 June 2006, 14:18 GMT
Alright, the bitmap fonts work fine with GTK1 and anything else that doesn't use XFT. Evidently something in Gnome breaks XFT for bitmap fonts.
Comment by name withheld (Gullible Jones) - Wednesday, 05 July 2006, 11:35 GMT
Sorry about posting the duplicate - I had forgotten about this one, did a search for "fontconfig" and didn't see anything so I filed a bug... D'oh. Anyway there's some new stuff I mention in this closed task:

http://bugs.archlinux.org/task/4963

It looks to me as though some GTK stuff might be messing up fontconfig. Very odd.
Comment by name withheld (Gullible Jones) - Thursday, 06 July 2006, 10:23 GMT
My bad, antialiasing is fuxed on Gnome too.

(Damn it, I tried to do before and after screenshots and overwrote the first screenshot... Grr. I'll try again.)
Comment by name withheld (Gullible Jones) - Thursday, 06 July 2006, 18:13 GMT
Alright, here are the screenshots...

Before fontconfig reinstall, after a clean installation with no missing deps and a refreshed font cache:
http://img509.imageshack.us/img509/2177/screen16bg.png

After fontconfig reinstall:
http://img515.imageshack.us/img515/9939/screen21an.png

As you can see there's quite a huge difference.

Loading...