Red Hat Bugzilla – Bug 1290777
No way of enabling Indirect GLX with GDM
Last modified: 2016-11-03 22:50:14 EDT
Description of problem:
Remote OpenGL not working with indirect GLX, and no obvious way of telling GDM to enable it.
Version-Release number of selected component (if applicable):
Always using the nvidia proprietary drivers, or most probably any other hardware accelerated drivers that don't use Mesa.
Steps to Reproduce:
1. Setup machine with nvidia drivers
2. ssh -Y remotehost
name of display: remotehost:33.0
libGL error: failed to load driver: swrast
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 153 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 27
Current serial number in output stream: 30
Normal glxinfo output.
Passing an argument +iglx to Xorg enables indirect GLX, and remote OpenGL then works correctly.
Tested with the nouveau driver this works, but that doesn't allow for running CUDA applications. I assume the Mesa driver underpinning nouveau is doing internal trickery to present as direct GLX even on remote connections that the nVidia driver doesn't, or isn't able, to do.
Related bug is that GDM doesn't allow arbitrary Xorg args to be passed: https://bugzilla.gnome.org/show_bug.cgi?id=586777
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.