Bug 171224

Summary:	fontconfig breaks firefox
Product:	[Fedora] Fedora	Reporter:	John Ellson <john.ellson>
Component:	fontconfig	Assignee:	David Zeuthen <davidz>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	mclasen
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-20 16:24:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Ellson 2005-10-19 16:24:54 UTC

Description of problem:
Latest fontconfig breaks firefox.  Firefox quits without error mesage before
opening window.

Version-Release number of selected component (if applicable):
fontconfig-devel-2.3.91.cvs20051017-1
firefox-1.5-0.5.0.beta2

How reproducible:
100%

Steps to Reproduce:
1.firefox --debug
2.
3.
  
Actual results:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912501427328 (LWP 28890)]
0x00000037d6518b7e in FcCharSetCopy () from /usr/lib64/libfontconfig.so.1


Expected results:


Additional info:
Problem fixed by reverting to fontconfig-2.3.2-1

Comment 1 Sammy 2005-10-20 16:07:19 UTC

I am running i386 version of  firefox-1.5-0.5.0.beta2 on my X86_64 system and 
it is working fine with the new fontconfig-cvs (I do this so that I can use plugins like 
flash, etc which do not have 86_64 versions). 
 
So, it seems like something may be wrong in the X86_64 version of fontconfig-cvs.

Comment 2 John Ellson 2005-10-20 16:24:25 UTC

I don't know.  I re-upgraded to fontconfig-2.3.91.cvs20051017-1 today, after
today's other rawhide uprades, and now I can't recreate  the problem.

I tried with my regular .mozilla/firefox/  configuration, and with that moved
aside to get a vanilla configuration.

The other thing I've done since yesterday is to log out and log back in, so
perhaps there was a corrupted font cache thats been cleared now.

Probably we should abandon this report unless I can recreate it.

Changed to:  WORKSFORME.