Bug 1336014

Summary: indirect rendering has been disabled by default in 1.17
Product: Red Hat Enterprise Linux 6 Reporter: Joe Wright <jwright>
Component: xorg-x11-serverAssignee: Adam Jackson <ajax>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.8CC: adam.winberg, alanm, ayadav, dkochuka, extern.frank.sudthoff, J.H.Hodrien, jkoten, knweiss, mjtrangoni, mkolaja, mmezynsk, pasteur, pgozart, rik.theys, ryan.kraus1, sfroemer, thomas.eriksson, tpelka
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1339111 (view as bug list) Environment:
Last Closed: 2017-03-21 11:16:36 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: 1339111    

Description Joe Wright 2016-05-13 20:23:09 UTC
Description of problem:
- indirect rendering is now set to default in Xorg 1.17

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

How reproducible:
- use application that requires indirect rendering

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
- this seem to be a behavioral change in 1.17. setting regression flag

Comment 7 Ryan Kraus 2016-05-16 12:19:07 UTC
This ticket is about indirect rending being disabled by default on Xorg 1.17. It can be enabled, in 1.17, by starting Xorg with the +iglx flag. An easy way to reproduce the issue is to run "glxinfo -i".

Comment 11 Rik Theys 2016-05-23 11:32:48 UTC
Hi,

How can the +iglx option be added to the X server arguments when using gdm? I've tried various settings for /etc/gdm/custom.conf that should do this but none seem to work. It seems setting the X server command in custom.conf is no longer possible.

Are there any plans to revert the default settings to the 1.16 version?

Regards,

Rik

Comment 12 Adam Jackson 2016-05-23 15:12:21 UTC
(In reply to Rik Theys from comment #11)
> Hi,
> 
> How can the +iglx option be added to the X server arguments when using gdm?
> I've tried various settings for /etc/gdm/custom.conf that should do this but
> none seem to work. It seems setting the X server command in custom.conf is
> no longer possible.

Indeed, you can't, gdm does not have that ability. The best you can do in the interim is replace the Xorg binary with a shell script that execs the real thing with +iglx prepended to the comand line.

> Are there any plans to revert the default settings to the 1.16 version?

Yes.

Comment 15 Karsten Weiss 2016-05-30 14:51:20 UTC
May I suggest that this issue should be mentioned in the Technical Notes or the Release Notes as well? AFAICS both documents currently contain almost no information about the xorg-x11-server changes although there was a version jump from 1.15.0 to 1.17.4.

Comment 16 adam winberg 2016-06-07 13:59:43 UTC
(In reply to Adam Jackson from comment #12)
> 
> Indeed, you can't, gdm does not have that ability. The best you can do in
> the interim is replace the Xorg binary with a shell script that execs the
> real thing with +iglx prepended to the comand line.
> 
Do you have an example of how this could look? I've tried but can't make it work.

Comment 17 adam winberg 2016-06-07 15:04:56 UTC
(In reply to adam winberg from comment #16)
> Do you have an example of how this could look? I've tried but can't make it
> work.

No need, i managed to make it work:
https://mail.gnome.org/archives/gdm-list/2011-September/msg00006.html

Don't know what I managed to screw up before though.

Comment 21 errata-xmlrpc 2017-03-21 11:16:36 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://rhn.redhat.com/errata/RHBA-2017-0729.html