Bug 1371944

Summary: [NVS 510] wrong mirroring with third monitor turned off
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Hudziec <thudziec>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED NOTABUG QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-02 11:32:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
wrong mirroring with changed resolution none

Description Tomas Hudziec 2016-08-31 13:40:55 UTC
Created attachment 1196368 [details]
wrong mirroring with changed resolution

Description of problem:
There is wrong mirroring of two monitors, when the third is turned off. It does not mirror monitors, but sets them as primary & secondary and places them exactly on each other.

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-1.0.11-4.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.obtain at least 3 monitors and connect them to NVS 510
2.turn one of monitors off, but do not disconnect it
3.mirror other two monitors

Actual results:
Displays have written next to them "Primary", "Secondary" and "Off". It is possible to arrange displays, they are exactly overlapping each other. It is also possible to change their resolution, which affects mirroring [image in attachment]. 

Expected results:
Every display should have written "Mirrored" next to it. It should not be possible to arrange displays or change its resolution in mirror mode.

Additional info:
graphics card NVIDIA Corporation GK107 [NVS 510] [10de:0ffd]

Comment 2 Tomas Hudziec 2016-09-02 11:32:49 UTC
The bug occurred with kernel version 3.10.0-498.el7.x86_64. Seems to be fixed in kernel-3.10.0-500.el7.x86_64, as it does not occur any more.