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.
RHEL 7 currently ships vte291-0.52.2. vte291-0.52.4 is the latest stable bug-fix release from that branch. It contains a very conservative set of bug-fixes for the 0.52.x series of releases.
There are two competing concerns here.
One is that RHEL 7 is at a very advanced point in its lifecycle, which means that we need to be very conservative about every change we make. At the same time vte291 is one of the most commonly used components, so every little bug-fix does really matter.
I am still evaluating the potential impact of this update. In the meantime, I am filing this to get started with the paperwork.
(In reply to Debarshi Ray from comment #0)
> I am still evaluating the potential impact of this update. In the meantime,
> I am filing this to get started with the paperwork.
I feel confident in the changes in the vte-0-52 branch. They are targetted bug-fixes that have been shipped in Fedora 29 and onwards without any known fall out from them.
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 (GNOME 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:3987