Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2176279

Summary: [Regression] cannot enable H264 plugin
Product: Red Hat Enterprise Linux 8 Reporter: Joe Wright <jwright>
Component: firefoxAssignee: Jan Horak <jhorak>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.6CC: alanm, amike, casantos, desktop-qa-list, jhorak, JONATHAN.SATTELBERGER, jraising, mkolbas, sbarcomb, tpopela
Target Milestone: rcKeywords: Desktop, Regression
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2176276
: 2176280 (view as bug list) Environment:
Last Closed: 2023-03-08 07:45:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2176276, 2176281    
Bug Blocks: 2176280    

Description Joe Wright 2023-03-07 21:32:27 UTC
+++ This bug was initially created as a clone of Bug #2176276 +++

Description of problem:
- Cannot enable H264 plugin

Version-Release number of selected component (if applicable):
RHEL 7.9.z: Reproduced firefox-102.8.0-2.el7_9.x86_64
RHEL 8.6.z Version locked: Reproduced firefox-102.4.0-1.el8_6.x86_64
RHEL 8.7.z: Reproduced firefox-102.8.0-2.el8_7.x86_64
RHEL 9.1.z: Reproduced firefox-102.8.0-2.el9_1.x86_64

How reproducible:
- reproduced by customer and in-house

Steps to Reproduce:
- Update to latest for major release, or version locked EUS
- Demonstrate initial non-functionality in Firefox using https://www.webex.com/test-meeting.html 
- Start and join the test meeting to fully reproduce
- Note error message regarding h264 plugin (see webex-test.jpg)
- Close tab
- Go to about:addons, plugins, and select "always activate" for the OpenH264 plugin. Note that it is not enabled (plugin.jpg) initially
- Observe that it just sits with the message "OpenH264 Video Codec provided by Cisco Systems, Inc will be installed shortly" but the plugin never seems to install (see plugin-never-enables.jpg)
- Retest with the webex meeting and note that it still doesn't work, same error as before

Actual results:
- Plugin doesn't install/enable

Expected results:
- Plugin works

Additional info:

Comment 6 Tomas Popela 2023-03-08 07:45:32 UTC
It's enough to have just one bug opened as we're building Firefox for all RHEL releases from one SRPM.

*** This bug has been marked as a duplicate of bug 2176276 ***