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 823019 - Mouse clicks are not synchronized with cursor when display is scaled up
Summary: Mouse clicks are not synchronized with cursor when display is scaled up
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-vdagent-win
Version: ---
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Arnon Gilboa
QA Contact: Desktop QE
URL:
Whiteboard:
: 834999 (view as bug list)
Depends On:
Blocks: 835194
TreeView+ depends on / blocked
 
Reported: 2012-05-18 19:25 UTC by Marc-Andre Lureau
Modified: 2019-10-10 14:20 UTC (History)
10 users (show)

Fixed In Version: vdagent-win-0.1-11
Doc Type: Bug Fix
Doc Text:
spice-gtk relies on agent best resolution match when resizing the display.There is a mouse offset when there is no exact match between the client display and the guest resolution. An update has been made to ensure that the vdagent starts correctly and these problems will no longer occur. As a result the guest's mouse will now respond correctly to user input.
Clone Of:
: 835194 (view as bug list)
Environment:
Last Closed: 2012-12-04 18:17:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:1502 0 normal SHIPPED_LIVE new package: spice-vdagent-win 2012-12-04 23:07:17 UTC

Description Marc-Andre Lureau 2012-05-18 19:25:34 UTC
Description of problem:

spice-gtk rely on agent best resolution match when resizing the display.

There is a mouse offset when there is no exact match between the client display and the guest resolution

Version-Release number of selected component (if applicable):
vdagent from git, and previous releases (probably current supported rhev release too), unfortunately, the tags seems to be missing in upstream repo.

How reproducible:
100%

Steps to Reproduce:
1. run spicy with "Resize guest to best match"
2. resize client to a non-exact match (for example, 1400x480)
3. move cursor to bottom-right corner

  
Actual results:
observe the mouse is off (depending on ratio client/guest)

Expected results:
Guest mouse should be under client pointer.

Comment 1 Christophe Fergeau 2012-06-25 08:36:18 UTC
This is fixed by http://cgit.freedesktop.org/spice/win32/vd_agent/commit/?id=b4e9afc721882ae14fe9e720a3cd113701cf9f8e if I'm not mistaken

Comment 4 Marc-Andre Lureau 2012-07-02 14:04:39 UTC
*** Bug 834999 has been marked as a duplicate of this bug. ***

Comment 9 errata-xmlrpc 2012-12-04 18:17:07 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-1502.html


Note You need to log in before you can comment on or make changes to this bug.