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.

Bug 1022426

Summary:	[remote-viewer] New display opens in fullscreen
Product:	Red Hat Enterprise Linux 7	Reporter:	CongDong <codong>
Component:	virt-viewer	Assignee:	Jonathon Jongsma <jjongsma>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	cfergeau, codong, dblechte, jjongsma, marcandre.lureau, mzhan, rbalakri, tjamrisk, tzheng
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	virt-viewer-0.6.0-1.el7	Doc Type:	Bug Fix
Doc Text:	Connecting to a server with --fullscreen=auto-conf, leaving fullscreen and then opening another display results in the second display opening in fullscreen. After this change, the new display will open in window mode after leaving fullscreen, as expected.	Story Points:	---
Clone Of:	1009513	Environment:
Last Closed:	2015-03-05 13:38:19 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:	1009513, 1109400
Bug Blocks:	1009648

Comment 2 Jonathon Jongsma 2013-11-13 16:14:08 UTC

patch applied upstream.

Comment 4 Jonathon Jongsma 2014-07-07 22:00:48 UTC

will be fixed by rebase

Comment 6 CongDong 2014-07-22 01:38:41 UTC

I can reproduce with: virt-viewer-0.5.7-7.el7.x86_64

VERIFY:
Steps:
Prepare a client has two physical monitors.

1. # virsh start demo
# virsh dominfo demo
Id:             3
Name:           demo
UUID:           4cd561bf-ba7f-404c-9bfa-2651534c56dc
OS Type:        hvm
State:          running
CPU(s):         2
CPU time:       61.2s
Max memory:     1048576 KiB
Used memory:    1048576 KiB
Persistent:     yes
Autostart:      disable
Managed save:   no
Security model: selinux
Security DOI:   0
Security label: system_u:system_r:svirt_t:s0:c246,c937 (enforcing)

2. 
Add following content to ~/.config/virt-viewer/settings
[4cd561bf-ba7f-404c-9bfa-2651534c56dc]
monitor-mapping=1

3. # virt-viewer demo , make sure only 1 display is shown.

4. # virt-viewer demo -f
One display comes out fullscreen.

5. Click "Leave fullscreen" button on the top of virt-viewer
And open another display, "View" -> "Displays" -> "Display 2"

Result:
step5, display 2 comes out in window mode. 

As the result, VERIFIED

Comment 8 errata-xmlrpc 2015-03-05 13:38:19 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