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.

If we don't rebase spice-gtk for 7.3, I think we should backport the fixes mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1302095#c23 to the spice-gtk package:
« https://bugzilla.redhat.com/show_bug.cgi?id=1040679
http://cgit.freedesktop.org/spice/spice-gtk/commit/?id=3bf5ef7dc32da6349e82c0bc39b7884ce6d517de
http://cgit.freedesktop.org/spice/spice-gtk/commit/?id=01540664bd0608a02a0be787eb548709f3d68fe1 »

They should avoid the kind of issues hit by the customer in rhbz#1302095

spice-gtk-0.26-5.el7 has the fixes due to bug 1182252