Description of problem: Changes (such as higlighting Menu item when hovering over them with mouse cursor, rendering moved app window when moving it with mouse, rendering moving scroll bar when drawing it with mouse) caused my mouse movement are not rendered after migration. -It happens when remote-viewer window is resized before migration only. -It happens in client as well as server mouse mode (in server mode cursor disappears). -It happens on Linux as well as Windows guests. -It happens on RHEL6.2 as well as RHEL6.3 hosts. -It is observed until remote-viewer is closed/opened again. Because It happens on Linux/Windows clients in client/server mouse mode I assume It may be a bug in spice-gtk. Version-Release number of selected component (if applicable): spice-gtk-0.11-11.el6.x86_64 virt-viewer-0.5.2-9.el6.x86_64 spice-server-0.10.1-10.el6.x86_64 How reproducible: always Steps to Reproduce: 1. Connect to a Windows/Linux guest with spice agent installed and running. 2. Resize remote-viewer window to invoke guest resolution resize. 3. Migrate guest machine (keep mouse in guest, possibly move with it during migration). 4. Try to move an app window or invoke context menu and move over it with mouse. Actual results: Moved window is not rendered during moving it, Menu items are not highlighted as mouse is moving over them. Expected results: Rendered. Additional info:
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