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.
The non-working keys have been fixed in bug 1352765 already - this ticket here is about the silencing the "key event queue full" warning messages from QEMU.
According to Description,
Verified it on build qemu-kvm-rhev-2.6.0-22.el7,the issue has been fixed.
According to comment 3,
To my opinion,verified failed because the mouse cannot work at all after guest boot up but the error message was gone.
As the original bug was closed as duplicated,should we reopen it or report new ?
(In reply to dengmin from comment #6)
> To my opinion,verified failed because the mouse cannot work at all after
> guest boot up but the error message was gone.
> As the original bug was closed as duplicated,should we reopen it or report
> new ?
OK, thanks for testing! I'd suggest to open a new bug, since BZ 1348422 was only about the error messages according to the bug description. So I think it is less confusing to have a new bug instead for the non-working mouse.
(In reply to Thomas Huth from comment #7)
> (In reply to dengmin from comment #6)
> > To my opinion,verified failed because the mouse cannot work at all after
> > guest boot up but the error message was gone.
> > As the original bug was closed as duplicated,should we reopen it or report
> > new ?
>
> OK, thanks for testing! I'd suggest to open a new bug, since BZ 1348422 was
> only about the error messages according to the bug description. So I think
> it is less confusing to have a new bug instead for the non-working mouse.
Open a new bug for tracing new issue - Bug 1371054
Base on comment 6,the original issue has been fixed and another issue will be traced in new Bug 1371054.
So we take it as fixed and move it to verified.Thanks a lot.
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://rhn.redhat.com/errata/RHBA-2016-2673.html