Bug 675331

Summary:	Firefox 4-4.0-0.12.b10.fc14.x86_64 looks for wrong GRE
Product:	[Fedora] Fedora	Reporter:	Neil Bryant <neil.bryant>
Component:	firefox	Assignee:	Tom "spot" Callaway <tcallawa>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4	CC:	gecko-bugs-nobody
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:	2011-02-04 22:59:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Neil Bryant 2011-02-04 22:44:24 UTC

Description of problem:
After update, FF4 exits with this error to console, after the profile dialog:
"Could not find compatible GRE between version 2.0b9 and 2.0b9."

Version-Release number of selected component (if applicable):
firefox4-4.0-0.12.b10.fc14.x86_64
xulrunner2-2.0-0.11.b10.fc14.x86_64

How reproducible:


Steps to Reproduce:
1. Accepted updates from package updater
2. Ran
3. Select profile
  
Actual results:
"Could not find compatible GRE between version 2.0b9 and 2.0b9."

Expected results:
Normal Execution.

Additional info:
Looked in /usr/lib64/firefox-4/application.ini, Gecko is listed as:
  [Gecko]
  MinVersion=2.0b10
  MaxVersion=2.0b10
which I presume is correct, so I'm not sure where to look next.

Due to other issues with FF4 (Bug 664877), I have FF4 also running as a different user. That user runs fine (launching with su).

Comment 1 Neil Bryant 2011-02-04 22:59:00 UTC

I seem to have fixed that issue by filing the bug:

The workaround from the other bug is to copy application.ini:
cp /usr/lib64/firefox-4/application.ini /usr/lib64/xulrunner-2/ 

I checked, and while application.ini in firefox-4 was updated to Gecko versions 2.0b10, the application.ini in xulrunner-2 was still at 2.0b9.

I changed that, and the new error has gone away.I still can't launch FF4 from my main account, while it works from a second account just fine via su--but that is a pre-existing condition.

I'm not clear if there's any reason to keep the sopy of application.ini; but in absence of instruction, I will attempt to delete it and see.

I'm going to try to close this, I guess (and if I can); but leave it posted for reference.

Comment 2 Neil Bryant 2011-02-04 23:10:10 UTC

For completeness; removing the copied application.ini from the xulrunner-2 directory leads back to the 'could not read application.ini' (Bug 664877) error in my main account, while the second account continues to work fine.

Recopying the file (which was updated in the upgrade, apparently) removes new errors, and takes me back to where I was before all this (looking for a different bug).

Cheers

Comment 3 Christopher Aillon 2011-02-07 06:51:37 UTC

This is spot's *unofficial* firefox4 package.  Please file bugs with him instead of here.  Thanks.