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.
Host: windows server 2016
Guest: gen2, xorg-x11-server-Xorg-1.20.4-9.el7.x86_64, kernel-3.10.0-1101.el7.x86_64
Hi Alan, test with xorg-x11-server-Xorg-1.20.4-9.el7.x86_64 on Hyper-V 2016 host, the bug can not be reproduced.
1) Check the patches that fix 1665433 already come into rhel7.8(xorg-x11-server-Xorg-1.20.4-9.el7.x86_64), is this right? Could you help to add the fixed version?
2) According to Comment 7, this bug was set to "RHEL 7.8 GA blocker", so this is y-stream bug, we need to create another new 7.7.z bug, right?
Thanks!
(In reply to HuijingHei from comment #9)
> Host: windows server 2016
> Guest: gen2, xorg-x11-server-Xorg-1.20.4-9.el7.x86_64,
> kernel-3.10.0-1101.el7.x86_64
>
> Hi Alan, test with xorg-x11-server-Xorg-1.20.4-9.el7.x86_64 on Hyper-V 2016
> host, the bug can not be reproduced.
>
> 1) Check the patches that fix 1665433 already come into
> rhel7.8(xorg-x11-server-Xorg-1.20.4-9.el7.x86_64), is this right? Could you
> help to add the fixed version?
>
> 2) According to Comment 7, this bug was set to "RHEL 7.8 GA blocker", so
> this is y-stream bug, we need to create another new 7.7.z bug, right?
>
> Thanks!
Sorry, this comment is for Adam.
(In reply to HuijingHei from comment #10)
> (In reply to HuijingHei from comment #9)
> > Host: windows server 2016
> > Guest: gen2, xorg-x11-server-Xorg-1.20.4-9.el7.x86_64,
> > kernel-3.10.0-1101.el7.x86_64
> >
> > Hi Alan, test with xorg-x11-server-Xorg-1.20.4-9.el7.x86_64 on Hyper-V 2016
> > host, the bug can not be reproduced.
> >
> > 1) Check the patches that fix 1665433 already come into
> > rhel7.8(xorg-x11-server-Xorg-1.20.4-9.el7.x86_64), is this right? Could you
> > help to add the fixed version?
This particular issue was fixed as of -8, -9 added a fix for an unrelated issue.
> > 2) According to Comment 7, this bug was set to "RHEL 7.8 GA blocker", so
> > this is y-stream bug, we need to create another new 7.7.z bug, right?
No, this is the bug for 7.7.z, see comment #0.
(In reply to Adam Jackson from comment #11)
>
> This particular issue was fixed as of -8, -9 added a fix for an unrelated
> issue.
>
> > > 2) According to Comment 7, this bug was set to "RHEL 7.8 GA blocker", so
> > > this is y-stream bug, we need to create another new 7.7.z bug, right?
>
> No, this is the bug for 7.7.z, see comment #0.
Hi Adam, thanks for your reply! Could you help to add the fixed version field and change the status to ON_QA, then it will not block "RHEL 7.8 GA", thanks!
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, 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:1075