| Summary: | glXQueryDrawable returns 0 for all attributes except GLX_FBCONFIG_ID | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Andrey Tsyvarev <tsyvarev> |
| Component: | GLX | Assignee: | mesa-dev |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 7.5 | ||
| Hardware: | Other | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
reproduce bug for GLXWindow
glxinfo output glxinfo output without additional environment variables |
||
One quick thing to check: Do you have GLX 1.3 or later? glXQueryDrawable() is a 1.3 function. Run 'glxinfo' and check the "GLX version" line. GLX version, shown by glxinfo, is 1.4. X server is Xvfb, native for Ubuntu 8.10. Normally, it corresponds with Mesa 6.2(GLX version 1.2), but when runnning with LD_LIBRARY_PATH pointed to Mesa 7.5, GLX version for server becomes 1.4. May be, the problem in that? But the most of others GLX 1.3 functions works well, including functions which works with GLXFBConfig. Even this function, glXQueryDrawable, works correctly for GLX_FBCONFIG_ID attribute. Ian and I discussed this last week. We were not reporting GLX 1.4 until very recently (the patch just came in a few days ago) so I'm a bit skeptical that you're actually getting GLX 1.4 on the server and not just the client, unless you're using binary drivers. Yes, some of the functions work correctly, including EXT_texture_from_pixmap functions, but I'm told that that is a "feature" of our glXGetProcAddress, which always returns a somewhat valid pointer, even for functions that probably shouldn't be there. Could you attach your glxinfo? Created attachment 30141 [details]
glxinfo output
GLX 1.4 on the server is only when LD_LIBRARY_PATH pointed to Mesa 7.5 library, compiled with --with-driver=xlib(only software implementation). As I understand, this variant of GLX library is actually fully implemented on the client side, so it doesn't depend on X server at all, and may returns any server side parameters.
Really, GLX version of server is 1.2(as I noted in the previouse post).
I understand, that for GLX 1.2 using of GLX 1.3 commands leads, strictly speaking, to an unspecified behaviour. But:
-if this variant of GLX implementation is really fully client side, why does it depend on server's GLX version?
-if it depends on server's GLX, why it returns wrong GLX version for the server? Moreover, how can library user test, whether he is allowed to use GLX 1.3 commands?
Created attachment 30142 [details]
glxinfo output without additional environment variables
"Real" version of the GLX on the server.
OK, there's a few bugs in the fake GLX code here. I've committed fixes to the Mesa 7.6 branch. For the real GLX case (the second glxinfo) you've only got GLX 1.2 (the lesser of the client and server versions) to glXQueryDrawable() isn't available. Can you test Mesa 7.6 from git? Fixed with commit c3eef6021a06d728aa4c8b882264f554f2d4b801 and 0526100a5cbd928fa28d38abdafd6beb024b0828. No follow-up since so closing now. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 30077 [details] reproduce bug for GLXWindow According to the description of glXQueryDrawable(), it should return attribute value for GLXDrawable, passed it as parameter. But for all attributes except GLX_FBCONFIG_ID it returns 0. E.g., it returns 0 for GLX_WIDTH and GLX_HEIGHT attributes for all drawables type, while drawables have non-zero sizes. Also the function always returns 0 for GLX_LARGEST_PBUFFER and GLX_PRESERVED_CONTENTS attributes of GLXPbuffer.