I cannot use epiphany after upgrading to xulrunner-1.9.0.4-r1. When epiphany is launched a dialog box comes up saying it cannot initialize Mozilla. Nothing is sent to stderr. Downgrading to xulrunner-1.9.0.4 fixes the problem. # emerge -vp xulrunner These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] net-libs/xulrunner-1.9.0.4-r1 [1.9.0.4] USE="dbus gnome startup-notification -custom-optimization -ipv6 -java" 0 kB
Forgot to mention: re-emergeing epiphany and epiphany-extensions does not fix the problem.
(In reply to comment #1) > Forgot to mention: re-emergeing epiphany and epiphany-extensions does not fix > the problem. > post your emerge info if you want help.
Created attachment 172010 [details] emerge --info Same thing here:
Created attachment 172015 [details] emerge --info
I'm now able to run epiphany. I took a look at this bug https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/30791 ... which mentions compreg.dat. I took a look in /usr/lib/xulrunner-1.9 but there was no compreg.dat file there. Then I discovered it existed in both /usr/lib/xulrunner and /usr/lib/mozilla. But both these directories don't seem to belong to a particular package so I removed them. This still didn't fix epiphany, but I then discovered a compreg.dat in /usr/share/epiphany. But the file wasn't owned by the epiphany package. So what I did then was unmerge epiphany, then "rm -rf /usr/share/epiphany" and then emerge epiphany again. Now epiphany runs. The launchpad bug seems to indicate that compreg.dat is created when a xulrunner app is run as root and this somehow mucks up things (I didn't understand the details). Why this affects xulrunner-1.9.0.4-r1 and not xulrunner-1.9.0.4 is beyond me. Then again maybe that wasn't the problem but the steps I performed somehow "fixed" it...
same problem here
can confirm that deleting /usr/share/epiphnay and reemerging epiphany fixes the problem.
(works fine for me, but I don't have a /usr/share/epiphany/compreg.dat)
could you run qfile /usr/share/epiphany/compreg.dat (from portage-utils) or equery belongs /usr/share/epiphany/compreg.dat (from gentoolkit) ? I don't have this file on any of my machines.
(In reply to comment #9) > could you run qfile /usr/share/epiphany/compreg.dat (from portage-utils) or > equery belongs /usr/share/epiphany/compreg.dat (from gentoolkit) ? > > I don't have this file on any of my machines. > It doesnt belong to any package. ( equery b /usr/share/epiphany/compreg.dat )
*** Bug 247676 has been marked as a duplicate of this bug. ***
On a system of mine that experienced the problem I had a /usr/share/epiphany/components/compreg.dat - moving that away (to be able to debug things with the copy later) fixed it. It is apparently created by running epiphany as root, so you experience the problem only if you have launched epiphany as root ever before upgrading to xulrunner-1.9.0.4-r1 (and epiphany was using xulrunner-1.9 before with the -r1x revisions). So running epiphany as root prior to upgrade is the necessary thing for reproducing the bug for testing.
(In reply to comment #12) > On a system of mine that experienced the problem I had a > /usr/share/epiphany/components/compreg.dat - moving that away (to be able to > debug things with the copy later) fixed it. It is apparently created by running > epiphany as root In addition, I found also xpti.dat in my /usr/share/epiphany/components/ directory. ls /usr/share/epiphany/components/ -l insgesamt 252 -rw-r--r-- 1 root root 142551 25. Jun 08:05 compreg.dat -rw-r--r-- 1 root root 100271 27. Okt 01:26 xpti.dat The timestamps are interesting, too, as I upgraded epiphany often from the gnome git overlay and now from the tree. But removing the *.dat files helped here, too
I too have this problem. I eliminated all instances of compreg.dat in Epiphany and xulrunner (I have two versions via slot). I then rm -f epiphany, rebuilt epiphany and it still won't work. Ultimately I had to mask firefox and xulrunner and regress to 3.0-r1 and 1.9-r3 in order to have a firefox and mozilla that function on my box. I do not see any other .dat files in epiphany or xulrunner.
I looked in ChangeLog for xulrunner ebuild. Difference between 1.9.0.4 and 1.9.0.4-r1 was in disableing libxul... So just adding: mozconfig_annotate '' --disable-libxul to ehe xulrunner ebuild fixed the problem. What‘s libxul by the way?
(In reply to comment #16) > I looked in ChangeLog for xulrunner ebuild. Difference between 1.9.0.4 and > 1.9.0.4-r1 was in disableing libxul... So just adding: > > mozconfig_annotate '' --disable-libxul > > to ehe xulrunner ebuild fixed the problem. What‘s libxul by the way? Something important, fixing some crash cases. --disable-libxul stops build/installation a dozen more libraries that could be needed, as far as I understood. Details of what they are would be nice though for embedded usage purposes
*** Bug 249978 has been marked as a duplicate of this bug. ***
so how are things going with xulrunner 1.9.0.5 ?
No problem.
ok, closing then.
Just a comment for those running into this bug. Removing the compreg.dat file worked for me _without_ reemerging epiphany. Should you be reading this, and lamenting the thought of another wait while epiphany re-emerges, first try launching epiphany after deleting the compreg.dat mentioned above. Cheers, Chris
*** Bug 248133 has been marked as a duplicate of this bug. ***
*** Bug 259185 has been marked as a duplicate of this bug. ***
Due to comment 23, I'm reopening this bug. I've got a problem with yelp (2.24.0-r10 and 2.26.0) refusing to run with "Could not initialize gecko!" message. This problem is fixed by simply 'touch .autoreg' in /usr/lib/xulrunner-1.9. This file does exist in /usr/lib/mozilla-firefox already.
xulrunner modifications are not our business.
Is this still a problem even after removing compreg.dat and xpti.dat ?
And what about my problem ? Should I reopen bug comment 23 ? While it won't be a problem for long, as gnome is moving to webkit, that shouldn't stop fixing this bug.
(In reply to comment #28) > And what about my problem ? > Should I reopen bug comment 23 ? Yelp 2.26.0 should work with xulrunner 1.9.1 (it does for me). If it doesn't for you, please reopen that bug.
Don't you mean 1.9.0.11 ? And it seems to work now, hard to tell exactly why, quite a bit has changed in the meanwhile.
(In reply to comment #30) > Don't you mean 1.9.0.11 ? *cough*, right, looking at too many similar bug reports is confusing. > And it seems to work now, hard to tell > exactly why, quite a bit has changed in the meanwhile. > If it does crop up again, reopen. Thanks.
