Bug 6 - HYRGothic font hangs fontconfig?
Summary: HYRGothic font hangs fontconfig?
Status: RESOLVED DUPLICATE of bug 5
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2.1
Hardware: Other other
: high normal
Assignee: Keith Packard
QA Contact:
URL: http://bugs.debian.org/cgi-bin/bugrep...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-12 11:43 UTC by Colin Walters
Modified: 2003-01-27 18:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Colin Walters 2003-01-12 11:43:47 UTC
This is another report filed in the Debian BTS; the submitter says that the font
at http://myhome.hanafos.com/~difro/HYRGothic14.pcf.gz hangs fontconfig.
More details in the URL in the bug description.
Comment 1 Owen Taylor 2003-01-14 15:26:28 UTC
We saw this with one of the .pcf.gz fonts in the Red Hat distribution
as well, I don't remember which one it was, sadly. Maybe k14.pcf.gz
(a 14 kanji font ... might even be the same as the one here)

On short inspection, it seemed like a bug in the  gz support in
FreeType, but I suppose it might have been looping in fontconfig
and simply all the time was being spent in FreeType.

Comment 2 Anthony Fok 2003-01-21 07:51:57 UTC
Yes, Owen, your guess was right indeed.  It appears to have to do with the
earlier gzip code in FreeType-2.1.3+CVS that caused the hang.  I happened to
have two versions packaged here for Debian, 2.1.3-4 and 2.1.3-5, one before
James Su's freetype gzip patch, and one after, and testing suggests that the bug
was fixed in the process.

On the Debian front, I have just reassigned the bug report to the libfreetype6
package, and closed it with explanation.  :-)

Thanks again,

Anthony
Comment 3 Keith Packard 2003-01-28 13:33:46 UTC
Another instance of the freetype gzip code problem.

*** This bug has been marked as a duplicate of 5 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.