Bug 444815

Summary: PVFB's NumLock doesn't stay in sync with host's
Product: Red Hat Enterprise Linux 5 Reporter: Markus Armbruster <armbru>
Component: xenAssignee: Miroslav Rezanina <mrezanin>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 5.2CC: clalance, leiwang, llim, mrezanin, sandy.garza, tao, xen-maint
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: xen-3.0.3-111.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-13 22:16:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 514498    

Description Markus Armbruster 2008-04-30 19:05:42 UTC 
Description of problem:
The guest's NumLock state can get out of sync with the host's.

Version-Release number of selected component (if applicable):
Last observed with kernel-xen-2.6.18-91.el5 in the guest, and xen-3.0.3-64.el5
in the host.

How reproducible:
Always

Steps to Reproduce:
1. Start PVFB guest, open its graphical console
2. Check status of guest NumLock (use gdm's user name entry to test), and status
of host NumLock in a suitable host window (e.g. terminal)
3. Toggle NumLock in the guest console window, check again
4. Toggle NumLock outside the guest console window, check again
  
Actual results:
Initial state of guest's NumLock may or may not match hosts.  Step 3 toggles
both host's and guest's NumLock.  Step 4 toggles only host's NumLock.

Expected results:
Initial state matches, and stays in sync through steps 3 and 4.
Comment 3 Miroslav Rezanina 2010-05-14 07:59:43 UTC 
Partialy fixed by patch for bz #552612. However, there is errors in keyboard layout parsing to get NumLock synchronization to work properly.
Comment 11 Michal Novotny 2010-10-04 07:11:57 UTC 
*** Bug 475213 has been marked as a duplicate of this bug. ***
Comment 13 errata-xmlrpc 2011-01-13 22:16:16 UTC 
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 therefore 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.

http://rhn.redhat.com/errata/RHBA-2011-0031.html