Bug 60901 - TTF causes xftcache segfault
TTF causes xftcache segfault
Status: CLOSED CURRENTRELEASE
Product: Red Hat Raw Hide
Classification: Retired
Component: XFree86 (Show other bugs)
1.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-03-08 14:16 EST by Sammy
Modified: 2007-04-18 12:40 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-03-11 12:12:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sammy 2002-03-08 14:16:59 EST
This is not the default but if you add the TTF directory to the directories
in XftConfig file that xftcache starts to segfault every time and if one is
using anti-aliasing the desktop never comes on after login.
Comment 1 Mike A. Harris 2002-03-11 01:29:51 EST
Please attach the problem config file
Comment 2 Mike A. Harris 2002-03-11 01:31:31 EST
What font files are in the TTF directory?
Comment 3 Mike A. Harris 2002-03-11 01:34:46 EST
Also, what version of the following (and please upgrade to the latest if you
haven't already)

freetype
XFree86
Comment 4 Sammy 2002-03-11 12:12:05 EST
I only have the fonts that came with the rpm in the TTF directory.

The same problem with 4.2.0-6.32 AND 4.2.0-6.41

Freetype version is 2.0.6-3.

I have another directory that comes from ttfonts rpm BUT also contains the
Microsoft's version of tt fonts. This is also listed in XftConfig.

This happens with both the standard config file that is in the rpm except TTF
directory added or a slightly modified config file that I have. In both cases
just commenting the TTF directory line allows xftcache to work.

Comment 5 Sammy 2002-03-18 11:58:14 EST
The problem is resolved in XFree86-4.2.0-6.47 and freetype-2.0.9-1.
Closing....

Note You need to log in before you can comment on or make changes to this bug.