Red Hat Bugzilla – Bug 435763
Keyboard doesn't respond properly in virt-manager
Last modified: 2008-05-21 11:37:57 EDT
Description of problem:
In virt-manager, the keyboard repeats some characters when pressed once and
other times it doesn't respond at all to keyboard input for a second or two. I'm
not 100% sure if this is a general Xen issue (e.g. interrupts problem) or a
problem in virt-manager.
Version-Release number of selected component (if applicable):
RHEL5.2 beta (x86_64 paravirt) on a RHEL5.2 beta host (x86_64)
Steps to Reproduce:
1. Configure using versions above
2. Start paravirt host in virt-manager
3. Type in gnome-terminal
A single key press sometimes generates multiple characters or doesn't respond at
all. Occasionally it keeps printing the same character to the screen repeatedly.
Keyboard input also lags behind what is actually typed.
Keyboard should work as in normal RHEL installation.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time. This request will be
reviewed for a future Red Hat Enterprise Linux release.
The console is actually provided by gtk-vnc, so changing the component
*** Bug 437159 has been marked as a duplicate of this bug. ***
Set dev ack for Dan.
Created attachment 297833 [details]
Track based on scancode instead of keycode
Fix built into gtk-vnc-0.3.2-2.el5
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.