Bug 1295061

Summary: Primary monitor not detected correctly with DVI-I and DVI-D ports
Product: Red Hat Enterprise Linux 7 Reporter: Ashish Shah <ashishks>
Component: mutterAssignee: Florian Müllner <fmuellner>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: ashishks, ayadav, cww, fmuellner, jadahl, jkoten, mkolbas, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-13 15:54:37 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1420851    

Description Ashish Shah 2016-01-01 14:48:55 UTC 
Description of problem:

Dual head configuration with spanning desktop across two monitors does not detect primary monitor correctly in GDM/GNOME
DVI-I is detected as primary monitor during boot-up and upon login to KDE session.
GDM login screen and GNOME session detects monitor on DVI-D as primary.
GNOME is not detecting primary monitor correctly with DVI-I and DVI-D ports.
Looks like GDM follows the alphabetic order DVI-D as primary in RHEL 7.2 ?
But KDE does select the power-on monitor as primary.

Version-Release number of selected component (if applicable):

RHEL7.2
GNOME 3.14

How reproducible:

Always (with specific hardware)

Steps to Reproduce:
1. Boot up system in GUI mode with dual monitor.
2. On GDM screen login as user to KDE session.


Actual results:

Monitor on DVI-I is detected as primary during boot-up and in KDE session
GDM and GNOME detect DVI-D monitor as primary

Expected results:

GDM/GNOME should also detect monitor on DVI-I as primary

Additional info:

This was working well with RHEL7.1 and earlier, even with RHEL6.
Problem is specific to RHEL7.2
Problem is also specific to dual head setup with DVI-I and DVI-D ports
Configuring monitors.xml to use desired monitor as primary helps to workaround the issue.