Source games stopped working - nvidia update(361.28-1) suspected

carkasjak · 2016-02-11 15:28:13

spider-net wrote:

Fixed for me. https://bugs.archlinux.org/task/48123 is now closed.

The conflict with mesa might be solved, but the issue with certain games not working is not. This was after the latest update and reboot as well: https://i.imgur.com/TMxYtmd.png

AnAkkk · 2016-02-11 16:17:07

https://github.com/ValveSoftware/Dota-2 … -182935495

zebulon · 2016-02-11 16:32:50

AnAkkk wrote:

https://github.com/ValveSoftware/Dota-2 … -182935495

Yes, using

__GLVND_DISALLOW_PATCHING=1 steam

fixes Bioshock Infinite.

carkasjak · 2016-02-11 16:44:57

zebulon wrote:

AnAkkk wrote:
https://github.com/ValveSoftware/Dota-2 … -182935495
Yes, using
__GLVND_DISALLOW_PATCHING=1 steam
fixes Bioshock Infinite.

Yup, this is a fine workaround until the issue is fixed.

skunkos · 2016-02-11 17:50:06

zebulon wrote:

AnAkkk wrote:
https://github.com/ValveSoftware/Dota-2 … -182935495
Yes, using
__GLVND_DISALLOW_PATCHING=1 steam
fixes Bioshock Infinite.

Fixes CS: GO too. But I have impression that now the game takes longer to actually start.

skiwi · 2016-02-12 12:05:20

skunkos wrote:

zebulon wrote:
AnAkkk wrote:
https://github.com/ValveSoftware/Dota-2 … -182935495
Yes, using
__GLVND_DISALLOW_PATCHING=1 steam
fixes Bioshock Infinite.
Fixes CS: GO too. But I have impression that now the game takes longer to actually start.

Fixes DOTA2 as well, but the GNOME panel remains visible in fullscreen. This only happens in-game, not in Steam itself.

chrissi5120 · 2016-02-12 12:41:00

skiwi wrote:

skunkos wrote:
zebulon wrote:
Yes, using
__GLVND_DISALLOW_PATCHING=1 steam
fixes Bioshock Infinite.
Fixes CS: GO too. But I have impression that now the game takes longer to actually start.
Fixes DOTA2 as well, but the GNOME panel remains visible in fullscreen. This only happens in-game, not in Steam itself.

Fixes DOTA2 for me too, fullscreen works normal, no gnome panel visible !

dunc · 2016-02-12 14:40:07

skunkos wrote:

zebulon wrote:
AnAkkk wrote:
https://github.com/ValveSoftware/Dota-2 … -182935495
Yes, using
__GLVND_DISALLOW_PATCHING=1 steam
fixes Bioshock Infinite.
Fixes CS: GO too. But I have impression that now the game takes longer to actually start.

Same with Borderlands 2.

So it seems like both Source and Unreal Engine are affected. The only other game I've tried since updating is the Talos Principle, which I bought last night. It started without any issues.

evil.genius · 2016-02-13 17:51:26

I realise there's a workaround for this, but has anyone filed a bug report?

WorMzy · 2016-02-13 18:06:14

Please read the thread.. on this page alone there's a link to the Arch Linux bug report, and several links to a report on Valve's github issue tracker for DOTA2 where it's explicitly said that nvidia are aware of the issue and it will be fixed in a future update.

evil.genius · 2016-02-13 19:58:58

I have read the thread. The Arch bug report relates to Bumblebee and has been closed. The DOTA2 thread relates to DOTA2. I am unaffected by either of these. If Nvidia have a public bug tracker, please point me to it. Since this seems to be only an Arch issue at this point, I thought perhaps there was a report which I could follow.

YAOMTC · 2016-02-13 19:59:30

Another set of updates are available. The comment: "Install tls libs to proper location". I don't think this was meant to solve the existing problems with games, and it does not.

lib32-nvidia-utils 361.28-4
lib32-nvidia-libgl 361.28-4
nvidia-utils 361.28-5
nvidia-libgl 361.28-5

Last edited by YAOMTC (2016-02-13 20:00:08)

WorMzy · 2016-02-13 20:33:53

evil.genius wrote:

I have read the thread. The Arch bug report relates to Bumblebee and has been closed.

