Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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
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".
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
(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.
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.
(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.
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