Comment 14 for bug 1599775
Revision history for this message
| Michael Thayer (michael-thayer) wrote | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I hope this upstream change set will do the trick:
https:/
Re comment 11, I looked at Mesa to see how they were distinguishing client and server GL and applied that to my code (see comments in change set).
To summarise the issue: the tricks that we were playing to prevent the X server from loading our GL libraries, which unlike Mesa are designed to be client only, were not working here, and the X server process was failing when our libraries tried to call a function (RTR3InitDll) in another library which gets loaded by clients but which the X server was not (not sure why). I refined the tricks by studying how Mesa handles detecting being loaded by the server (technically being loaded for use with GBM rather than with X11) and in addition got rid of the immediate dependency which was failing.
Was that at all helpful?