Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#48105 - [nvidia] Civilization 5 (steam) crash with last version of nvidia drivers
Attached to Project:
Arch Linux
Opened by Fabiano (fbn1979) - Tuesday, 09 February 2016, 08:58 GMT
Last edited by Felix Yan (felixonmars) - Thursday, 11 February 2016, 02:37 GMT
Opened by Fabiano (fbn1979) - Tuesday, 09 February 2016, 08:58 GMT
Last edited by Felix Yan (felixonmars) - Thursday, 11 February 2016, 02:37 GMT
|
DetailsDescription:
Civilization 5 (steam) crash with last version of nvidia drivers > dmesg Civ5XP[1153]: segfault at edc ip 00000000f6d236f4 sp 00000000f242586c error 4 in libGLdispatch.so.0[f6ce4000+7e000] Other people having problems https://forums.geforce.com/default/topic/910505/-linux-civilization-v-crashes-with-v-361-drivers/?offset=1 nvidia 361.18-3 The game was starting before upgrade Additional info: nvidia 361.18-3 Steps to reproduce: Start Civ 5 from steam |
This task depends upon
Closed by Felix Yan (felixonmars)
Thursday, 11 February 2016, 02:37 GMT
Reason for closing: Upstream
Additional comments about closing: Fixed in 361.28.
Thursday, 11 February 2016, 02:37 GMT
Reason for closing: Upstream
Additional comments about closing: Fixed in 361.28.
Comment by Felix Yan (felixonmars) -
Wednesday, 10 February 2016, 15:35 GMT
Upstream suggests that it's an app bug in the Aspyr port and successfully worked around in 361.28. Please try again with the new drivers, thanks.
Comment by Alexander Schnaidt (Namarrgon) -
Wednesday, 10 February 2016, 18:42 GMT
I can confirm that 361.28-1 does fix this particular crash for me.