Bug 457284

Summary:	Firefox 3.0.1 hangs at startup with "symbol lookup error in libgdk-x11-2.0.so.0"
Product:	[Fedora] Fedora	Reporter:	Franck Collins <franck>
Component:	gtk2	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	quantumburnz
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:	2008-10-22 21:53:20 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 Franck Collins 2008-07-30 17:00:47 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); fr; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1

Description of problem:
When I launch Firefox, it crashes with this message :

/usr/lib64/firefox-3.0.1/firefox: symbol lookup error: /usr/lib64/libgdk-x11-2.0.so.0: undefined symbol: XRRGetScreenResources

Version-Release number of selected component (if applicable):
gtk2-2.13.5-1.fc10

How reproducible:
Always


Steps to Reproduce:
1. Launch Firefox

Actual Results:
Firefox crashes

Expected Results:
Firefox OK

Additional info:

Comment 1 Matthias Clasen 2008-08-01 01:38:22 UTC

Whats the output of 
ldd /usr/lib64/libgdk-x11-2.0.so|grep randr  ?

Comment 2 Christopher D. Stover 2008-10-22 21:53:20 UTC

The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present.  Since it has been thirty days or
more since we first requested additional information, we're assuming
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED: INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.

Thank you in advance.