Hide Forgot
Description of problem: Can't connect to any display if specifying nothing to monitor-mapping. Version-Release number of selected component (if applicable): virt-viewer-2.0-13.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Set monitor-mapping to blank string. # cat .config/virt-viewer/settings #rhel7.2-back-clone [d622b6f8-fdee-ad9c-63fe-cac2e9b6200d] monitor-mapping= 2. Wait for the guest startup and Login into the guest first. 3. lanuch virt-viewer with -f arguments. # virt-viewer rhel7.2-back-clone -f Actual results: "Connected to graphic sever" screen displays and can't connect to any display. Expected results: virt-viewer should ignore the monitor-mapping settings and connect to correct displays. Additional info: This issue doesn't occur on rhel7.2.
We already had this discussion, more than once, but why the tests are being done using root instead of a normal user? :-\
(In reply to Fabiano Fidêncio from comment #2) > We already had this discussion, more than once, but why the tests are being > done using root instead of a normal user? :-\ Hi, I tested this problem with root user and normal user. Both of them have same problem.
Fixed upstream: https://git.fedorahosted.org/cgit/virt-viewer.git/commit/?id=fcb200e3d4452ebf53d2205603ac18305104806b
Hi fidencio, For this bug, the empty value problem is resolved. But if specify <CLIENT_MONITOR-ID> greater than the real monitor count, it still can't connect to any display. #rhel7.2-back-clone [d622b6f8-fdee-ad9c-63fe-cac2e9b6200d] monitor-mapping=1:5 Should i file a new bug for it or just change the status of this bug? Thanks
According comment 8, this bug is fixed. and filed a new bug for another problem. https://bugzilla.redhat.com/show_bug.cgi?id=1315206 So move this bug from ON_QA to VERIFIED.
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