Bug 92507 - Multimonitor: change of resolution switches previously disabled display (by Display's app) back on
Summary: Multimonitor: change of resolution switches previously disabled display (by D...
Status: RESOLVED MOVED
Alias: None
Product: Spice
Classification: Unclassified
Component: virt-viewer (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-17 14:29 UTC by Fabiano Fidêncio
Modified: 2018-06-05 14:18 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Fabiano Fidêncio 2015-10-17 14:29:13 UTC
Description of problem:
With multimonitor guest running (happens with both Windows and Linux guest), when a display is disconnected through Display's app (or equivalent) and resolution of any other active display is changed (e.g. by resizing a window or by switching to fullscreen), the previously disabled display is switched on again.

Version-Release number of selected component (if applicable):
Client: virt-viewer-2.0 (also happens with git master)
spice-gtk-0.29 (also happens with git master)

How reproducible:
Always

Steps to Reproduce:
1. Set up a multimonitor guest and run it
2. Connect to the VM using remote-viewer
3. In the Display settings of guest system activate all displays
4. Disable the previously activated displays so that their window stays black and a message "Waiting for display X..." is shown. Do not close this window.
5. Change the resolution of any active screen (either by resizing the window or by switching to fullscreen)
  
Actual results:
All previously disabled displays are switched on again.

Expected results:
The disabled displays stay disabled even after change of resolution of any other active display.

Additional info:
Originally reported by Milan Barta: https://bugzilla.redhat.com/show_bug.cgi?id=868970
Comment 1 GitLab Migration User 2018-06-05 14:18:12 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/spice/spice-gtk/issues/44.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.