My bad, I thought it was the same report linked in post #10.

The DOTA2 thread relates to DOTA2.

No, the DOTA2 thread relates to the bug that affects multiple games. I don't know if nvidia have a public bug tracker (there is one that claims to be, but there's nothing from post-2011), but you should keep your eye on the nvidia devtalk thread.

alien2003 · 2016-02-15 21:47:36

The same problem with L4D2. Still not fixed

Vash63 · 2016-02-15 21:48:16

Has anyone figured out if the game performance is worse with __GLVND_DISALLOW_PATCHING=1 ? I've put my updates on pause waiting for a new Nvidia driver as it is.

dunc · 2016-02-16 18:12:08

Vash63 wrote:

Has anyone figured out if the game performance is worse with __GLVND_DISALLOW_PATCHING=1 ? I've put my updates on pause waiting for a new Nvidia driver as it is.

No hard numbers, but it certainly doesn't seem noticably worse apart from the (maybe, slightly) slower initial startup. The hassle of setting the environment variable for every game that needs it is probably as good a reason as any to hold off updating, but I don't think performance is.

saivert · 2016-02-19 01:22:43

I don't know about you guys but I don't have to use any workarounds for CS: GO using these drivers:
https://github.com/fafryd1125/arch-nvidia-utils
https://github.com/fafryd1125/arch-lib32-nvidia-utils

nstgc · 2016-02-19 14:43:43

dunc wrote:

Same with Borderlands 2.
So it seems like both Source and Unreal Engine are affected. The only other game I've tried since updating is the Talos Principle, which I bought last night. It started without any issues.

I think BL2 is unrelated. I tried disabling the optimization, but that didn't help.

[edit2] It does help with Saints Row IV though.

Last edited by nstgc (2016-02-19 14:44:04)

kittenclaws · 2016-02-24 19:38:54

blackout23 wrote:

The problem is not fixed in the newest package release.
What is strange is that you can work around this for some reason by going to the startup script of the game in the games install directory and for example edit hl2.sh for Counter Strike: Source and change __GL_THREADED_OPTIMIZATION=1 to 0. And now it will start.

Workaround works for me! Thank you. Was driving myself a little crazy trying to find a solution to this.

HL3 Confirmed.

Silex89 · 2016-02-24 23:39:56

I am in a system (laptop) that has a 4th generation i7 (Intel+NVidia), with a NVidia GTX870M. I was able to play all my games very smoothly prior to the update. I used to run steam using primusrun, but now all I have is this goofy window telling me that I have a missing library.

Captura%20de%20pantalla%20de%202016-02-24%2020-23-28.png

If I try to run steam without bumblebee is fine (but the performance is awful in the integrated card as you would expect). Then I tried the workaround from former posts and I had the same output as the rest of the forumers about the missing OpenGL extensions. The environment variable does not work for me unfortunately (it fixes the GL extensions problem but in turn gives me a core dumped for the ld.so library. Using optirun as a bridge for primus does not solve the issue either).

Have you guys any other workaround that I can try?

Thank you in advance.

silentz0r · 2016-02-26 01:54:51

Silex89 wrote:

I am in a system (laptop) that has a 4th generation i7 (Intel+NVidia), with a NVidia GTX870M. I was able to play all my games very smoothly prior to the update. I used to run steam using primusrun, but now all I have is this goofy window telling me that I have a missing library.
https://dl.dropboxusercontent.com/u/315 … -23-28.png
If I try to run steam without bumblebee is fine (but the performance is awful in the integrated card as you would expect). Then I tried the workaround from former posts and I had the same output as the rest of the forumers about the missing OpenGL extensions. The environment variable does not work for me unfortunately (it fixes the GL extensions problem but in turn gives me a core dumped for the ld.so library. Using optirun as a bridge for primus does not solve the issue either).
Have you guys any other workaround that I can try?
Thank you in advance.

If you read the whole thread you can find solutions to the recent problem, and googling should help with the fatal error.
Anyway going a bit off-topic, I'm on similar setup, and have a little steam.sh script to load my steam:

#!/bin/bash
export STEAM_FRAME_FORCE_CLOSE=1
export __GLVND_DISALLOW_PATCHING=1
LD_PRELOAD='/usr/$LIB/libstdc++.so.6 /usr/$LIB/libgcc_s.so.1 /usr/$LIB/libxcb.so.1' steam

