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 1032939 - Display 1 always pop out when using virt-viewer to relaunch guest
Summary: Display 1 always pop out when using virt-viewer to relaunch guest
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-viewer
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jonathon Jongsma
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1032936
Blocks: 1009648
TreeView+ depends on / blocked
 
Reported: 2013-11-21 09:36 UTC by tingting zheng
Modified: 2015-07-16 15:06 UTC (History)
9 users (show)

Fixed In Version: virt-viewer-0.6.0-8.el7
Doc Type: Bug Fix
Doc Text:
The first guest display was re-enabled after a guest reboot even when it was previously disabled on the guest. This update removes the fixed association between the the main guest window and a specific guest display number, which prevents the problem from occurring.
Clone Of: 1032936
Environment:
Last Closed: 2015-03-05 13:38:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0295 0 normal SHIPPED_LIVE virt-viewer bug fix and enhancement update 2015-03-05 17:33:00 UTC

Description tingting zheng 2013-11-21 09:36:29 UTC 
The bug can also be reproduced on rhel7,so cloned the bug.
version:
libvirt-1.1.1-12.el7.x86_64
virt-viewer-0.5.7-2.el7.x86_64
spice-gtk-0.20-6.el7.x86_64
spice-vdagent-0.14.0-5.el7.x86_64
spice-gtk3-0.20-6.el7.x86_64
spice-server-0.12.4-3.el7.x86_64
spice-glib-0.20-6.el7.x86_64
spice-xpi-2.8-4.el7.x86_64

+++ This bug was initially created as a clone of Bug #1032936 +++

Description
Display 1 always pop out when using virt-viewer to relaunch guest

Version:
libvirt-0.10.2-29.el6.1.x86_64
virt-viewer-0.5.6-8.el6.x86_64
spice-gtk-python-0.20-11.el6.x86_64
spice-xpi-2.7-24.el6.x86_64
spice-vdagent-0.14.0-2.el6.x86_64
spice-glib-0.20-11.el6.x86_64
spice-gtk-0.20-11.el6.x86_64
spice-server-0.12.4-6.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare a spice guest with qxl and spicevmc.
2.Boot the guest,use virt-viewer to launch the guest,disable display 1 and enable other displays,eg:display 2.
# virt-viewer $guest --spice-debug --debug > spice-debug-1.log
3.Close virt-viewer.
4.Use virt-viewer to relaunch the guest,both display 1 and display 2 will be launched,display 1 will show:waiting for display 1,see the screenshot.
# virt-viewer $guest --spice-debug --debug > spice-debug-2.log

Actual results：
As description.

Expected results:
Step 4,only display 2 launched.

Additional info:
1.Attached the spice debug info.
2.The issue can also be reproduced on rhel7.

--- Additional comment from tingting zheng on 2013-11-21 04:32:55 EST ---



--- Additional comment from tingting zheng on 2013-11-21 04:33:35 EST ---
Comment 2 CongDong 2013-12-17 05:44:40 UTC 
Can reproduce this with:
# rpm -qa virt-viewer
virt-viewer-0.5.7-3.el7.x86_64

Steps:
1.Prepare a spice guest with qxl and spicevmc.
2.Boot the guest,use virt-viewer to launch the guest,disable display 1 and enable other displays,eg:display 2.
# virt-viewer $guest --spice-debug --debug > spice-debug-1.log
3.Close virt-viewer.
4.Use virt-viewer to relaunch the guest,both display 1 and display 2 will be launched,display 1 will show:waiting for display 1,see the screenshot.
# virt-viewer $guest --spice-debug --debug > spice-debug-2.log

Result:
Display 1 come out, show a message:
Waiting for display 1 ...
Comment 3 RHEL Program Management 2014-03-24 05:50:39 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 5 Jonathon Jongsma 2014-08-19 15:28:03 UTC 
I'm investigating what it would take to fix this...
Comment 6 Jonathon Jongsma 2014-08-26 21:52:46 UTC 
Some patches posted to Mailing list, but they need careful review: https://www.redhat.com/archives/virt-tools-list/2014-August/msg00094.html
Comment 8 CongDong 2014-10-14 07:09:15 UTC 
Can reproduce with virt-viewer-0.6.0-7.el7.x86_64

VERIFY with: virt-viewer-0.6.0-8.el7.x86_64

Steps:
1.Prepare a spice guest with qxl and spicevmc.
2.Boot the guest,use virt-viewer to launch the guest,disable display 1 and enable other displays,eg:display 2.
# virt-viewer $guest --spice-debug --debug > spice-debug-1.log
3.Close virt-viewer.
4.Use virt-viewer to relaunch the guest
# virt-viewer $guest

Result:
Step4, only display 2 comes out

As the result, set VERIFIED.
Comment 10 errata-xmlrpc 2015-03-05 13:38:38 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-2015-0295.html
Note You need to log in before you can comment on or make changes to this bug.