This bug affects windows clients as well as linux clients. Any discussion relevant to both bugs should take place at the parent bug. +++ This bug was initially created as a clone of Bug #1018180 +++ Description of problem: when user resizes monitors in a way that current primary monitors gets smaller than some other monitor, the now-biggest screen becomes primary. This is quite confusing for the users and it should not happen. The issue occurs just with new clients, I didn't manage to reproduce with old (3.2) client/new vdagent combo. Version-Release number of selected component (if applicable): RHEL 6.5: spice-gtk-0.20-9.el6.x86_64 Windows 7 32b: mingw-virt-viewer-0.5.6-6.el6_64 How reproducible: with 3.3 vdagent: roughly 70-100 % of cases with 3.2 vdagent: occurs in one of multiple tries Steps to Reproduce: 1. connect to multiple monitor guest (windowed) 2. resize primary monitor (with taskbar) to be smaller than some other monitor (or vice versa - resize non-primary monitor to be larger than primary) 3. Actual results: the now-biggest monitor becomes primary Expected results: primary monitor is not changed at all Additional info: The only case when primary monitor is changed is when current primary monitor is disabled - guest should however handle this condition entirely itself
needinfo, discussion in dup bug.
pushing to 3.4 as no blocker flag proposed and we are at RC phase and the issue is under investigation
parent bug is in POST, moving here too
moving to Jonathon, who fixed the bug
We'll re-base in in the next release, moving to 3.5
hi Marc-Andre, Would you be able to explain a bit more about "Fix: Always use the current window location to align and configure displays". What are we recommending users to do to avoid the screen swap? Cheers, Julie
(In reply to Julie from comment #9) > hi Marc-Andre, > Would you be able to explain a bit more about "Fix: Always use the current > window location to align and configure displays". What are we recommending > users to do to avoid the screen swap? > > Cheers, > Julie I used Jonathon comments from bug 1018180, better ask him.
Sorry for the confusing wording. The user does not need to do anything. My comment simply means that virt-viewer itself will always use the current window locations to align displays, rather than using possibly-out-of-date cached location information. So it should "just work" now.
(In reply to Jonathon Jongsma from comment #11) > Sorry for the confusing wording. The user does not need to do anything. My > comment simply means that virt-viewer itself will always use the current > window locations to align displays, rather than using possibly-out-of-date > cached location information. So it should "just work" now. Thanks Jonathon.
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/RHSA-2015-0197.html