Bug 5491

Summary:

libXft uses new fontconfig objects without registering

Product:

xorg

Reporter:

Stefan Dirsch <sndirsch>

Component:

Lib/Xft

Assignee:

Xorg Project Team <xorg-team>

Status:

RESOLVED FIXED

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

high

CC:

bugs.freedesktop, eich, keithp, mfabian

Version:

7.0.0

Keywords:

patch

Hardware:

Other

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Patch to fix this issue	none

Description Stefan Dirsch 2006-01-04 06:32:35 UTC

libXft uses new fontconfig objects without registering. I'll attach a patch. 
Details can be found in Novell Bugzilla. 
 
  https://bugzilla.novell.com/show_bug.cgi?id=141216&x=0&y=0

Comment 1 Stefan Dirsch 2006-01-04 06:33:40 UTC

Created attachment 4230 [details] [review]
Patch to fix this issue

Comment 2 Tilman Sauerbeck 2006-07-09 12:05:26 UTC

Someone check this patch :)

Comment 3 Daniel Stone 2007-02-27 01:29:43 UTC

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Comment 4 Stefan Dirsch 2007-11-04 09:17:35 UTC

Could anybody finally have a look at this patch?

Comment 5 Keith Packard 2007-11-04 11:32:11 UTC

Only 22 months late.

Comment 6 Stefan Dirsch 2007-11-04 11:55:00 UTC

(In reply to comment #5)
> Only 22 months late.
Close as fixed, but the patch has not been applied to git yet. Could you explain in more detail? Thanks.

Comment 7 Julien Cristau 2007-11-05 15:22:37 UTC

(In reply to comment #6)
> Close as fixed, but the patch has not been applied to git yet. Could you
> explain in more detail? Thanks.
> 
commit 8a7f3d450c1f339f429dbce55df523d026c92375
Author: Stefan Dirsch <sndirsch@suse.de>
Date:   Sun Nov 4 11:31:44 2007 -0800

    Register objects used by libXft.
    
    libXft uses XFT_MAX_GLYPH_MEMORY without first registering with fontconfig.

Comment 8 Stefan Dirsch 2007-11-05 15:52:05 UTC

Thanks!

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.