Bug 1157981

Summary:	'NUM LOCK' works reversely with host after reboot guest
Product:	Red Hat Enterprise Linux 7	Reporter:	xiagao
Component:	spice-gtk	Assignee:	Default Assignee for SPICE Bugs <rh-spice-bugs>
Status:	CLOSED ERRATA	QA Contact:	SPICE QE bug list <spice-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	coli, dblechte, djasa, hhuang, huding, jjongsma, juzhang, marcandre.lureau, mazhang, rbalakri, tjamrisk, tpelka, virt-maint, xfu, xiagao
Target Milestone:	rc
Target Release:	7.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spice-gtk-0.26-3.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 07:34:49 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 xiagao 2014-10-28 07:43:09 UTC

Description of problem:
boot guest with 'NUM LOCK' on and reboot guest in remote-viwer with spice,when the guest boots up,the numeric keypad works reversely with host.


Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.1.2-3.el7.x86_64
spice-server-0.12.4-7.el7.x86_64

How reproducible:
90%

Steps to Reproduce:
1. boot guest with "NUM LOCK" on
2. reboot guest
# reboot
3. input something at numeric keypad with "NUM LOCK" on and off.

Actual results:
can't input number from the numeric keypad works with 'NUM LOCK' on,it works reversely with host.

Expected results:


Additional info:
1.cmd
/usr/libexec/qemu-kvm \
-name 'virt-tests-vm1' \
-sandbox off \
-M pc-i440fx-rhel7.1.0 \
-m 8192 \
-smp 8,sockets=2,cores=2,threads=2 \
-S \
-rtc base=localtime,clock=host,driftfix=slew \
-k en-us \
-nodefaults \
-device nec-usb-xhci,id=usb0,bus=pci.0,addr=0x5 \
-device usb-tablet,id=tablet1,bus=usb0.0,port=1 \
-no-shutdown \
-enable-kvm \
-chardev socket,id=serial_xiagao,path=/tmp/xiagao,server,nowait \
-device isa-serial,chardev=serial_xiagao \
-drive file=/home/v1/img/RHEL-Server-7.1-64-ide.qcow2,if=none,id=drive-ide0-0-0,media=disk,format=qcow2,snapshot=off,aio=native,cache=writeback \
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 \
-drive file=/home/v1/img/disk1.raw,if=none,id=drive-disk,format=raw,snapshot=off,aio=native,cache=none,rerror=stop,werror=stop \
-device ide-drive,drive=drive-disk,id=ide1-0-0 \
-netdev tap,id=hostnet0,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown \
-device e1000,netdev=hostnet0,id=net0,mac=52:54:00:ae:a4:95 \
-vga qxl \
-spice port=5905,disable-ticketing \
-boot menu=on \
-monitor stdio

2.note:
vnc works, but spice doesn't.

Comment 2 Gerd Hoffmann 2014-11-05 11:17:35 UTC

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.

Comment 3 Gerd Hoffmann 2014-11-18 11:24:07 UTC

> Reassigning to spice for investigation.

Oops, forgot to actually reassign.

Comment 4 Marc-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

Comment 5 Jonathon Jongsma 2015-01-05 17:05:52 UTC

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.

Comment 6 xiagao 2015-01-15 08:05:16 UTC

(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

Comment 7 Jonathon Jongsma 2015-01-15 16:07:39 UTC

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 11 Jonathon Jongsma 2015-06-05 16:08:24 UTC

There are now 0.26 builds for RHEL 7.2. Moving to modified.

Comment 17 errata-xmlrpc 2015-11-19 07:34:49 UTC

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