Here's a screenshot of lib0 engine running with a custom Mesa build (and now Arch Linux's stock Mesa 17.2.6) on Manjaro MATE 17.0.4:
It looks normal, but it's actually broken because when I try to switch focus from a terminal to lib0 engine window the whole desktop screen turns black.
Also, Arch Linux crashes the same binary that worked a few minutes before on Ubuntu 16.04 like this:
First it returns from glXGetProcAddress just fine:
Then it moves returned pointer with no issues too:
But watch this: if I step one assembly instruction further -- it crashes. For no reason.
It executed glXGetProcAddress several times before that point, what's the problem on this particular line? I don't know. No one knows.
This forces me to ban any other distro that can't execute code that works just fine on Ubuntu 16.04 and Mesa 17.0.7 until a person who understands the inner workings of graphics drivers will explain this random behavior. At no point I, as a software developer, should care about any of this given the same binary runs perfectly fine under another environment.
lib0 engine requirements are updated to exclude any other distro except Ubuntu 16.04 which so far at least works reliably.