First line closes steam to system tray (instead of exiting), just like on windows.
Second line is the current workaround to Source games not working.
Third line is a workaround to use Arch's libraries instead of the libs that steam ships with, fixing the error you mentioned.

This is just a convenience script that I tend to update whenever something new is happening.

I also just launch steam via the above script, and then add the following launch command to any game I want to use the Nvidia GPU with max FPS:

vblank_mode=0 primusrun %command%

Finally I didn't come up with any of the solutions, so searching should've provided you with information/workarounds.

Last edited by silentz0r (2016-02-26 01:58:49)

Silex89 · 2016-02-29 16:16:02

I managed to launch Source(2)-powered games with the following environment variables:

LD_PRELOAD=/usr/lib/nvidia/libGL.so __GLVND_DISALLOW_PATCHING=1 optirun %command%

The problem is that sometimes the NVidia's libgl produces a minidump, the game gets stuck for some 10 seconds and crashes. This happens randomly. I will send you the terminal output ASAP.

Gibzon · 2016-04-11 22:25:18

silentz0r wrote:

#!/bin/bash
export STEAM_FRAME_FORCE_CLOSE=1
export __GLVND_DISALLOW_PATCHING=1
LD_PRELOAD='/usr/$LIB/libstdc++.so.6 /usr/$LIB/libgcc_s.so.1 /usr/$LIB/libxcb.so.1' steam
First line closes steam to system tray (instead of exiting), just like on windows.
Second line is the current workaround to Source games not working.
Third line is a workaround to use Arch's libraries instead of the libs that steam ships with, fixing the error you mentioned.

confirm this works well, i added the export lines on /usr/bin/steam script so it loads with steam.

Arch Linux

#26 2016-02-11 15:28:13

Re: Source games stopped working - nvidia update(361.28-1) suspected

#27 2016-02-11 16:17:07

Re: Source games stopped working - nvidia update(361.28-1) suspected

#28 2016-02-11 16:32:50

Re: Source games stopped working - nvidia update(361.28-1) suspected

#29 2016-02-11 16:44:57

Re: Source games stopped working - nvidia update(361.28-1) suspected

#30 2016-02-11 17:50:06

Re: Source games stopped working - nvidia update(361.28-1) suspected

#31 2016-02-12 12:05:20

Re: Source games stopped working - nvidia update(361.28-1) suspected

#32 2016-02-12 12:41:00

Re: Source games stopped working - nvidia update(361.28-1) suspected

#33 2016-02-12 14:40:07

Re: Source games stopped working - nvidia update(361.28-1) suspected

#34 2016-02-13 17:51:26

Re: Source games stopped working - nvidia update(361.28-1) suspected

#35 2016-02-13 18:06:14

Re: Source games stopped working - nvidia update(361.28-1) suspected

#36 2016-02-13 19:58:58

Re: Source games stopped working - nvidia update(361.28-1) suspected

#37 2016-02-13 19:59:30

Re: Source games stopped working - nvidia update(361.28-1) suspected

#38 2016-02-13 20:33:53

Re: Source games stopped working - nvidia update(361.28-1) suspected

#39 2016-02-15 21:47:36

Re: Source games stopped working - nvidia update(361.28-1) suspected

#40 2016-02-15 21:48:16

Re: Source games stopped working - nvidia update(361.28-1) suspected

#41 2016-02-16 18:12:08

Re: Source games stopped working - nvidia update(361.28-1) suspected

#42 2016-02-19 01:22:43

Re: Source games stopped working - nvidia update(361.28-1) suspected

#43 2016-02-19 14:43:43

Re: Source games stopped working - nvidia update(361.28-1) suspected

#44 2016-02-24 19:38:54

Re: Source games stopped working - nvidia update(361.28-1) suspected

#45 2016-02-24 23:39:56

Re: Source games stopped working - nvidia update(361.28-1) suspected

#46 2016-02-26 01:54:51

Re: Source games stopped working - nvidia update(361.28-1) suspected

#47 2016-02-29 16:16:02

Re: Source games stopped working - nvidia update(361.28-1) suspected

#48 2016-04-11 22:25:18

Re: Source games stopped working - nvidia update(361.28-1) suspected

Board footer