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 908822

Summary: Mirrored displays with --full-screen=auto-conf option
Product: Red Hat Enterprise Linux 6 Reporter: Vaclav Ehrlich <vehrlich>
Component: virt-viewerAssignee: Daniel Berrangé <berrange>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: acathrow, cfergeau, dblechte, djasa, dyasny, gkong, hyao, lcui, marcandre.lureau, pvine, rwu, tpelka, tzheng, uril
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 947046 (view as bug list) Environment:
Last Closed: 2013-05-09 23:34:06 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:    
Bug Blocks: 947046    

Description Vaclav Ehrlich 2013-02-07 15:37:41 UTC
Description of problem:
When connecting with remote-viewer from client to guest with --full-screen=auto-conf option, guests displays are mirrored.
Client is with two physical monitors.

Version-Release number of selected component (if applicable):
virt-viewer-0.5.2-18.el6.x86_64
spice-client-0.8.2-15.el6.x86_64
spice-vdagent-0.12.0-4.el6.x86_64
spice-gtk-python-0.14-7.el6.x86_64
spice-gtk-0.14-7.el6.x86_64
spice-server-0.12.0-12.el6.x86_64
spice-protocol-0.12.2-1.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1.start guest 
/usr/libexec/qemu-kvm -vga qxl -m 1024 -spice port=3000,disable-ticketing --full-screen -device virtio-serial -chardev spicevmc,id=vdagent,debug=0,name=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0

2.connect with remote-viewer
remote-viewer spice://localhost?port=3000 --full-screen=auto-conf 

3.wait guest boots up and gdm shows up, login into gnome session
  
Actual results:
Guest's displays are mirrored.

Expected results:
Guest's displays are properly configured. Only one is main (with menu toolbar)

Additional info:
Guest, client: RHEL 6.4 x86_64

Comment 2 RHEL Program Management 2013-02-11 06:47:27 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 4 Marc-Andre Lureau 2013-05-09 23:34:06 UTC
this looks like a duplicate of bug 876444

*** This bug has been marked as a duplicate of bug 876444 ***