Red Hat Bugzilla – Bug 138436
fc-cache fontconfig/libfreetype segfault processing MSungStd-Light-Acro.otf
Last modified: 2008-08-02 19:40:32 EDT
Description of problem:
fontconfig crashes on the font file MSungStd-Light-Acro.otf
when creating the fonts.cache-1 file. fc-cache will segfault
when processing a directroy with this file.
The existence of this file prevents X start-up on window
managers using fontconfig
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Get the font file from Adobe Asian Font Packs
Adobe Acrobat 5.x
You will get a chtfont.tar.gz file containing the MSung... file
2. The file is 8351624 bytes with md5sum
3. Create a directory for the file and put the directory in
4. Run fc-cache -v -f
fc-cache will segfault on the directory containing this
fc-cache will correctly create the cache file
This works on FC2 - could be problem in the fontconfig library.
Unfortunately the font file is too large to attach here - my apologies
for making you go through hoops to access the font but it is
directly available at
Tracked this down to freetype - I replaced libfreetype.so.6
with the library from FC2 and it works.
Faulty version of freetype is 2.1.9-1 as shipped
with Fedora Core 3. FC2's freetype-2.1.7-4 is ok.
Other large otfs from Adobe (e.g. Chinese Simplified, Japanese)
don't trigger this problem in FC3.
Do you know if the problem still occurs with freetype 2.1.10 ?
(In reply to comment #4)
> Do you know if the problem still occurs with freetype 2.1.10 ?
Fixed using 2.1.10 from rawhide (problem still occurs with 2.1.9 in Core 4); can
generate cache file now.
Created attachment 120279 [details]
The correct fontconfig cache file
This cache file is correctly generated by freetype 2.10 in rawhide 2005-10-09.
fc-cache crashes on this font file all the way from FC3 to FC4 with 2.1.9.
Oops - that should be rawhide 2005-10-22.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing since it works in FC5 and forward, and FC3 and FC4 are maintained by
Fedora Legacy for security updates only.