Bug 726973

Summary: spice-server: regression: wrong resolution set for tablet
Product: Red Hat Enterprise Linux 6 Reporter: Alon Levy <alevy>
Component: spice-serverAssignee: Alon Levy <alevy>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1CC: cmeadors, dblechte, djasa, mkenneth, uril
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spice-server-0.8.2-3.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 15:21:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
fix by passing red_dispatcher surface_create by value none

Description Alon Levy 2011-07-31 15:52:02 UTC
Created attachment 516022 [details]
fix by passing red_dispatcher surface_create by value

Description of problem:
When not using an agent and using a tablet the resolution set after a primary creation can be wrong. This results in a non-functioning pointer.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. start a windows vm with the newest driver (0.1-8), tablet (-usb -usbtablet) and no vdagent (no virtio-serial) and a qxl device (-vga qxl)
2. change resolution repeatedly (start a cmd screen, do alt-enter
3. Either after boot or after a few rounds of 2. you will no longer be able to move the pointer anywhere (the actual limits to the pointer will be 16 on at least one axis)

Actual results:
pointer stops working

Expected results:
pointer should work

Additional info:

Comment 2 Alon Levy 2011-07-31 15:56:05 UTC
updated title: this is a regression introduced by the async patches for spice-server, brought in by the spice-server rebase (rhbz#723676)

Comment 6 errata-xmlrpc 2011-12-06 15:21:52 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.

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

Comment 7 David Jaša 2012-03-05 17:28:53 UTC
After a consultation with Marian, we've decided that no ongoing testing is needed.