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 1021862 - virt-viewer can not configure multi-dispalys optionally
Summary: virt-viewer can not configure multi-dispalys optionally
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-viewer
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Virt Viewer Maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1021845
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-22 08:43 UTC by CongDong
Modified: 2015-05-11 22:16 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1021845
Environment:
Last Closed: 2013-12-16 07:44:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description CongDong 2013-10-22 08:43:24 UTC
+++ This bug was initially created as a clone of Bug #1021845 +++
Can reproduce this on RHEL7, so clone this.

# rpm -qa virt-viewer spice*
virt-viewer-0.5.7-1.el7.x86_64
spice-gtk3-0.20-2.el7.x86_64
spice-server-0.12.4-1.el7.x86_64
spice-gtk-0.20-2.el7.x86_64
spice-glib-0.20-2.el7.x86_64
spice-vdagent-0.14.0-3.el7.x86_64


Description of problem:
Virt-viewer can not configure multi-displays optionally

Version-Release number of selected component (if applicable):
# rpm -qa virt-viewer spice*
spice-gtk-0.20-9.el6.x86_64
spice-glib-0.20-9.el6.x86_64
virt-viewer-0.5.2-18.el6.x86_64
spice-server-0.12.4-6.el6.x86_64
spice-vdagent-0.14.0-2.el6.x86_64
spice-gtk-python-0.20-9.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
Scenario 1:
1. Prepare a rhel guest.
2. Configure the guest with only 1 display, use virt-viewer to connect it.
#virt-viewer vm
3. View - > Displays - > Display 4(check on)
4. Can see display 4 come out, but display 2 and display 3 will come out too.

Scenario 2:
5. Configure the guest with 4 displays.
6. View - > Displays - > Display 2(check off)
7. After check off the display, the display 2 will disappear, but it will come out soon.

Actual results:
As step 4 and 7.

Expected results:
Can configure the displays optionally.
Step4, display 2 and display 3 should not come out.
Step7, display 2 should not come out again.

Additional info:

--- Additional comment from CongDong on 2013-10-22 04:19:02 EDT ---



--- Additional comment from CongDong on 2013-10-22 04:19:43 EDT ---

Comment 1 CongDong 2013-10-22 08:46:20 UTC
Can reproduce this with :
virt-viewer-0.5.7-2.el7.x86_64

Comment 3 CongDong 2013-11-21 08:37:46 UTC
With the latest pkgs can not reproduce this bug.
And can not reproduce this with the same pkgs in description.


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