You miss the point. This isn't about glxinfo, this is about *ALL* glx applications. glxinfo is just an example.
You said, "glxinfo creates a context that allows direct rendering" ... but direct rendering is not available because the client is remote from the server. In older versions of mesa (6.5 for sure, not sure through when), it would detect when remote and use indirect. This behavior seems to have reverted.
Now, when remote, it tries to use drisw, but it results in an empty set of visuals and fbconfigs as described by the codepath in my initial report.
You miss the point. This isn't about glxinfo, this is about *ALL* glx applications. glxinfo is just an example.
You said, "glxinfo creates a context that allows direct rendering" ... but direct rendering is not available because the client is remote from the server. In older versions of mesa (6.5 for sure, not sure through when), it would detect when remote and use indirect. This behavior seems to have reverted.
Now, when remote, it tries to use drisw, but it results in an empty set of visuals and fbconfigs as described by the codepath in my initial report.