Bug 1042168 - Exiting full-screen will change the secondary Windows monitor to be the primary one.
Summary: Exiting full-screen will change the secondary Windows monitor to be the prima...
Keywords:
Status: CLOSED DUPLICATE of bug 1174129
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: mingw-virt-viewer
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks: 1009648
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:15 UTC by Bill Sanford
Modified: 2015-06-11 13:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-11 13:36:37 UTC
oVirt Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Bill Sanford 2013-12-12 21:15:47 UTC
Description of problem:
With displays 1 and 2 in full-screen, I change the primary monitor's resolution from it's max to 1024x768. Then I exit full-screen of the primary monitor and this will then change the secondary Windows monitor to be the primary Windows monitor within the Windows Screen Resolution. Since this is changing the secondary display to be the first, the taskbar gets moved over with the correct behavior.

Version-Release number of selected component (if applicable):
RHEV-M 3.3 (is26)
Windows 2008 Server - guest
Windows 2008 Server R2 - Client

How reproducible:
100%

Steps to Reproduce:
1. See above
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jonathon Jongsma 2013-12-12 21:24:12 UTC
This sounds like the same behavior as the situation decribed here? https://bugzilla.redhat.com/show_bug.cgi?id=1018180#c8

Comment 2 Sandy Stutsman 2015-06-11 13:36:37 UTC
I've tested with with the patches for https://bugzilla.redhat.com/show_bug.cgi?id=1174129
and confirmed that this is a dupllicate.

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


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