When you get to it, can you please tell me if the mesa_glthread variable makes any effect on AMD GPU? I lack the hardware to test it. It looks like something with the drivers is at play, yesterday I received a dual graphics laptop at work and I had a similar error, it wasn't GW2 specific and even trying out glxgears produced an error like yours. Are you perhaps running a laptop with optimus/primusrun? As a general note, prior to uploading these new builds I tested them on 3 different systems: Mint 18.1 (aka Ubuntu 16.04) with Nvidia GPU, Ubuntu 18.04 (with Mesa 18.0 / Intel HD) and Debian 9 (with Mesa 13 / Intel HD). Aside from slow performance on the Intel HD's, all 3 checked out correctly. I also have a dual-graphics laptop - Nvidia GPU + Intel HD one. I have only installed the open source nvidia 395 drivers (from the graphics-drivers ppa) and have set the Nvidia GPU as the default one in Nvidia settings. I also checked that it is the one in use. I am not sure about Optimus. On my previous laptop (still with Ubuntu 12.04) I tried setting it up with bumblebee but didn't succeed and haven't bothered with it on this laptop at all. Not sure whether Optimus hasn't been implemented in the open source drivers. Quick googling didn't tell me much. I tried the fix you suggested with the edditing of "/etc/security/limits.conf", setting it to a value 16 times larger than yours and I still get the same crash error and debug output. What domain did you use for the lines? I just put the * wildcard. The 28th June still works perfectly well. Did you install any specific libraries on the 3 different systems before isntalling your package? Maybe my wine-staging is missing something? And what Nvidia drivers did you use. Felix said on reddit that they are using 395 as well.