|
Bugzilla – Full Text Bug Listing |
| Summary: | epiphany won't start | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Felix Miata <mrmazda> |
| Component: | GNOME | Assignee: | Joe Hargadon <jhargadon> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | andreas.hanke |
| Version: | Alpha 4 | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Felix Miata
2006-09-11 17:21:23 UTC
I'm unable to replicate in beta 1, are you having this problem still felix? Bug 209961 and bug 214992 are giving me a dickens of a time trying to update so that I can find out. The latter is a blocker that looks like it may keep me out of this for some time. I still get this in beta1 with epiphany-2.16.1-10. The epiphany package is broken.
% rpm -q --requires epiphany | grep xulrunner
mozilla-xulrunner181 = 1.8.0.99
But:
% ldd `which epiphany` | grep gtkembedmoz
libgtkembedmoz.so => /usr/lib/xulrunner-1.8.0.6/libgtkembedmoz.so
% objdump -p `which epiphany` | grep RPATH
RPATH /usr/lib/xulrunner-1.8.0.6
=> It has an rpm requirement on xulrunner181, but actually needs xulrunner180 at run-time. Packaging bug.
The dependencies are buggy in a way that causes the wrong xulrunner version to be pulled in.
Workaround: Install mozilla-xulrunner180 manually; Solution: Fix epiphany so that rpm dependencies and actual requirements match.
I found the following in epiphany.spec: # usedforbuild mozilla-xulrunner180 mozilla-xulrunner180-devel mozilla-xulrunner181 It's serious. You think you're building against *181, but actually it's being built against *180. The result are broken dependencies. Besides that, seamonkey started providing libgtkembedmoz.so again as well. I recommend reviewing _all_ gecko-related packages for bogus dependencies ASAP. *** This bug has been marked as a duplicate of bug 216100 *** |