Bug 880883
Summary: | atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0). | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Chao Yang <chayang> |
Component: | spice-gtk | Assignee: | Christophe Fergeau <cfergeau> |
Status: | CLOSED DUPLICATE | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.4 | CC: | acathrow, alevy, areis, armbru, bsarathy, cfergeau, chayang, dblechte, dyasny, ezubillaga, ipilcher, juzhang, marcandre.lureau, michen, mkenneth, qzhang, shuang, virt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-05-29 11:39:58 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chao Yang
2012-11-28 03:14:05 UTC
I am seeing the same thing with a RHEL 6.3 guest on a Fedora 18 host. Every keypress in the (SPICE) console results in the message being printed. Needless to say, this makes it extremely difficult to use the console, although it does still work. This guest worked find on Fedora 17, with the virt-preview repository enabled. The guest was moved to Fedora 18 by 'virsh defining' the F17 XML file. The problem does not occur when I change the display type to VNC (with cirrus video). Same here, changing the display type to VNC solves the problem. The video card type (cirrus, qxl, etc) doesn't make any difference on my experience. Using F18 host with custom 3.0 Linux guest. Which client is in use? (this goes for the original poster and anyone who managed to reproduce) (In reply to Alon Levy from comment #6) > Which client is in use? (this goes for the original poster and anyone who > managed to reproduce) It's remote-viewer in use. (In reply to chayang from comment #7) > (In reply to Alon Levy from comment #6) > > Which client is in use? (this goes for the original poster and anyone who > > managed to reproduce) > > It's remote-viewer in use. Which version? this should be fixed in spice-gtk 0.15, commit eec5f937150e9bc65e02b80ea06bd4bad3a90978 Assuming retesting confirms it's fixed: Marc-Andre, got an RHBZ for spice-gtk commit eec5f93? If yes, this bug can be closed as duplicate of it. If no, this bug can be used to track it. I don't think there is any bug for it. It is not reproducible with qemu-kvm-0.12.1.2-2.369.el6.x86_64, host kernel-2.6.32-376.el6.x86_64, RHEL6.4 GA guest if connect guest either with spice-gtk-0.14-7.el6.x86_64 in rhel6 or spice-gtk3-0.18-1.fc18.x86_64 in F18. Hi Marc-Andre, Markus, Is there any relevant fix in either qemu-kvm or kernel? Cause I cannot reproduce this issue with above combination. (In reply to chayang from comment #12) > It is not reproducible with > qemu-kvm-0.12.1.2-2.369.el6.x86_64, host kernel-2.6.32-376.el6.x86_64, > RHEL6.4 GA guest if connect guest either with spice-gtk-0.14-7.el6.x86_64 in > rhel6 or spice-gtk3-0.18-1.fc18.x86_64 in F18. > > Hi Marc-Andre, Markus, > Is there any relevant fix in either qemu-kvm or kernel? Cause I cannot > reproduce this issue with above combination. The spice-gtk fix has been backported to to RHEL, and is available since spice-gtk 0.15. You would need older spice-gtk version to reproduce. This is a spice-gtk bug, and it has already been fixed. The big should be closed as duplicate of whatever bug is associated with the fix. Since I don't know which one to use, I'm reassigning to spice-gtk. found it, bug 868237 *** This bug has been marked as a duplicate of bug 868237 *** |