Bug 769078

Summary:	Dual monitor head 0 does not work on boot - even after prior session configuration set...
Product:	[Fedora] Fedora	Reporter:	Don Reese <don.e.reese>
Component:	gnome-desktop	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	don.e.reese, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-13 21:57:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Don Reese 2011-12-19 21:18:34 UTC

Description of problem:
Purchased HP P7-1126s with Radeon HD 6370D onboard video. Trying to use two Westinghouse 22" monitors (same model) on both DVI-D connections. At boot both heads (head 0 is left, head 1 is right) come on with same display. When Fedora 16 comes up head 0 is not engaged and will power off due to lack of a signal. If not using auto login the login screen will try to show on head 0 (which has no display) and head 1 is showing the vern background (wish I could get that changed - maybe when I get to the point that I can trust the system). Anyway using auto login (with the menu set to use head 1) will get you past the login problem, but head 0 remains inactive until you open the monitor system settings. At that point the second monitor wakes up and you can tell the system to keep the configuration. Well at least until you power off.

Next time you power on you have to go though the same thing again. I have not tried to just log out and see if head 0 remains active.

Version-Release number of selected component (if applicable): Fresh install of Fedora16 desktop (gnome - bad choice imho). But now can't get other desktops (including KDE) to run after installing them though yum.

How reproducible:
Every time I turn on the computer and boot Fedora 16.

Steps to Reproduce:
1. Boot Fedora 16
2. Configure head 0 so that it is working. Restart
3.

Actual results:
Head 0 configuration is not remembered between boots. Login does not turn on head 0 but displays the login screen there.

Expected results:
Should be able to use head 0 once set up for use under gnome. Should be able to see login screen.

Additional info:

Comment 1 Don Reese 2011-12-19 22:50:24 UTC

Westinghouse LCM-22w3 Monitors

Comment 2 Fedora End Of Life 2013-01-16 17:22:41 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 21:57:59 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.