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 1244878 - Windows needs to send complete monitors_config message to client
Summary: Windows needs to send complete monitors_config message to client
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spice-gtk
Version: 7.2
Hardware: All
OS: Windows
unspecified
medium
Target Milestone: rc
: 7.2
Assignee: Default Assignee for SPICE Bugs
QA Contact: SPICE QE bug list
URL:
Whiteboard:
: 1265363 (view as bug list)
Depends On: 1202419
Blocks: 1210796 1244880 1248189 1248196 1265359 1265360 1265361 1265363
TreeView+ depends on / blocked
 
Reported: 2015-07-20 16:45 UTC by Sandy Stutsman
Modified: 2016-03-15 10:43 UTC (History)
16 users (show)

Fixed In Version: spice-gtk-0.26-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1202419
: 1244880 1248189 1265361 1265363 (view as bug list)
Environment:
Last Closed: 2015-11-19 07:38:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2211 0 normal SHIPPED_LIVE virt-viewer, spice-gtk, and libgovirt bug fix and enhancement update 2015-11-19 08:27:40 UTC

Description Sandy Stutsman 2015-07-20 16:45:48 UTC
+++ This bug was initially created as a clone of Bug #1202419 +++

Description of problem:
Currently, Windows does not provide correct position information for multi-monitor in the monitors_config message to the spice client.

Version-Release number of selected component (if applicable):
3.6


How reproducible:
Always

Steps to Reproduce:
1. Bring up a Windows VM with >1 monitor
2. Use the "Screen Resolution" applet to position the monitors
3. Notice that after clicking apply, the monitors are all positioned at the same X position

Actual results:
When using the Windows "Screen Resolution" to position monitors, the monitors are re-positioned at the same X location (0)

Expected results:
The monitor positions should remain at the position set by the user.

Additional info:
The solution required a new IOCTL to the Windows QXL driver that will allow VDAgent to pass updated position information to the driver which can then set it in the monitors_config message.

Comment 3 David Jaša 2015-08-14 12:22:01 UTC
qa_ack+ as per bug 1202419 comment 4.

Comment 4 Fabiano Fidêncio 2015-08-28 00:18:10 UTC
Btw, the upstream commit is:
8b0cd321d5a4d08ccba5845c5f2206e6f8032c1d

Comment 10 errata-xmlrpc 2015-11-19 07:38:11 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-2211.html

Comment 11 Pavel Grunt 2016-03-15 10:43:22 UTC
*** Bug 1265363 has been marked as a duplicate of this bug. ***


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