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 1267184 - Monitor mapping doesn't properly adjust resolutions
Summary: Monitor mapping doesn't properly adjust resolutions
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-viewer
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.3
Assignee: Virt Viewer Maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1269918 (view as bug list)
Depends On: 1297830
Blocks: 1166298 1166319 1278016 1295396 1309234
TreeView+ depends on / blocked
 
Reported: 2015-09-29 09:08 UTC by Tomas Jamrisko
Modified: 2016-11-04 01:10 UTC (History)
12 users (show)

Fixed In Version: virt-viewer-2.0-7.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1278016 1309234 (view as bug list)
Environment:
Last Closed: 2016-11-04 01:10:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2229 0 normal SHIPPED_LIVE virt-viewer, libgovirt, spice-gtk, and usbredir bug fix and enhancement update 2016-11-03 13:26:58 UTC

Description Tomas Jamrisko 2015-09-29 09:08:16 UTC 
Description of problem:
Mapping client:guest monitors results in their resolutions being switched

Version-Release number of selected component (if applicable):
spice-gtk3-0.26-5.el7

How reproducible:
100%

Steps to Reproduce:
1. RHEL guest with agent running
2. Client with 2 screens of different resolutions
3. Creat mapping for the guest in client's configuration file, 2:1;1:2
4. Connect to the guest with -f option

Actual results:
Displays are mapped as expected, except that resolution still honors 1:1;2:2, which results in scaling.

Expected results:
Resolution set on individual displays should account for remapping.
Comment 2 Pavel Grunt 2015-09-29 09:31:04 UTC 
changing the component - virt-viewer takes care about monitor-mapping
Comment 3 Pavel Grunt 2015-09-29 09:48:29 UTC 
Tomas, is the guest also RHEL 7.2?
I cannot reproduce the bug here - the guest always adjust to the window size.

A patch fixing a similar issue was posted: https://www.redhat.com/archives/virt-tools-list/2015-May/msg00013.html
Comment 4 Tomas Jamrisko 2015-09-30 08:46:26 UTC 
No, the guest was RHEL6.7 (from nighlies), haven't tried with 7.2.
Comment 5 Jonathon Jongsma 2015-10-09 14:12:09 UTC 
*** Bug 1269918 has been marked as a duplicate of this bug. ***
Comment 6 Jonathon Jongsma 2015-10-09 14:16:35 UTC 
I just posted a patch to fix bug 1269918, but Pavel pointed out that this bug is the same. Here's the patch: https://www.redhat.com/archives/virt-tools-list/2015-October/msg00021.html
Comment 7 Fabiano Fidêncio 2015-10-21 13:26:34 UTC 
(In reply to Jonathon Jongsma from comment #6)
> I just posted a patch to fix bug 1269918, but Pavel pointed out that this
> bug is the same. Here's the patch:
> https://www.redhat.com/archives/virt-tools-list/2015-October/msg00021.html

These 2 additional patches are also needed: http://www.redhat.com/archives/virt-tools-list/2015-October/msg00066.html and http://www.redhat.com/archives/virt-tools-list/2015-October/msg00067.html
Comment 8 Fabiano Fidêncio 2015-10-21 18:07:06 UTC 
Just for the record, these are the necessary commits:
aff6c79ae080db286e4cb853cdfa02f2da0d0398
73b55b3e1b09c81cf72082b4ec49d66c79ba7dc7
96413a62663cb68f1559abac2c37b0eb80ddf4ab
Comment 9 Xiaodai Wang 2016-02-17 09:58:24 UTC 
I can reproduce it on rhel7.2 release version.
$ rpm -q virt-viewer
virt-viewer-2.0-6.el7.x86_64

Steps:
1. Prepare a env with two physical monitors.
2. Install a spice guest and modify the configuration file.
$ cat .config/virt-viewer/settings 
[83865c8a-7ded-46e1-b803-584de8de0412]
monitor-mapping=1:2;2:1

[virt-viewer]
ask-quit=false
3. Run "virt-viewer -c qemu:///system 83865c8a-7ded-46e1-b803-584de8de0412 -f"

Actual Result:
The two displays appear in correct monitors but the resolution are incorrect.

Additional Info:
This issue also exists in rhel6.7, so clone it to rhel6.7.
Comment 11 Xiaodai Wang 2016-04-14 08:04:08 UTC 
I verified this bug following the steps in #comment 9 with virt-viewer-2.0-7.el7.x86_64. And the resolutions on two monitors are correct.

So move the bug from ON_QA to VERIFIED now.
Comment 13 errata-xmlrpc 2016-11-04 01:10:37 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.

https://rhn.redhat.com/errata/RHBA-2016-2229.html
Note You need to log in before you can comment on or make changes to this bug.