Bug 682024

Summary:	second screen not recovered from screen saver
Product:	Red Hat Enterprise Linux 6	Reporter:	Jeff Fearn 🐞 <jfearn>
Component:	xorg-x11-drv-nouveau	Assignee:	Ben Skeggs <bskeggs>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1	Keywords:	Triaged
Target Milestone:	rc
Target Release:	6.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 10:36:25 UTC	Type:	---
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:	842499

Description Jeff Fearn 🐞 2011-03-03 22:58:16 UTC

Description of problem:
I'm running the RHEL 6.1 nightly builds on a HP Z400 with an nvidia Quadro card and dual monitors. When unlocking the screen saver the primary monitor is not reactivated and the user is forced to disable the monitor in the gnome display panel, save it, then re-enable the monitor. Quite tricky if your menu bar is on the disabled monitor.

Version-Release number of selected component (if applicable):
kernel-2.6.32-118.el6

How reproducible:
Always

Steps to Reproduce:
1. Install nightly kernel
2. reboot
3. enable screen saver
4. wait
5. move mouse

Actual results:
Main monitor blank

Expected results:
Main monitor working

Additional info:

Comment 1 Ben Skeggs 2011-03-04 06:46:29 UTC

This is a regression from 6.0.  Although the card in question is not supported in 6.0, others that were will be effected by this issue.

A patch that was available in the 6.0 kernel was lost during the rebase of the DRM components due to a proper fix not being available upstream at the time.  We included a quick workaround for the problem instead.

Upstream is now fixed properly, but it is likely too invasive for 6.1 at this point but we should add the workaround back.  Jeff has tested a scratch build and confirmed it corrects the bug for him.

Comment 2 RHEL Program Management 2011-03-04 06:59:55 UTC

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Comment 3 RHEL Program Management 2011-04-04 02:15:58 UTC

Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 4 Ben Skeggs 2011-08-24 06:26:08 UTC

This should be fixed for sure with the current kernel builds available for 6.2, can you confirm Jeff?

Comment 5 RHEL Program Management 2011-10-07 16:17:02 UTC

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 6 Ben Skeggs 2012-07-11 07:33:49 UTC

Ping :)

Comment 7 Jeff Fearn 🐞 2013-02-28 22:41:02 UTC

This is working for me on 6.4.

Comment 8 Jan Kurik 2017-12-06 10:36:25 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/