Bug 1339491

Summary: Can't connect to any display if specifying nothing to monitor-mapping
Product: Red Hat Enterprise Linux 7 Reporter: Xiaodai Wang <xiaodwan>
Component: virt-viewerAssignee: Virt Viewer Maint <virt-viewer-maint>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: cfergeau, dblechte, fidencio, juzhou, mxie, mzhan, pgrunt, rbalakri, rduda, tzheng, virt-bugs, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-viewer-2.0-8.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1304648
: 1339500 (view as bug list) Environment:
Last Closed: 2016-11-04 01:20:00 UTC Type: Bug
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: 1304648    
Bug Blocks: 1339500    

Comment 5 Xiaodai Wang 2016-06-29 06:54:08 UTC 
I can reproduce it with virt-viewer-2.0-7.el7.x86_64, 

then updated to virt-viewer-2.0-8.el7.x86_64 and tried it again, it doesn't occur any more.

steps:
1. Set monitor-mapping to blank string
$ cat .config/virt-viewer/settings 
[4987d17c-4c07-432a-918d-47e1a1ad79fc]
monitor-mapping=
2. Wait for the guest startup and Login into the guest first.
3. lanuch virt-viewer with -f arguments.
$ virt-viewer -c qemu:///system rhel7.2-back-clone -f

Actual Result:
virt-viewer can open guest successfully and there is a warning message in terminal.

(virt-viewer:908): virt-viewer-WARNING **: Empty monitor-mapping configuration

so move this bug from ON_QA to VERIFIED.
Comment 7 errata-xmlrpc 2016-11-04 01:20:00 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