Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 952715

Summary:	Virt-Viewer: MultiMonitor: X & Y coordinates are incorrect when bringing a 2nd display that is not enabled
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Vimal Patel <vipatel>
Component:	mingw-virt-viewer	Assignee:	Marc-Andre Lureau <marcandre.lureau>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	acathrow, bsanford, cfergeau, djasa, mkrcmari, pvine
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-22 19:37:01 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 Vimal Patel 2013-04-16 14:25:16 UTC

Description of problem:
When doing displaying a 2nd monitor, which is not enabled on the guest, the one display that does work, the cursor and where the mouse clicks are different x, y coordinates, they should be in sync.

*Tested on Windows 7 x86_64 client & Windows 7 x86_64 guest

Version-Release number of selected component (if applicable):
RHEVM 3.2, Beta 2.1, SF 13.1

Client:
Spice Client updated: rhevm-spice-client-x86|64-cab-3.2-9

Guest:
RHEV-Tools-Setup 3.2-5 

How reproducible:
100%

Steps to Reproduce:
1. Install windows 7 guest 64 bit, enable two monitors
2. install tools
3. don't enable the 2nd displays on guest
4. display both monitors
5. do some mouse click and drags (the cursor and where clicked are different x, y coordinates)
  
Actual results:
X & Y coordinates of the cursor and where clicked are not in sync.

Expected results:
X & Y coordinates of the cursor and mouse clicks should be in sync.

Additional info:

Comment 1 David Jaša 2013-04-19 19:28:46 UTC

this bug can also be reproduced using exact steps of bug 953984.

Comment 2 Marc-Andre Lureau 2013-04-22 19:37:01 UTC

dup of 912793

*** This bug has been marked as a duplicate of bug 912793 ***