[Bug 490888] New: All fonts are monospace after upgrade to fontconfig-2.6.99.behdad-3

[Red Hat Bugzilla]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: All fonts are monospace after upgrade to fontconfig-2.6.99.behdad-3

https://bugzilla.redhat.com/show_bug.cgi?id=490888

           Summary: All fonts are monospace after upgrade to
                    fontconfig-2.6.99.behdad-3
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: medium
         Component: fontconfig
        AssignedTo: besfahbo(a)redhat.com
        ReportedBy: mschmidt(a)redhat.com
         QAContact: extras-qa(a)fedoraproject.org
                CC: besfahbo(a)redhat.com, fedora-fonts-bugs-list(a)redhat.com
    Classification: Fedora
    Target Release: ---


Description of problem:
Today I did 'yum update' on my Rawhide KVM guest. About 20 packages were
updated, among them was fontconfig. After reboot to get the new kernel, all
fonts in GDM were monospaced and without antialiasing. After logging in into
GNOME everything was monospaced and no AA too (menus, window titles,
gnome-terminal, ...). I thought I had lost my Preferences -> Appearance ->
Fonts settings, so I went there to check, but all fonts appeared the same.

The problem was fixed it by running 'fc-cache -r' and logging out and back in.


Version-Release number of selected component (if applicable):
The upgrade was from:
fontconfig-2.6.97-5.g945d6a4.fc11.x86_64
to:
fontconfig-2.6.99.behdad-3.fc11.x86_64

How reproducible:
Not sure. I haven't tried downgrading and repeating the upgrade yet.

Steps to Reproduce:
1. Update fontconfig 
2. Reboot (although relogin would probably be sufficient)

Actual results:
All fonts are monospace and without antialiasing.

Expected results:
Font should look as they did before the upgrade.

Additional info:
I suspect the bug is in fontconfig's postinstall script where it does:
rm -f /var/cache/fontconfig/????????????????????????????????.cache-2
But at least on my system the number of question marks does not correspond to
the actual filename lengths of the files in that directory. E.g.
/var/cache/fontconfig/3830d5c3ddfd5cd38a049b759396e72e-x86-64.cache-2

(the "-x86-64" is not accounted for)

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.