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.
Hmm, qemu notifies spice-server about the kbd led changes, to allow for syncronization here, and IIRC this used to work correctly in the past.
Reassigning to spice for investigation. Could also be a spice client bug though.
> Reassigning to spice for investigation.
Oops, forgot to actually reassign.
Comment 4Marc-Andre Lureau
2015-01-05 11:27:36 UTC
I can't reproduce (although I am testing with f21 client/host/guest). This is probably not a regression, right? afaik, nothing has changed much in this area, moving to 7.2. Can you try to reproduce with f21 client? and provide SPICE_DEBUG=1 log? thanks
FYI, a similar bug was fixed in spice-gtk commit d06b256710cf91aec1275785d8cd65283581f544. If you're using a client that uses spice-gtk and your version of spice-gtk is less than 0.26, you may run into this issue. Which version of spice-gtk do you have on the client?
If this is same bug you are seeing, it is indeed not a regression.
(In reply to Jonathon Jongsma from comment #5)
> FYI, a similar bug was fixed in spice-gtk commit
> d06b256710cf91aec1275785d8cd65283581f544. If you're using a client that uses
> spice-gtk and your version of spice-gtk is less than 0.26, you may run into
> this issue. Which version of spice-gtk do you have on the client?
>
1. client:spice-gtk3-0.20-8.el7.x86_64 -->fail
2. client:spice-gtk3-0.22-2.el7.x86_64 -->fail
I can get the highest Spice-gtk version from brew is spice-gtk-0.22-2.el7.Can you provide 0.26 version for rhel7.1?
thanks,
xiagao
Right, since the version of spice-gtk you're using is < 0.26, it's expected to have this issue. Providing a new version of spice-gtk that contains this fix is the goal of this bug. Moving to POST.
Comment 11Jonathon Jongsma
2015-06-05 16:08:24 UTC
There are now 0.26 builds for RHEL 7.2. Moving to modified.
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-2015-2211.html