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 1052328 - 1920x1200 resolution on RHEL guest causing functionality issues for mouse.
Summary: 1920x1200 resolution on RHEL guest causing functionality issues for mouse.
Keywords:
Status: CLOSED DUPLICATE of bug 1008312
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-vdagent
Version: 6.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-13 16:25 UTC by Ulhas Surse
Modified: 2019-04-28 09:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 21:45:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ulhas Surse 2014-01-13 16:25:08 UTC 
Description of problem:
The point about the mouse is that, when  try to increase resolution, the focus in not working, I mean, when I click, in the screen the click occurs about 4 o 5 cm away.

Version-Release number of selected component (if applicable):
spice-vdagent-0.12.0-4.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create a New Desktop with selection number of monitors from console tab.
2. After install, change resolution for monitors as 1920x1200
3. Try to access other monitors and click on screen.

Actual results:
Click happens 4-5 cm away from the point of click.

Expected results:
Click should be done at the point where clicked.

Additional info:
Guest operating system is RHEL 6.4 client system.
Comment 4 Jonathon Jongsma 2014-02-03 22:03:25 UTC 
I am unable to reproduce this.  Can you esplain the process in a bit more detail?

(In reply to Ulhas Surse from comment #0)
> Steps to Reproduce:
> 1. Create a New Desktop with selection number of monitors from console tab.
> 2. After install, change resolution for monitors as 1920x1200
> 3. Try to access other monitors and click on screen.

Rather than explaining the procedure at a high level, it is much more useful to explain exactly what steps you took (e.g. "open application X, click button Y, etc").

What does "create a new desktop" mean? 
What is the "console tab"?
How do you change the monitor resolution to 1920x1200?
Comment 5 Christophe Fergeau 2014-02-04 09:23:45 UTC 
(In reply to Jonathon Jongsma from comment #4)> 
> (In reply to Ulhas Surse from comment #0)
> > Steps to Reproduce:
> > 1. Create a New Desktop with selection number of monitors from console tab.

> What does "create a new desktop" mean? 
> What is the "console tab"?

1) makes sense in the context of the RHEV admin portal which asks you if you want to create a desktop or a server when creating a new VM, and which has a 'console' tab in its VM creation or configuration dialog.
Comment 6 Jonathon Jongsma 2014-02-04 16:02:36 UTC 
(In reply to Christophe Fergeau from comment #5)
> 1) makes sense in the context of the RHEV admin portal which asks you if you
> want to create a desktop or a server when creating a new VM, and which has a
> 'console' tab in its VM creation or configuration dialog.

Indeed, sorry about that.  But the remaining question is still important: How did you change the monitor resolution?  From within the guest? by resizing the client window?
Comment 7 Jonathon Jongsma 2014-02-04 16:18:36 UTC 
In case it's not clear, that question was directed to Ulhas Surse, not Christophe.  And the reason that I'm asking for more explicit details is that I've tried to reproduce this and was unsuccessful, so I want to make sure that I'm following the procedure exactly.
Comment 8 Jonathon Jongsma 2014-02-04 20:05:42 UTC 
OK, I finally managed to reproduce this, by disabling the "view > automatically resize" option and then changing the resolution from within the guest.  The left (primary) display seems fine, but the second display does indeed seem to be offset by several inches.
Comment 9 Jonathon Jongsma 2014-02-05 21:45:37 UTC 
After a bit of debugging, this looks like the exact same root issue as bug 1008312.

*** This bug has been marked as a duplicate of bug 1008312 ***
Note You need to log in before you can comment on or make changes to this bug.