Bug 214720

Summary: Latest Firefox update breaks Galeon
Product: [Fedora] Fedora Reporter: E Mair <e>
Component: galeonAssignee: Denis Leroy <denis>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: medium    
Version: 6CC: extras-qa, fedora
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-22 07:48:35 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 E Mair 2006-11-08 23:59:15 UTC 
Description of problem:
Installing firefox-1.5.0.8-1.fc6 will stop Galeon from starting.

Version-Release number of selected component (if applicable):
firefox-1.5.0.8-1.fc6
galeon-2.0.3-3.fc6

How reproducible:
Always

Steps to Reproduce:
1. Install latest update of Firefox
2. Try to run Galeon
  
Actual results:
Galeon will not start.

"galeon: error while loading shared libraries: libgtkembedmoz.so: cannot open
shared object file: No such file or directory"

Expected results:

Galeon should start.

Additional info:
Comment 1 Denis Leroy 2006-11-09 11:00:42 UTC 
Already fixed and rebuild, will be available at the next Fedora Extras push.
Comment 2 Remi Collet 2006-11-09 16:13:15 UTC 
I think galeon should (as epihany, yelp and others does) require exact version
for gecko-libs.

From yelp.spec
%define gecko_version 1.8.0.8
...
Requires: gecko-libs = %{gecko_version}
...
BuildRequires: gecko-devel = %{gecko_version}

In this way, next firefox update will not break galeon but will only block
updates until new galeon is ready.
Comment 3 Denis Leroy 2006-11-09 22:43:04 UTC 
Good point, we're hitting a limitation of the rpm automatic dependencies
detection system here, and of course firefox non-standard dynamic libraries
versioning.
Comment 4 E Mair 2006-12-22 04:14:55 UTC 
Same thing again with FF 1.5.0.9.
Comment 5 Denis Leroy 2006-12-22 07:48:35 UTC 
Fixed already, at next FE push.