Bug 1199210 - Firefox 99 no longer plays video content due to Tumbleweed FFMPEG / openh264 incompatibility
Firefox 99 no longer plays video content due to Tumbleweed FFMPEG / openh264 ...
Status: NEW
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Firefox
Current
x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
: ---
Assigned To: Factory Mozilla
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-05-04 17:18 UTC by Paul Hands
Modified: 2022-05-05 06:38 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Hands 2022-05-04 17:18:21 UTC
About 21 days ago, I reported a bug ( https://bugzilla.mozilla.org/show_bug.cgi?id=1764436 ) to the FireFox team, after a Tumbleweed update caused FireFox to stop playing some video content.   Other browsers like Brave or Opera worked just fine, leading me to suspect Firefox.  I worked with the FF team to run various tests and their eventual resolution is "wontfix" because the problem actually seems to be some packaging issue with FFMPEG and OPeH264...perhaps a version mismatch.

One of the FF developers said "To fix the problem, you need to install the exact same version of https://software.opensuse.org/package/libopenh264-6 that was used to build OpenSuse's ffmpeg-5."  The mozilla bug link above gives the full story.

I have been unable to get Firefox to play video content, no matter what combination of FFMPEG and Openh264 I've tried, but this area isn't my strength.

The FF people recommended that I open a bug with Tumbleweed, and perhaps together, the bug can be resolved.

I'm available for any testing or experiments...just let me know.

==========================MACHINE INFO==========================================

Operating System: openSUSE Tumbleweed 20220503
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel Version: 5.17.4-1-default (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 47.0 GiB of RAM
Graphics Processor: AMD DIMGREY_CAVEFISH
Comment 1 Wolfgang Rosenauer 2022-05-04 21:18:50 UTC
For me everything still works as always with TW and FF100.

The difference might be that I still have the packman libavcodec installed which supports everything.

I heard that some people of openSUSE/SUSE worked on getting H.264 support through openh264 but nobody ever talked to me as Firefox maintainer if there is anything I need to take care of.

I currently have
libavcodec58_134-4.4.1-10.6.x86_64
libavcodec57-3.4.9-1.28.x86_64
from Packman's Essentials installed and it's working fine.

What is installed for you?
ls -l /usr/lib64/libavcodec*
Comment 2 Paul Hands 2022-05-04 21:51:49 UTC
(In reply to Wolfgang Rosenauer from comment #1)
> For me everything still works as always with TW and FF100.
> 
> The difference might be that I still have the packman libavcodec installed
> which supports everything.
> 
> I heard that some people of openSUSE/SUSE worked on getting H.264 support
> through openh264 but nobody ever talked to me as Firefox maintainer if there
> is anything I need to take care of.
> 
> I currently have
> libavcodec58_134-4.4.1-10.6.x86_64
> libavcodec57-3.4.9-1.28.x86_64
> from Packman's Essentials installed and it's working fine.
> 
> What is installed for you?
> ls -l /usr/lib64/libavcodec*

I seem to have an assortment....

#yum list installed|grep -i libavcodec
ffmpeg-4-libavcodec-devel.x86_64                   4.4.1-10.6                                   @System
libavcodec56.x86_64                                2.8.18-1.25                                  @System
libavcodec57.x86_64                                3.4.9-1.28                                   @System
libavcodec58_134.x86_64                            4.4.1-10.6                                   @System
libavcodec59.x86_64                                5.0.1-16.3                                   @System


And they all come from the @system repo.
or, to use your ls command...

# ls -l /usr/lib64/libavcodec*
lrwxrwxrwx 1 root root       24 Apr 30 05:33 /usr/lib64/libavcodec.so -> libavcodec.so.58.134.100
lrwxrwxrwx 1 root root       23 Apr 11 23:52 /usr/lib64/libavcodec.so.56 -> libavcodec.so.56.60.100
-rwxr-xr-x 1 root root  9829248 Apr 11 23:53 /usr/lib64/libavcodec.so.56.60.100
lrwxrwxrwx 1 root root       24 Apr 30 05:27 /usr/lib64/libavcodec.so.57 -> libavcodec.so.57.107.100
-rwxr-xr-x 1 root root 11311712 Apr 30 05:27 /usr/lib64/libavcodec.so.57.107.100
lrwxrwxrwx 1 root root       24 Apr 30 05:33 /usr/lib64/libavcodec.so.58 -> libavcodec.so.58.134.100
lrwxrwxrwx 1 root root       24 Apr 30 05:33 /usr/lib64/libavcodec.so.58.134 -> libavcodec.so.58.134.100
-rwxr-xr-x 1 root root 12372264 Apr 30 05:33 /usr/lib64/libavcodec.so.58.134.100
lrwxrwxrwx 1 root root       23 Apr 30 07:16 /usr/lib64/libavcodec.so.59 -> libavcodec.so.59.18.100
-rwxr-xr-x 1 root root  5264704 Apr 30 07:16 /usr/lib64/libavcodec.so.59.18.100


I could try switching to the packman packages, but I've had tht break lots of stuff in the past....
Comment 3 Wolfgang Rosenauer 2022-05-05 06:38:08 UTC
The packman approach worked (and was required for H.264 support) for a long time. If you would like to switch you should only switch the ffmpeg packages and not everything to packman. (And set the priority of the repo lower.)

If you are scared to break your system you probably need to wait a bit until I can clarify the H.264 support situation via openh264 with others but it may not work yet out of the box.