RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1314829 - Test case failure: multihead test on NVS 315
Summary: Test case failure: multihead test on NVS 315
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-nouveau
Version: 6.8
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Ben Skeggs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-04 16:07 UTC by Tomas Hudziec
Modified: 2017-12-06 10:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:34:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Hudziec 2016-03-04 16:07:24 UTC
Filed from caserun 273678

Version-Release number of selected component (if applicable):
RHEL-6.8-20160215.n.0
xorg-x11-server-utils-7.7-14.el6.x86_64

Steps to Reproduce: 
1. Have Dell 1703fpt connected on DP-1 and some other monitor(iiyama ProLite T2250MTS in my case) on DP-2.
2. Disconnect Dell monitor.
3. Reconnect Dell monitor.

Actual results:
System don't recognize Dell monitor, screen is black.

Expected results:
System recognize Dell monitor and start display on it.

Additional info:
after running xrandr or gnome-display-properties monitor is recognized
graphics card: NVIDIA Corporation GF119 [NVS 315] [10de:107c]
if monitors are connected vice versa(Dell on DP-2 and iiyama on DP-1), bug doesn't occur

Comment 2 Tomas Hudziec 2016-03-09 17:24:30 UTC
xorg-x11-drv-nouveau-1.0.11-1.el6.x86_64

based on additional info in description, most likely not a bug

Comment 3 Tomas Pelka 2016-04-01 09:58:10 UTC
Still an issue with 
xorg-x11-drv-nouveau-1.0.12-1.el6.x86_64
xorg-x11-server-Xorg-1.17.4-8.el6.x86_64

Comment 5 Jan Kurik 2017-12-06 10:34:39 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/


Note You need to log in before you can comment on or make changes to this bug.