Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 805003

Summary: Mouse clicks are not synchronized with cursor after reopening spice session with a multi-screen guest
Product: Red Hat Enterprise Linux 8 Reporter: Chris Pelland <cpelland>
Component: spice-vdagent-winAssignee: Arnon Gilboa <agilboa>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: dblechte, mkrcmari, sgordon, sgrinber, tdosek, uril
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: vdagent-win-0.1-10 Doc Type: Bug Fix
Doc Text:
When re-opening a SPICE session on a multi-screen guest, mouse clicks were not synchronized with the cursor location correctly. An update has been made and mouse clicks are now synchronized correctly with the guest.
Story Points: ---
Clone Of: 757819 Environment:
Last Closed: 2012-04-18 18:21:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 757819    
Bug Blocks:    

Comment 2 Tomas Dosek 2012-04-10 13:10:47 UTC
RHEV-toolsSetup_3.0_37.iso
rhevm-userportal-3.0.3_0001-3.el6.x86_64

I could not reproduce the above specified scenario - everything worked, mouse was synchronised accurately both in windowed and full-screen mode.

Comment 3 Marian Krcmarik 2012-04-10 13:16:52 UTC
(In reply to comment #2)
> RHEV-toolsSetup_3.0_37.iso
> rhevm-userportal-3.0.3_0001-3.el6.x86_64
> 
> I could not reproduce the above specified scenario - everything worked, mouse
> was synchronised accurately both in windowed and full-screen mode.

You would need specific multi-monitor layout on guest, I can verify that I just need to check that exact the same version of spice vdagent was deployed inot guest tools as I did verification earlier.

Comment 6 Stephen Gordon 2012-04-16 14:39:12 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When re-opening a SPICE session on a multi-screen guest, mouse clicks were not synchronized with the cursor location correctly. An update has been made and mouse clicks are now synchronized correctly with the guest.

Comment 8 errata-xmlrpc 2012-04-18 18:21:56 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-2012-0494.html