I've added debug output of $ and that is what i got: I'm an independent developer, so time is money. This is unfortunately not the first time that I've been sent on a wild goose chase that turned out to be a downstream bug.
Failing that, I will request that the submitter attempt to reproduce the bug using our official binary package (to eliminate downstream packaging bugs such as the one that prompted this issue.) Failing that, I will assume the bug to be Arch-specific and will not devote any significant time to diagnosing or fixing it until/unless it can be shown to affect another platform. In the future, if a bug is reported in VirtualGL on Arch, the first thing I will do is attempt to diagnose it on another distro of similar vintage, such as the latest Fedora or Ubuntu.
It's completely non-intuitive and "bare-metal" and, in general, made me feel like I was stuck in the 1990's trying to install BSD on a 386. It works like no other distro I've ever encountered.As you guys discovered, it can work one day and break the next, due to no fault of the upstream developers such as me. The problems with Arch, from my point of view: I cannot support every single distro on the planet. But I'm just one person maintaining three rather complicated OSS projects. I finally got Arch up and running, so that's no longer the problem. Otherwise, there isn't much I can do at this point except wait and hope that the problem manifests in some other way that I can reproduce.
If you can make this fail in the same way using another distro (Ubuntu 10-15, SUSE 11, CentOS 5-7, Fedora 22, Mint 17.2 are all things I can readily test), then I'm happy to look into it further.
Basically impossible to support from a software manager's point of view. I've tried several times without luck to get Arch Linux up and running. Not really much I can do unless this is reproducible with another distro. I cannot get past the login screen, because I am not a gamer and do not have a Steam account, but it seems that the failure you're observing is occurring before that point. LD_LIBRARY_PATH wasn't properly picking up my dev build.) Installing the 2.5 packages onto the system cleared up the segfault, and Steam launches. Correction: the failure I was experiencing (segfault) was due to a mismatch between my dev version and the system-installed version (i.e.