Created attachment 1887508 [details] Firefox message Description of problem: odysee, embedded video on twitter and some other web-sites cannot be played. Version-Release number of selected component (if applicable): - firefox-101.0-1.fc36.x86_64 - mozilla-openh264-2.2.0-1.fc36.x86_64 How reproducible: 100% Steps to Reproduce: 1. Update firefox from 100 to 101 2. Open odysee.com/twitter.com for example 3. Try to play video/embedded video Actual results: Video cannot be played. Respective message is shown on twitter and infinite loading animation is displayed on odysee. Also firefox is showing a message for missing codec. I've made sure all the suggestions from https://bodhi.fedoraproject.org/updates/FEDORA-2022-080ea50338#comment-2554974 are correct, but still this isn't working for me. YouTube playback is unaffected. Expected results: Video is played just it was on Firefox 100. Additional info: Downgrade to firefox 100 instantly restores the functionality. This is a problem on my desktop with AMDGPU (RX 6700XT) if it matters.
Created attachment 1887509 [details] about:config
Created attachment 1887510 [details] Twitter error
Created attachment 1887511 [details] Odysee
Please attach content of about:plugins and try to remove ffmpeg-free packages if they're installed.
(In reply to Martin Stransky from comment #4) > Please attach content of about:plugins and try to remove ffmpeg-free > packages if they're installed. Here is a content of about:plugins: OpenH264 Video Codec provided by Cisco Systems, Inc. File: system-installed Path: /home/agurenko/.mozilla/firefox/72w8miv5.default-release/gmp-gmpopenh264/system-installed Version: system-installed This plugin is automatically installed by Mozilla to comply with the WebRTC specification and to enable WebRTC calls with devices that require the H.264 video codec. Visit https://www.openh264.org/ to view the codec source code and learn more about the implementation. Widevine Content Decryption Module provided by Google Inc. File: 4.10.2449.0 Path: /home/agurenko/.mozilla/firefox/72w8miv5.default-release/gmp-widevinecdm/4.10.2449.0 Version: 4.10.2449.0 State: Enabled This plugin enables playback of encrypted media in compliance with the Encrypted Media Extensions specification. Encrypted media is typically used by sites to protect against copying of premium media content. Visit https://www.w3.org/TR/encrypted-media/ for more information on Encrypted Media Extensions. $ rpm -q ffmpeg-free 0 1 package ffmpeg-free is not installed
What do you get from rpm -qa ffmpeg\* terminal command?
(In reply to Martin Stransky from comment #6) > What do you get from > > rpm -qa ffmpeg\* > > terminal command? I get no output.
Hm, just installed VLC which brought a lot of dependencies including ffmpeg-libs-5.0.1-3.fc36.x86_64 and now it's working. Is that a change from FF100 -> FF101 that it relies on a system libs instead of built-ins? If so, should FF package bring ffmpeg-libs as a dependency?
(In reply to Gurenko Alex from comment #8) > Hm, just installed VLC which brought a lot of dependencies including > ffmpeg-libs-5.0.1-3.fc36.x86_64 and now it's working. Is that a change from > FF100 -> FF101 that it relies on a system libs instead of built-ins? If so, > should FF package bring ffmpeg-libs as a dependency? We can't install ffmpeg-libs by default as it contains patented things and it's provided by rpmfusion.org project. So it looks like your system was correctly installed and you seen just openh264 bugs there. Firefox uses ffmpeg-libs when they're installed since gstreamer support removal years ago, there's no change on Firefox side there.
(In reply to Martin Stransky from comment #9) > (In reply to Gurenko Alex from comment #8) > > Hm, just installed VLC which brought a lot of dependencies including > > ffmpeg-libs-5.0.1-3.fc36.x86_64 and now it's working. Is that a change from > > FF100 -> FF101 that it relies on a system libs instead of built-ins? If so, > > should FF package bring ffmpeg-libs as a dependency? > > We can't install ffmpeg-libs by default as it contains patented things and > it's provided by rpmfusion.org project. > So it looks like your system was correctly installed and you seen just > openh264 bugs there. > Firefox uses ffmpeg-libs when they're installed since gstreamer support > removal years ago, there's no change on Firefox side there. Right, I forgot it came from rpmfusion. So the bug is still on the openh264 side? Should I move this issue/discussion to Mozilla's bugzilla?
(In reply to Gurenko Alex from comment #10) > (In reply to Martin Stransky from comment #9) > > (In reply to Gurenko Alex from comment #8) > > > Hm, just installed VLC which brought a lot of dependencies including > > > ffmpeg-libs-5.0.1-3.fc36.x86_64 and now it's working. Is that a change from > > > FF100 -> FF101 that it relies on a system libs instead of built-ins? If so, > > > should FF package bring ffmpeg-libs as a dependency? > > > > We can't install ffmpeg-libs by default as it contains patented things and > > it's provided by rpmfusion.org project. > > So it looks like your system was correctly installed and you seen just > > openh264 bugs there. > > Firefox uses ffmpeg-libs when they're installed since gstreamer support > > removal years ago, there's no change on Firefox side there. > > Right, I forgot it came from rpmfusion. So the bug is still on the openh264 > side? Should I move this issue/discussion to Mozilla's bugzilla? openh264 is provided by Cisco so you can file a bug here: https://github.com/cisco/openh264/issues
Updating to firefox-101.0-1.fc36.x86_64 broke video on some sites, and downgrading back to firefox-100.0-2.fc36.x86_64 fixes it. I don't have anything installed from rpm fusion. $ rpm -qa ffmpeg\* (no results) Maybe I should file a separate bug as this is a pretty clear regression from a recent clean install without any non-Fedora packages installed.
Here's an example site: https://weather.com/news/weather/video/california-restricting-water-usage-in-some-parts-of-the-state?cm_ven=hp-slot-4
FEDORA-2022-9277f357d1 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9277f357d1
FEDORA-2022-9277f357d1 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-950e0f78c7 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-950e0f78c7
FEDORA-2022-0e2ff84e1e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0e2ff84e1e
FEDORA-2022-0e2ff84e1e has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-0e2ff84e1e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0e2ff84e1e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-950e0f78c7 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-950e0f78c7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-950e0f78c7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-950e0f78c7 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-d1c8a76563 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-f0988ea008 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f0988ea008
FEDORA-2022-f0988ea008 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.