opera-stable 80.0.4170.16 Does Not Launch
-
gmiazga Opera last edited by
@brucehankins Opera 80 needs codecs with built for chromium 94, any previous versions will be incompatible. I think that using codecs you mentioned in https://repo.herecura.eu/herecura/x86_64/opera-beta-ffmpeg-codecs-94.0.4606.31-1-x86_64.pkg.tar.zst should work.
-
BruceHankins last edited by
@gmiazga I'll try installing locally and see if that works. They upgraded to chromium 94 with the opera-stable release but my understanding is it's still using the codecs from chromium 92. This seems like a pretty big oversight. It means as the package maintainer I now how to compile and add the new libffmpeg.so codecs as a build dependency when packaging opera-stable for it to run properly.
-
l33t4opera last edited by sgunhouseHi @brucehankins,
First of all, regarding the repackaging: you should be cautious with this because of legal reasons - check if you can do it before you get in trouble.Of course you should be fine while using the lib from the repo, since your OS is using glibc 2.33 (the same version which the latest Arch Linux uses, so there should not be crashes or other serious problems with it).
Additionally you should know, that every time the Opera will be updated to the next major version (or it will be based on a significantly higher version of Chromium), you will have to update the lib accordingly. In other case, the lib may be not working in the Opera or even may cause crash of the browser.
The same goes for the glibc version, if your OS will use a lower version than the one with which the FFMPEG will be compiled, it will not work and will cause the browser to not launch at all.
-
BruceHankins last edited by
@l33t4opera thanks for the reply. The opera-stable .deb package is licensed as distributable, and I'm making no changes to the software, just repackaging from a .deb to an .eopkg format.
-
benvantende last edited by
@gmiazga said in opera-stable 80.0.4170.16 Does Not Launch:
Works perfectly! Thanks
-
spikespiegel last edited by@gmiazga said in opera-stable 80.0.4170.16 Does Not Launch:
@brucehankins Opera 80 needs codecs with built for chromium 94, any previous versions will be incompatible. I think that using codecs you mentioned in https://repo.herecura.eu/herecura/x86_64/opera-beta-ffmpeg-codecs-94.0.4606.31-1-x86_64.pkg.tar.zst should work.
Thanks! BTW, the link seems broken. This is the right link:
https://repo.herecura.eu/herecura/x86_64/opera-beta-ffmpeg-codecs-94.0.4606.54-2-x86_64.pkg.tar.zst
Thanks again @gmiazga
-
l33t4opera last edited by
@brucehankins I see, but as you wrote "compile and add the new libffmpeg.so codecs as a build dependency", it depends now which version of "libffmpeg.so" do you mean.
If you mean the one from the repo, then there might be legal issues because it provides also H.264 codec, which as I know is not allowed to be distributed without paying a license fee.
The lib included in the Opera's package has no such issue, because it doesn't include H.264 support.Perhaps someone from Opera or any person who knows the topic better may reply to it to dispel any doubts.
-
styen last edited by styen
https://github.com/Ld-Hagen/fix-opera-linux-ffmpeg-widevine works
On Arch-based and Debian-based distros it may run automatically after opera update -
BruceHankins last edited by
@styen it doesn't, I'm the maintainer responsible for updating the package. Hopefully the next release will work better.
-
styen last edited by styen
@brucehankins Well, if you've repackaged opera, is there symlink for opera somewhere in PATH? It's required to detect opera directory by script.
Post here output ofdirname $(readlink -f $(which opera))It should be the correct Opera installation path
Also if original libffmpeg.so from .deb replaced with something else, return it back before applying fix. -
yogimanuk last edited by
The problem with this codec breaking Opera frequently is terribly irritating. It seems to me that if Opera can not ship with the codec there is little that can be done about that. But why can new releases of Opera not come with a script that downloads and copies the correct the correct version of ffmpeg that is required for that specific release. I mean seriously how hard would it be to include this script in either a directory or link to it from within the settings. click it, download the right version, ask for credentials and copy the correct file to the correct location. Why do we have to deal with this every time a new version of Opera appears when the problem doesn't exist with the other browsers that are available and if it does exist why is this not such a problem.
-
leocg Moderator Volunteer last edited by
@yogimanuk See https://forums.opera.com/post/150324
I understand that they can't provide the codecs themselves, including downloading it from a third party through a script. -
-
benvantende last edited by
@yogimanuk Agree ... It is a weird situation, although I can live with it. I created my own script that I always run after an Opera update
-
yogimanuk last edited by
@benvantende Yes I too have a script that copies the files, my problem is I never know what codec version to download and where from.
-
styen last edited by styen
@yogimanuk said in opera-stable 80.0.4170.16 Does Not Launch:
my problem is I never know what codec version to download and where from.
https://forums.opera.com/topic/51878/opera-stable-80-0-4170-16-does-not-launch?_=1633610756070#8 -
-
-
-
BruceHankins last edited by
@jferreira I agree, but I'm not leaving. Unfortunately for the users on my distro of choice, Opera will be held back on 79 until a fix is implemented and 80 truly is stable and not so much of a dev/beta release.
