From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020528
Description of problem:
I've synced two boxes with Raw Hide today and noticed all legacy apps lost
access to TrueType fonts (for example xfontsel will only list type1 fonts, not
Strangely anough gnome2 apps are fine
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Upgrade to latest rawhide.
I suppose the problem lies in one of the XFree86 rpms or in freetype
I can provide a list of installed rpms if necessary
Actual Results: emacs complains at startup about faces, gnome1-apps ui nows
uses minuscule fonts, evo & galeon are ugly...
A lot of apps are rendered inusable pending fixes. Since I use 100dpi monitors
the 75dpi fallbacks just don't cut it
Expected Results: These apps should have displayed cleanly using the configured
(Note that I wonder what would happen if mkfondir changed its font descriptions
too much as all old control-center capplets do not exist anymore. How would one
change the gtkhtml font for example ?)
Please attach your /etc/X11/fs/config, your X server config to the bug
report using the link below.
It is possible that the problem you are seeing might be a transient of some
kind as we switch to fontconfig/Xft2 infrastructure.
Also be sure to restart xfs and X any time you update either of them.
gnome 2 works fine since it's on a whole different font architecture (fontconfig
if you have the very bleeding edge, Xft1 otherwise). But the core font
configuration is apparently horked.
I always do mkfontdirs and xfs restart whenever font config is borked,
unfortunately (maybe because I have an ISO-8859-15 locale) any X upgrade seems
to eat the "fixed" font on my setups without this.
Anyway here are my config files
Created attachment 60265 [details]
Created attachment 60266 [details]
Created attachment 60267 [details]
Just installed the fontconfig rpm (didn't knew there was one till now), didn't
change anything (but didn't break anything new, that's a relief:)
Latest rawhide is now ok
(I do wonder which one of these fixed it:)
I'd guess the freetype upgrade; FreeType-2.1.0 had problems
with the charmaps in a lot of fonts.