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.

Fix for https://bugzilla.redhat.com/show_bug.cgi?id=1803811 has a regression, reported upstream [0].

The regression breaks hardware acceleration of video encoding/decoding, which could make things like streaming and video watching on high resolutions slow and stutter. Seems to be affecting Firefox and Chromium, so the impact is broad.

Note that hardware accelerated video encoding/decoding for Firefox is quite new, so it wouldn't be a huge change, but still a bad surprise to our customers if they have heard about it.

We should try to fix it in RHEL 7.9 on z-stream, once a fix upstream is available.

[0] https://gitlab.freedesktop.org/mesa/mesa/-/issues/2882

The impact is still not fully known, but at this point we know that certain configurations of Chromium are affected, and Firefox seems to be generally affected.

We believe that the best approach to address this issue is to revert the change included in https://bugzilla.redhat.com/show_bug.cgi?id=1803811, which introduced this regression. This is safe to do, as we are basically coming back to what we had before. Requesting exception.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (mesa bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3990