Bug 1795328

Summary:	Crash in xf86CrtcRotate with Option "Rotate" in xorg.conf
Product:	Red Hat Enterprise Linux 8	Reporter:	Michel Dänzer <mdaenzer>
Component:	xorg-x11-server	Assignee:	Michel Dänzer <mdaenzer>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	tpelka
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.2
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:	xorg-x11-server-1.20.6-3.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 15:41:41 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:	1739559

Description Michel Dänzer 2020-01-27 17:15:39 UTC

Description of problem:

Xorg crashes on startup if rotation is configured in xorg.conf for any connected RandR outputs.


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

1.20.6-2.el8


How reproducible:

Always (with an affected configuration, which is rare).


Steps to Reproduce:
1. Configure rotation in xorg.conf Section "Monitor" for any connected RandR output.
2. Start Xorg.


Additional info:

This is a regression in xorg-x11-server-1.20.6-2.el8, caused by one of my fixes for bug 1738670. Upstream fix pending review at https://gitlab.freedesktop.org/xorg/xserver/merge_requests/384 .

Comment 1 Michel Dänzer 2020-01-27 17:37:29 UTC

Example xorg.conf snippet to reproduce below. The identifier needs to be adapted to match one of the RandR outputs which are connected at Xorg startup (grep the log file for " connected"). Option values "left" or "right" reproduce as well, but not "normal".

Section "Monitor"
    Identifier "DVI-D-3"
    Option "Rotate" "inverted"
EndSection

Comment 5 errata-xmlrpc 2020-04-28 15:41:41 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1633