Segfault with 367.27 in Aspyr port of Civ 5

My fresh installation of Civ 5 (with all DLCs) is crashing often. Sometimes it crashes when I try to open a saved game during gameplay, sometimes it crashes within minutes of gameplay, while at other times I can get in over an hour of play before it crashes.

This is the typical output I get after a crash from dmesg in bash:

[ 3532.632700] Civ5XP[3241]: segfault at 0 ip 0000000008cd8534 sp 00000000e177d030 error 4 in Civ5XP[8048000+22a7000]
[ 3532.632766] Civ5XP[3242]: segfault at 0 ip 0000000008cd8534 sp 000000007ccff030 error 4 in Civ5XP[8048000+22a7000]

This appears to be the same issue seen here back in January for the 361.18 driver. I was wondering whether that issue has been resolved.

Hoping for a quick fix, I followed the suggestion of ahuillet and downgraded to 358, but I experienced similar segfaults. Apparently this issues is being tracked under 200167137 , but it isn’t clear to me where I can follow. It would be great to know whether there has been an update to this issue.

I see that this issue has also been discussed in Reddit with a response from Aspyr. It appears that the problem is on their end, not NVIDIA’s. I will go ahead and submit my own ticket to them to see if a fix has been made.

Finally, in another forum topic there is a potential fix which involves installing the drivers with GLVND enabled. How does one go about checking whether this has been installed/enabled?

In case you’re curious, I have a desktop with Ubuntu Xenial 16.04 as the OS and a GeForce GTX 980 Ti for my GPU.

nvidia-bug-report.log.gz (235 KB)

This does not appear similar to the earlier 361.18 issue. The 361.18 issue was a crash at startup introduced by glvnd, whose reaction to some undefined behavior was less tolerant than that of the glvnd-less driver. We have since modified glvnd to be more tolerant, thereby working around the application bug, and closing our internal bug 200167137. (As far as we’re aware that bug hasn’t been fixed in the application.)

Refer to or our README for details on glvnd.

From the information you are showing, there is no evidence that your problem is a NVIDIA bug. I suggest you contact Aspyr to ask for assistance, and circle back to us if and when you believe a NVIDIA driver bug to be the cause of your issue.


Merci beaucoup for the response and info. I’ve gotten in touch with Aspyr and will proceed with them. If anything NVIDIA-related comes up I’ll let you know.