Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJonathon Jongsma
2014-10-15 21:43:40 UTC
When connecting to a guest with virt-viewer (or remote-viewer) in --full-screen mode, virt-viewer immediately sends down a monitor configuration message as soon as the agent is connected.
If there are more monitors currently-enabled in the guest than are specified in the configuration message, the additional monitors do not always get disabled.
This is not always repeatable and seems racy.
Created attachment 947355[details]
spice debug log
This log illustrates the issue. Notice how initially the client sends down a new monitor configuration:
../../gtk/channel-main.c:1078 main-1:0: monitor config: #0 1600x900+1680+0 @ 32 bpp
../../gtk/channel-main.c:1078 main-1:0: monitor config: #1 1680x1050+0+0 @ 32 bpp
but the first monitors configuration data we receive from the server still shows the old configuration:
../../gtk/channel-display.c:1734 display-2:0: monitor id: 0, surface id: 0, +0+0-688x531
../../gtk/channel-display.c:1734 display-2:0: monitor id: 1, surface id: 0, +688+0-728x519
../../gtk/channel-display.c:1734 display-2:0: monitor id: 2, surface id: 0, +1416+0-896x705
Comment 3Marc-Andre Lureau
2015-01-05 11:38:25 UTC
Will be fixed in virt-viewer the same way as the bug 1212802
Relevant upstream commits:
4d6f730fce9818beb9f5d2639ffad256b9ede391
1f2ef0e9de4133c375df3b20993c93d66fa7f172
7870ea5eff91dd163e43f85b4168dd35def0e3e2
724744ca209297322b04cd9ed11e898a3d68a281
Comment 15Fabiano Fidêncio
2016-03-15 12:41:34 UTC
(In reply to Pavel Grunt from comment #13)
> Will be fixed in virt-viewer the same way as the bug 1212802
>
> Relevant upstream commits:
We need, before applying these 4 patches, to apply a860b2f7d7ab7f50ccd9f89f46014d8972d94a2c
> 4d6f730fce9818beb9f5d2639ffad256b9ede391
> 1f2ef0e9de4133c375df3b20993c93d66fa7f172
> 7870ea5eff91dd163e43f85b4168dd35def0e3e2
> 724744ca209297322b04cd9ed11e898a3d68a281
Comment 16Fabiano Fidêncio
2016-03-15 12:42:06 UTC
(In reply to Fabiano Fidêncio from comment #15)
> (In reply to Pavel Grunt from comment #13)
> > Will be fixed in virt-viewer the same way as the bug 1212802
> >
> > Relevant upstream commits:
>
> We need, before applying these 4 patches, to apply
> a860b2f7d7ab7f50ccd9f89f46014d8972d94a2c
Argh, 344eb9a68595ee26627e27fe733ac7789fdbdbb1
>
> > 4d6f730fce9818beb9f5d2639ffad256b9ede391
> > 1f2ef0e9de4133c375df3b20993c93d66fa7f172
> > 7870ea5eff91dd163e43f85b4168dd35def0e3e2
> > 724744ca209297322b04cd9ed11e898a3d68a281
I can reproduce it with virt-viewer-2.0-6.el7.x86_64.
# rpm -q virt-viewer
virt-viewer-2.0-6.el7.x86_64
Steps:
1. Configure monitor-mapping settings in ~/.config/virt-viewer/settings.
For example:
# cat /home/xiaodwan/.config/virt-viewer/settings
[83865c8a-7ded-46e1-b803-584de8de0412]
monitor-mapping=1:2
2. Open the guest with virt-viewer and open 4 displays, then keep 4 displays open and close the virt-viewer window.
3. Open the guest with virt-viewer command with "-f" options.
4. Try it several times.
Actual Result:
Sometimes display 2 and display 3 are not closed and "Waiting for display ...." appear in the dispaly.
Upgraded the version to latest virt-viewer-2.0-7.el7.x86_64 and verify it again. I tried it about 10 times and cannot reproduce it.
So move the 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-2229.html