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 1202419 - 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 8
Classification: Red Hat
Component: spice-qxl-xddm
Version: ---
Hardware: All
OS: Windows
low
medium
Target Milestone: rc
: ---
Assignee: David Blechter
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks: 1210796 1244878 1244880 1248189 1248196 1265359 1265360 1265361 1265363 1327266
TreeView+ depends on / blocked
 
Reported: 2015-03-16 15:02 UTC by Sandy Stutsman
Modified: 2019-10-10 13:54 UTC (History)
15 users (show)

Fixed In Version: qxl-win-unsigned-0.1-22 qxl-win-0.1-24
Doc Type: Bug Fix
Doc Text:
Previously, the API for managing a monitor's position was not implemented, causing virtual monitors to change position (coordinates). Now, the API for managing monitor position has been implemented, so monitors stay in the expected position.
Clone Of:
: 1210796 1244878 1327266 (view as bug list)
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Proposed patch for spice-gtk (1.28 KB, patch)
2015-07-23 15:37 UTC, Sandy Stutsman 		no flags Details | Diff
screencast (1.32 MB, application/ogg)
2015-08-14 12:19 UTC, David Jaša 		no flags Details
spice-gtk log (942.27 KB, text/plain)
2015-08-14 12:29 UTC, David Jaša 		no flags Details
full vdagent log from the client session (5.97 KB, text/plain)
2015-08-14 12:31 UTC, David Jaša 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1060 0 normal SHIPPED_LIVE spice-qxl-driver-win bug fix and enhancement update 2017-04-18 20:59:09 UTC

Description Sandy Stutsman 2015-03-16 15:02:51 UTC 
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 1 Sandy Stutsman 2015-07-23 15:37:11 UTC 
Created attachment 1055428 [details]
Proposed patch for spice-gtk
Comment 2 Sandy Stutsman 2015-07-23 15:38:52 UTC 
One fix to spice-gtk has not been pushed yet. see attached.

Fix for vdagent  is 
http://cgit.freedesktop.org/spice/win32/vd_agent/commit/?id=6023630562fd129433aef1eaddcf6fbee3f03e50

for win qxl:
http://cgit.freedesktop.org/spice/win32/qxl/commit/?id=ed37b635188893719c59d71c031feddd01408f36
Comment 3 Sandy Stutsman 2015-08-10 15:47:23 UTC 
WRT to reproducting I've noticed that the monitors don't always reposition at the same x coordinate but they are still not ordered correctly without this change.
Comment 4 David Jaša 2015-08-14 12:19:49 UTC 
Created attachment 1063001 [details]
screencast

I finally found a good reproducer:
1. in 4-monitor VM, enable all monitors
2. on < 4 monitor client, modify layout to something that computer wouldn't choose by itself
3. connect to the guest with -f (--full-screen=auto-conf on old clients)
4. look into vdagent log (C:\Windows\Temp\vdagent)

In the log, something like this is to be seen:
2076::INFO::2015-08-14 14:11:02,165::VDAgent::run::***Agent started in session 1***
...
2076::INFO::2015-08-14 14:11:31,743::VDAgent::handle_max_clipboard::Set max clipboard size: 104857600
2076::INFO::2015-08-14 14:11:31,758::VDAgent::handle_mon_config::0. 1920*1080*32 (0,0) 1
2076::INFO::2015-08-14 14:11:31,758::VDAgent::handle_mon_config::1. 3840*2160*32 (0,1080) 1
2076::INFO::2015-08-14 14:11:31,758::VDAgent::handle_mon_config::2. 1920*1080*32 (1920,0) 1
2076::INFO::2015-08-14 14:11:31,758::VDAgent::handle_mon_config::3. 0*0*0 (0,0) 1
2076::INFO::2015-08-14 14:11:31,758::VDAgent::handle_mon_config::3. detaching
// this was correct setting matching client layout

2076::INFO::2015-08-14 14:11:31,758::DesktopLayout::consistent_displays::#qxls 4 #others 0
2076::INFO::2015-08-14 14:11:31,774::DesktopLayout::set_displays::Set display mode 1920x1080
2076::INFO::2015-08-14 14:11:31,774::DesktopLayout::set_displays::Set display mode 3840x2160
2076::INFO::2015-08-14 14:11:31,805::DesktopLayout::set_displays::Set display mode 1920x1080
2076::INFO::2015-08-14 14:11:31,805::DesktopLayout::set_displays::Set display mode 0x0
2076::INFO::2015-08-14 14:11:31,821::DesktopLayout::consistent_displays::#qxls 4 #others 0
2076::INFO::2015-08-14 14:11:33,102::VDAgent::handle_mon_config::0. 1920*1080*32 (0,0) 1
2076::INFO::2015-08-14 14:11:33,118::VDAgent::handle_mon_config::1. 3840*2160*32 (0,0) 1
2076::INFO::2015-08-14 14:11:33,118::VDAgent::handle_mon_config::2. 1920*1080*32 (0,0) 1
// coordinates of all the monitrs are set to [0,0] leaving
// the layout to guest OS discretion
Comment 5 David Jaša 2015-08-14 12:29:51 UTC 
Created attachment 1063008 [details]
spice-gtk log
Comment 6 David Jaša 2015-08-14 12:31:32 UTC 
Created attachment 1063009 [details]
full vdagent log from the client session
Comment 20 David Blechter 2019-10-10 13:54:04 UTC 
moving from RHEVM product to RHEL 8
Note You need to log in before you can comment on or make changes to this bug.