Opera-10.50_pre6177 refuses to run with the error: 'Could not initialize Opera.'. That happens on both amd64 and x86. All earlier versions of opera have worked fine.
I confirm this bug present. See temporary workaround in my quickly hacked patch against /usr/bin/opera script.
Created attachment 215009 [details, diff] Patch to be able to run 10.50 version
Also confirmed. @MageSlayer: My /usr/bin/opera didn't have the lines removed in your patch and still fails. I have added gst-plugins-{ogg,theora,vorbis} as documented on the opera desktop team blog but made no difference.
Created attachment 215059 [details] Output from emerge --info =www-client/opera-10.50_pre6177
Comment on attachment 215009 [details, diff] Patch to be able to run 10.50 version Just run `. /etc/profile' and OPERA_DIR is suddenly set properly.
I have patched the wrapper script now to simply set OPERA_DIR by itself instead of relying on the user's environment to be refreshed (which I noticed myself would be rather cumbersome if it means you need to restart your X session just to get the variable in your environment. (In reply to comment #3) > I have added gst-plugins-{ogg,theora,vorbis} as documented on the opera > desktop team blog but made no difference. All you really need is media-libs/gst-plugins-base which is already a dependency of www-client/opera-10.50_pre6177, and the way I read it that would ensure support for ogg/vorbis/theora. As it obviously doesn't, I have made the ebuild depend on those specifically now.
(In reply to comment #6) > All you really need is media-libs/gst-plugins-base which is already a > dependency of www-client/opera-10.50_pre6177, and the way I read it that would > ensure support for ogg/vorbis/theora. As it obviously doesn't, I have made the > ebuild depend on those specifically now. I've made it depend on media-plugins/gst-plugins-meta now - that should cover everything nicely.
Jeroen, did you already commit the fixes? I just synced and reinstalled opera-10.50_pre6177, but opera still refuses to run, with the same error. I even renamed my .opera directory and started afresh, but with no success...
(In reply to comment #8) > Jeroen, did you already commit the fixes? I just synced and reinstalled > opera-10.50_pre6177, but opera still refuses to run, with the same error. I > even renamed my .opera directory and started afresh, but with no success... Sure I did. I am not even sure you're experiencing the same problem as the others did. Btw, your ${HOME}/.opera directory is entirely unused by this build - it uses the very much more visible ${HOME}/profile instead. To figure out what is going on in your case, emerge strace and run something like `strace -f -o opera.strace /usr/bin/opera' - then attach the file opera.strace to this bug report.
I went and looked the strace output. For me adding LINGUAS ”en” in addition to my language fixed this... This is my first time seeing en LINGUAS, I had on my paludis configuration -* fi, hence disabling the en, if it even were on by default. So atleast an user error here, I suppose.
Of course! MY_LINGUAS should not have "en" in it, because that includes the EULA. Other Opera ebuilds do this correctly, but it was apparently something I overlooked when rewriting it for 10.50. Should be fixed now: jeroen@astrid /keeps/gentoo/cvs/gentoo-x86/www-client/opera $ cvs diff Index: opera-10.50_pre6177.ebuild =================================================================== RCS file: /var/cvsroot/gentoo-x86/www-client/opera/opera-10.50_pre6177.ebuild,v retrieving revision 1.5 diff -u -B -r1.5 opera-10.50_pre6177.ebuild --- opera-10.50_pre6177.ebuild 3 Jan 2010 23:04:58 -0000 1.5 +++ opera-10.50_pre6177.ebuild 5 Jan 2010 18:13:15 -0000 @@ -22,7 +22,7 @@ IUSE="elibc_FreeBSD" -MY_LINGUAS="en zh-CN zh-HK zh-TW" +MY_LINGUAS="zh-CN zh-HK zh-TW" for MY_LINGUA in ${MY_LINGUAS}; do IUSE="${IUSE} linguas_${MY_LINGUA/-/_}"