Red Hat Bugzilla – Bug 356731
Move ephy to xulrunner
Last modified: 2008-02-28 12:21:57 EST
1. Install firefox and epiphany
2. Launch epiphany and load some pages, check it works well
3. Update epiphany and firefox after a security/bug fix errata
A large number of web pages, such as the one on the freedesktop gitweb (probably
application/xhtml+xml pages) , will show up as malformed XML.
Screenshot attached below
Created attachment 241961 [details]
I have no clue, but with firefox-188.8.131.52-1.fc8 on i386 it WORKSFORME. Do you
have something more interesting to add before I close this? Any interesting
plugins? COuld you try to run firefox with -safe-mode and test this?
I'm not running firefox, it's a bug in firefox as a framework. It probably
doesn't happen with firefox the web browser.
I believe this happens when the currently referenced firefox files are deleted
from the disk, which the old library (still in memory) will try to use.
1. Epiphany starts with firefox 184.108.40.206 as the backend, gecko will use the files
2. Upgrade firefox, keeping epiphany running
3. Files in $(libdir)/firefox-220.127.116.11/ don't exist anymore, and because they
aren't opened, they can't be found by the old running gecko library. No error
messages visible, apart from the inability to see open some web pages.
This should be fixed when moving to xulrunner, according to Chris Aillon, so
Just for the sake of my curiosity, has there been any updates on Ephy to play
nicely with XULrunner goodness? :) Thanks.
I have some patches but it doesn't work completely yet. Stay tuned and watch
Thanks for the update, Martin. It's appreciated greatly!
Created attachment 276851 [details]
a minimal epiphany xulrunner patch
With this patch, epiphany compiles and runs with xulrunner. This is a minimal
patch so some functions are disabled and need rewrite.
Martin, don't work from tarballs, ephy trunk already has a xulrunner backend (in
addition to the mozilla and webkit ones.
This patch is not intended for usage. I've just tried to compile and run ephy
with xulrunner and check how many changes has to be included.
The ephy trunk doesn't compile either, though.
http://bugzilla.gnome.org/show_bug.cgi?id=503657 has a patch which works against
the upstream code, but fails against ours because we ship compat .pc files... I
think we should switch to only shipping the upstream .pc files (and the mozembed
ones and the unstable ones that I filed a separate bug about)
What's the status on epiphany-extensions?
lists it as "failing" but doesn't list any open bug (yet) to report progress.
(In reply to comment #13)
> What's the status on epiphany-extensions?
> lists it as "failing" but doesn't list any open bug (yet) to report progress.
The extensions need Epiphany to be properly built against XULrunner, otherwise
the extensions get built against XULrunner and Ephy itself against
Firefox...which is not a good thing. :]
I've edited the Wiki page to comment about that; and I'll enqueue a rebuild for
it once Epiphany/XULrunner is complete. Thanks.
(In reply to comment #14)
> The extensions need Epiphany to be properly built against XULrunner, otherwise
> the extensions get built against XULrunner and Ephy itself against
> Firefox...which is not a good thing. :]
There is no firefox-devel package anymore, so epiphany cannot be built against
firefox anyway, and even if there was one it wouldn't since rawhide has a
preview of firefox 3 now which is incompatible with current trunk.
Unfortunately this also applies to xulrunner 1.9 which means that since 2 weeks
ago, the epiphany package in rawhide is not usable anyway.
(In reply to comment #15)
> There is no firefox-devel package anymore, so epiphany cannot be built against
> firefox anyway, and even if there was one it wouldn't since rawhide has a
> preview of firefox 3 now which is incompatible with current trunk.
> Unfortunately this also applies to xulrunner 1.9 which means that since 2 weeks
> ago, the epiphany package in rawhide is not usable anyway.
Forgive my ignorance. I meant to say that the extensions need Epiphany proper to
build (BR: epiphany-devel), so since it is not installable due to the broken
Gecko dependencies, then the extensions cannot be rebuilt.
I'm building an svn version of epiphany now into rawhide, which should clear up
the deps and actually run, though there may be issues with it. File new bugs if
that is the case.
Great job! Task completed with epiphany-2.21.5-0.1.svn7844.fc9 which is up
and running and works for me. Thanks a lot!
A small issue is that plugins in /usr/lib64/mozilla/plugins on my x86_64
box are neither seen nor used by epiphany, e.g. libgnashplugin.so.
Should a separate bug report be submitted for this, and if so, should this
be done for epiphany or gnash? libgnashplugin.so does get used, however,
after copying it to $HOME/mozilla/plugins.
I suppose that global /usr/lib64/xulrunner-1.9pre/plugins would have
worked, too, since both plugins present over there get displayed after
entering "about:config", namely libnullplugin.so and libunixprintplugin.so.
/usr/lib(64)/mozilla/plugins (or /usr/lib(64)/mozilla/plugins-wrapped if you run
nspluginwrapper) is a standard location for all mozilla plugins and all plugins
should be installed here...
Plugin issue reported as bug 427369. The present bug can probably be closed
*** Bug 427461 has been marked as a duplicate of this bug. ***
It doesn't compile with the latest trunk...I've updated the upstream BZ.
I just tried the new epiphany / xulrunner packages on a PowerPC-based laptop.
I had to install glib2-2.15.0-4.fc9 because of a requirement for g_dpgettext,
though this dependency is not in the spec file (should be glib2 >= first
version with g_dpgettext). After satisfying this dependency, epiphany now fails with,
"Epiphany cannot be used now. Mozilla initialization failed."
"** (epiphany:24842): WARNING **: Could not determine locale!" is written to
the console. firefox-3.0-0.beta2.7.fc9 works fine.
(In reply to comment #23)
See closed bug 427461. Install xulrunner-1.9-0.beta2.4.fc9 [e.g. from koji],
install it, and everything will work fine.
OK now that epiphany 2.21.5 has rebuilt successfully:
can somebody rebuild epiphany-extensions against this new epiphany to avoid the
broken deps? I started to but I couldn't find a corresponding
epiphany-extensions 2.21.5 release in:
(In reply to comment #25)
> OK now that epiphany 2.21.5 has rebuilt successfully ..
Actually, it doesn't [anymore] as reported in comment #22.
We need to update epiphany from gnome svn...there's an updated version what
(In reply to comment #26)
> (In reply to comment #25)
> > OK now that epiphany 2.21.5 has rebuilt successfully ..
> Actually, it doesn't [anymore] as reported in comment #22.
Well, the current 2.21.5 is still built and in rawhide and can act as a
BuildRequires for epiphany-extensions even if it wouldn't rebuild against the
But in any case the version of epiphany-extensions needs to be bumped up because
it won't compile against 2.21.5 even if epiphany did work, see my failed build:
(In reply to comment #27)
> We need to update epiphany from gnome svn...there's an updated version what
> should work.
Isn't this build of 02-Jan already against SVN?
Or do you mean an even more recent SVN of epiphany?
See gnome but at comment 12
(In reply to comment #28)
> But in any case the version of epiphany-extensions needs to be bumped up because
> it won't compile against 2.21.5 even if epiphany did work, see my failed build:
Unfortunately, epiphany-extensions has no 2.21.x release; and SVN trunk
currently fails to build against XULrunner. :(
I've filed upstream GNOME BZ 508369 for that; and am attempting to whip up a
patch for the moved headers now.
After update to xulrunner-1.9-0.beta2.12.nightly20080121.fc9, epiphany
crashes during start-up:
"EphyBrowser initialization failed for 0x......"
(In reply to comment #32)
> After update to xulrunner-1.9-0.beta2.12.nightly20080121.fc9, epiphany
> crashes during start-up:
> "EphyBrowser initialization failed for 0x......"
epiphany needs a rebuild for the new xulrunner? comment #31 suggests that may
not be able to.
epiphany-2.21.5-0.1.svn7856.fc9 continues to crash for all xulrunner
builds > 1.9-0.beta2.11.nightly20080115.fc9.
(In reply to comment #34)
> epiphany-2.21.5-0.1.svn7856.fc9 continues to crash for all xulrunner
> builds > 1.9-0.beta2.11.nightly20080115.fc9.
It's because it's built w/o rpath with mozilla home dir and gecko crashes during
initialization. We need to investigate it.
Would it be less work to build Epiphany against WebKit instead? There is not
much point in shipping two Gecko-based browsers.
(In reply to comment #36)
> Would it be less work to build Epiphany against WebKit instead? There is not
> much point in shipping two Gecko-based browsers.
Firefox is very far from being usable for me, and the WebKit backend doesn't
support plugins, so I'd rather it worked before F9.
epiphany still crashes with xulrunner-1.9-0.beta3.23.nightly20080217.fc9.
Btw, xulrunner is required for other GNOME applications like yelp anyway,
thus making WebKit the default backend for epiphany does not appear to
be obvious road to go.
We need to get good xulrunner support, yes; I was thinking of WebKit as an insurance policy. Not having
all the browsers use the same engine. The lack of support for plugins is a deal-breaker, though.
I guess there's Opera and running Firefox from an upstream tarball for those times when Firefox /
Epiphany is broken.
Should be fixed now.