Bug 835997
Summary: | Changes caused by mouse movement are not rendered after migration. | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Marian Krcmarik <mkrcmari> | ||||
Component: | spice-gtk | Assignee: | Christophe Fergeau <cfergeau> | ||||
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.3 | CC: | acathrow, cfergeau, dblechte, dyasny, yhalperi | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | spice-gtk-0.14-1.el6 | Doc Type: | Bug Fix | ||||
Doc Text: |
Cause: SPICE motion messages were not properly synchronized between client and server after migration
Consequence: Mouse state can get out of sync after migration
Fix: Make sure SPICE motion messages are synchronized between client and server
Result: Mouse state no longer gets out of sync after migration
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-02-21 08:47:55 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: | |||||||
Attachments: |
|
Description
Marian Krcmarik
2012-06-27 18:53:26 UTC
Created attachment 595628 [details]
patch for keeping the count of motion msgs in sync between the server and the client
The counting of motion messages was not synchronized between the client and the server after migration. This can lead to not delivering mouse motion updates to the guest; while mouse press events are still sent. This can explain the behavior Marian described.
The attached patch synchronized the mouse count.
Hi Marian, Can you try this scratch build https://brewweb.devel.redhat.com/taskinfo?taskID=4565938 ? Thanks. 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-2013-0343.html |