Bug 1309234 - 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 6
Classification: Red Hat
Component: virt-viewer
Version: 6.8
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Virt Viewer Maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1267184
Blocks: 1166298 1166319 1278016
TreeView+ depends on / blocked
 
Reported: 2016-02-17 10:00 UTC by Xiaodai Wang
Modified: 2016-06-02 13:02 UTC (History)
16 users (show)

Fixed In Version: virt-viewer-2.0-14.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1267184
Environment:
Last Closed: 2016-05-10 21:22:28 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0832 0 normal SHIPPED_LIVE libgovirt, spice-gtk, usbredir, and virt-viewer bug fix update 2016-05-10 22:41:23 UTC

Comment 6 Xiaodai Wang 2016-03-07 03:35:15 UTC
I updated the package to latest versions.
$ rpm -q spice-gtk virt-viewer
spice-gtk-0.26-7.el6.x86_64
virt-viewer-2.0-14.el6.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 and the resolution are correct, too.

So move the bug from ON_QA to VERIFIED.

Comment 9 errata-xmlrpc 2016-05-10 21:22:28 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-0832.html


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