deadbeet

I have the same issue and had to downgrade for now. I'm guessing this is caused by the fact that nvidia is switching(?) to GLVND https://devtalk.nvidia.com/default/topic/915640/unix-graphics-announcements-and-news/multiple-glx-client-libraries-in-the-nvidia-linux-driver-installer-package/ Sadly I can't say...

Sounds like a good idea. I'll do that in a few hours if no one else does. However, I realized that I've experienced two different error messages. With nvidia 361.18...

@kelleyk: I've now tested with the non-glvnd install and I have no issues.

Update: Seems like NVIDIA has confirmed issues with the GLVND enabled drivers that will be fixed in a future driver update. @arbu: Could you also test with a non-glvnd install...

I'll say that I've been running this script pretty hardcore recently, while also using the desktop client and phone client and I haven't faced any issues (yet)

@MerlionRock I love that idea

I'm having this issue as well. Both with ungoogled-chromium and firefox. If I use the config files and connect with wg myself it works fine, however.

That's a tricky decision to make, to be honest. Would it be for power users to be able to make their own customization or would it be to make it...

1.2 is out now with a good amount of changes! Do you know if the changes may have resolved this issue?

I'm still experiencing this on Tomb Raider. renaming libcurl.so.4 worked though :)