Bug 1310785 - xrandr gets killed after disabling second display and second invocation
Summary: xrandr gets killed after disabling second display and second invocation
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
medium
Target Milestone: rc
: ---
Assignee: Ben Skeggs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-22 16:21 UTC by Tomas Hudziec
Modified: 2017-12-06 11:21 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 11:21:52 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Tomas Hudziec 2016-02-22 16:21:34 UTC
Description of problem:
xrandr gets killed after disabling second display and second invocation

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

How reproducible:
75%

Steps to Reproduce:
1. $ xrandr --output DP-2 --off
2. $ xrandr

Actual results:
after step 2., xrandr gets killed by SIGSEGV(11) and display DP-2 is turned on

Expected results:
after step 2., xrandr outputs its common output on stdout

Additional info:
graphics card: NVIDIA Corporation G98 [Quadro NVS 295]

Comment 2 Tomas Hudziec 2016-03-09 17:26:25 UTC
Changed component to nouveau, since it's not reproducible on other graphics:
xorg-x11-drv-nouveau-1.0.11-1.el6.x86_64

Comment 4 Jan Kurik 2017-12-06 11:21:52 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.