Bug 36323

Summary: mouse lose synchronization in xp multi-monitor mode
Product: Spice Reporter: Emre Erenoglu <erenoglu>
Component: spice-gtkAssignee: Spice Bug List <spice-bugs>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Emre Erenoglu 2011-04-17 05:17:18 UTC 
Hi,

I'm running spiced qemu in my system. The guest system is Windows XP x86. The qxl drivers are loaded. Guest also has PS/2 and Tablet mouses configured.

qemu (with kvm) is 0.14. Spice server is 0.8.0, qxl drivers downloaded recently from the spice website (0.6.3).

When I use single qxl device, everything works OK. 

When I enable a second qxl device (multimonitor mode), then the mouse looses its pointer synchronization and I can no longer click where I want. The actual mouse clicks effect somewhere  generally 2 centimeters above and a bit to the left of the pointer I see in the screen.

Please let me know if you would need more info.
Comment 1 Marc-Andre Lureau 2011-06-16 07:11:34 UTC 
Emre, which client are you using: spicec or spice-gtk? version?

Also, do you have the agent running the guest? I suppose not, since we have seen before this kind of problem without it.

thanks for your help
Comment 2 Marc-Andre Lureau 2011-06-16 07:12:06 UTC 
(ok, just noticed you filed to gtk-client)
Comment 3 Emre Erenoglu 2011-06-16 07:15:10 UTC 
Yes. Thanks to the helpful developers in the mailing list, I managed to install the vdagent service inside the guest.

With the vdagent, there's no problem. So I'm happy now :)

I assume the problem continues to affect users who don't use the vdagent.

Emre
Comment 4 Marc-Andre Lureau 2013-04-10 15:43:49 UTC 
a lot of pointer improvements have been made since  2011, since there are no further reports or details, I am closing this bug for now, assuming it has been fixed.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.