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 1242605

Summary:	connecting to VM changes its resolution
Product:	Red Hat Enterprise Linux 6	Reporter:	Pavel Grunt <pgrunt>
Component:	spice-gtk	Assignee:	Default Assignee for SPICE Bugs <rh-spice-bugs>
Status:	CLOSED ERRATA	QA Contact:	SPICE QE bug list <spice-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.7	CC:	cfergeau, dblechte, djasa, fidencio, gklein, lsurette, rbalakri, rh-spice-bugs, spice-qe-bugs, srevivo, tpelka, ykaul
Target Milestone:	rc
Target Release:	6.8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spice-gtk-0.26-5.el6	Doc Type:	Bug Fix
Doc Text:	Cause: When the client doesn't set display dimensions and the "resize-guest" property is disabled, spice-gtk sends a wrong monitor config message (where all the monitors have width and heigh equals to 0) when the agent connects. Consequence: This wrong message confuses the guest, causing a resolution change. Fix: Don't send monitor config for if any of the monitors have its dimensions set. Result: Resolution doesn't chane when connecting to the guest.	Story Points:	---
Clone Of:	1242600	Environment:
Last Closed:	2016-05-10 21:15:45 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:	1242600
Bug Blocks:	1242602

Description Pavel Grunt 2015-07-13 17:33:16 UTC

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

Description of problem:
Connecting to the Fedora22 / rhel7.2 guest using remote-viewer changes the desktop resolution

Version-Release number of selected component (if applicable):
mingw-virt-viewer-2.0-2
guest Fedora22 / rhel7.2

How reproducible:
100%

Steps to Reproduce:
1. connect to a guest using remote-viewer
2. change resolution of the guest using "display settings"
3. disconnect
4. connect again
5. check resolution

Actual results:
resolution has changed (in my case from 800x600 to 1920x976)

Expected results:
resolution doesn't change

--- Additional comment from Pavel Grunt on 2015-07-13 13:19:30 EDT ---

Fixed in spice-gtk by commits
 28312b8d1e287a320851e8828825f2ca138d8b0b
 4b5e6ec2114e1250c81027ebeac9cfe8d059153f

Comment 2 Pavel Grunt 2015-07-14 07:07:00 UTC

Version-Release number of selected component (if applicable):
spice-gtk-0.26-4.el6.x86_64
virt-viewer-2.0-7.el6.x86_64
guest Fedora22 / rhel7.2

Fixed in spice-gtk by commits
 28312b8d1e287a320851e8828825f2ca138d8b0b
 4b5e6ec2114e1250c81027ebeac9cfe8d059153f

Comment 7 errata-xmlrpc 2016-05-10 21:15:45 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-2016-0832.html