Can't play videos after update
-
-
-
alexs last edited by
@leocg said in Can't play videos after update:
Or, most probably, Opera thinks that even offering a script like that may have legal consequences.
Now, it is mentioned here that Opera cannot make the library available for legal reasons.[1]
However, that does not mean that you are allowed to download it from a third-party source after installation in order to use it later. And that is exactly what the script does. An official statement from Opera would be more than helpful to explain why Opera users on Linux have to make the browser functional themselves, which is ridiculous.[1] https://forums.opera.com/post/150324
[2] FFmpeg License and Legal Considerations -
-
alexs last edited by alexs
@gloewa said in Can't play videos after update:
@alexs Are you kidding me? the linked opera-posting is from 2018!
That doesn't change the statement regarding the license.
@gloewa said:
Till few days ago all was as it should. The last update broke the video-functionality.
If opera is not able to fix it, its time to change to another browser. As simple as that.I don't disagree with you. For me, I had to fix the video functionality myself once again.
-
burnout426 Volunteer last edited by
See https://github.com/flathub/com.opera.Opera/issues/205#issuecomment-3289581435. For the dependencies (libavcodec, libavformat, and libavutil), it looks like you need avcodec62, avformat62 and avutil60 now for some versions of libffmpeg.so. Make sure you have those versions or newer of those packages.
-
burnout426 Volunteer last edited by
@gloewa said in Can't play videos after update:
previous versions of opera could play videos, current version
A libffmpeg.so only works with a specific major version of Chromium. So, any time Opera starts using a new major version of Chromium, you have to update to a new libffmpeg.so that's based on that new major version of Chromium.
Historically, Opera started using a new major version of Chromium every time Opera updated to a new major version itself. So, you had to find a new libffmpeg.so each time Opera updated to a new major version (102 to 103 for example). In addition, since Opera Beta was a major version ahead of Opera Stable and Opera Developer was 2 major versions ahead, you'd need a different libffmpeg.so for beta and a different one for developer.
However, for a while now, Opera has been been slower on updating to new major versions of Chromium, so a libffmpeg.so's compatibility has been lasting a bit longer. But, libffmpeg.so still needs to be updated eventually.
Now, for the Snap package of Opera and the Snap libffmpeg.so it uses, it has slots for multiple major versions of Opera, which can make it so you don't have to worry about compatibility most of the time and stuff just works. So, try the Snap version of Opera if you want. Also, some users that don't use the Snap package of Opera put a symlink to the snap libffmpeg.so in Opera's "lib_extra" folder and have had good luck.
For the Flatpak package of Opera, the maintainer tries to make sure all is good with a compatible libffmeg.so, but sometimes it can go wrong.
If you don't want to deal with any of that though, it's best to use a different browser.
-
burnout426 Volunteer last edited by
For the Flatpak package, see https://github.com/flathub/com.opera.Opera/issues/205#issuecomment-3291058932. Update coming soon.
-
gloewa last edited by
@burnout426 Thank you for all the information. That's very kind of you.
I solved the problem for now by copying libffmpeg.so from the Vivaldi directory to the Opera directory. Now everything is working as usual again.
Opera User since Version 3.x
-
valour47 last edited by
https://github.com/Ld-Hagen/fix-opera-linux-ffmpeg-widevine
this is what helped me every time this happend
-
gloewa last edited by
@valour47 Thanks for your Info. I solved the problem for now by copying libffmpeg.so from the Vivaldi directory to the Opera directory. Now everything is working as usual again.
Opera User since Version 3.x
-
3333e last edited by
@Opera-QA-Team
As I said at somewhere, opera has wrong LD_PRELOAD for buldled ffmpeg.
We can load newer version of ffmpeg (with same avcodec soname) if opera fixed the bug without violating with EULA. Please stop LD_PRELOAD. -
3333e last edited by
@burnout426 Also needed to remove bundled
.soto take avcodec based approach due toLD_PRELOADbug.ABI info is completely masked at unified
.so(extractable from source code) and major ver of avcodec could be bumped even major ver of Chromium is not bumped. -
-
-
alexs last edited by
@3333e said in Can't play videos after update:
@gloewa Copying random version from random place is not a reproducible solution.
It isn't, but the Opera programmers responsible leave you no other choice.
Like Opera, Vivaldi uses Chromium as its basis, but Vivaldi uses a functioning libffmpeg.so. I mentioned above [1] where Vivaldi gets the libffmpeg.so from.
[1] https://forums.opera.com/post/392484 -
-
