Panorama fails on startup

[Rosuav]

Your system information

• System information from steam (Steam -> Help -> System Information) in a gist: https://gist.github.com/Rosuav/09cb97da931958d4e3837162c9e272e1
• Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

I fire up the game. It goes to a black screen, then terminates.

Steps for reproducing this issue:

1. Spend six hours trying to diagnose and fix the issue.
2. Continue to experience problems.
3. Curse Valve for removing Scaleform already.

I've updated my Debian to the latest that I can get hold of, I've updated my NVIDIA drivers, I've uninstalled CS:GO and reinstalled it fresh, I've blown away my configs, I've done everything I can think of to try to fix this. Scaleform worked mostly-correctly (the occasional UI glitch), but Panorama has simply never worked for me.

If it helps, the crash in question is a segfault and appears to come from engine_client.so.

[orbus]

I have this same issue as well. Panorama has never been able to run on my system.

[kekstee]

Just stumbled across the solution: I had an Xbox 360 controller attached, with no controllers Panorama launches as expected. Launching it with a controller attached leads to the black screen and crash.

Console output of the failed launch: https://paste.pound-python.org/show/h0ISxJcGvdackqlNfNsb/

[kisak-valve]

Hello @Rosuav, can you check if adding -nojoy to the game's launch options makes a difference?

If it does, then this is #1757.

[Rosuav]

Already tried with -nojoy and, if you'll pardon the expression, no joy. I do own a 360 controller, but it isn't attached at the moment (and hasn't been since the most recent reboot).

[kisak-valve]

If you find any CrashIDs or minidumps (commonly found in /tmp/dumps) related to this issue, please put them in an archive and drag and drop the archive to the comment box.

[Rosuav]

Just made a fresh one, to be on the safe side. (Dumps tend to get smelly if you leave them around too long.)

assert_20180830221805_1.dmp.gz

[kisak-valve]

For reference, the attached minidump is a SIGSEGV in engine_client.so.

[Rosuav]

Correct. Which is as much as I was able to figure out from a gdb run, since I don't have debug symbols.

[PewieStiffin]

I have the same issue, i have to try and start the game 50 times and hope that it doesnt crash, very rarelly it works.
-edit: adding -nojoy in launch options seemed to fix the crash on startup, also works with -novid.

[orbus]

-nojoy worked for me! I want to know why, but not enough to read much more

[pmadzik]

I had same issue in my debian (testing/unstable). It helped:

cd /home/przema/.steam/root/ubuntu12_32/steam-runtime/pinned_libs_64

ln -s /home/przema/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/lib/x86_64-linux-gnu/libpng12.so.0.46.0 libpng12.so.0

[Rosuav]

YES!! Thank you @pmadzik, that worked for me too!

Now the question is: Why did that work? (Also, how did you know to try it?)

Hopefully this info will help Valve find a true solution.

[pmadzik]

I saw this message in my dump file:

Unable to load 'libpangoft2-1.0.so' (error info '/usr/lib/x86_64-linux-gnu/libpng16.so.16: version PNG12_0' not found (required by /home/przema/storage2/steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/libpangoft2-1.0.so)'), your game install may be corrupted or you may have a system conflict

The LD_LIBRARY_PATH variable content is also there and it indicate that directory with steam version of library libpng12 follows the system directory (which contains libpng12 as symbolic link to libpng16), but the "pinned" directory precedes system directory.

[kisak-valve]

The better question then is what's symlinking libpng12 to libpng16 ... they aren't ABI compatible.

[pmadzik]

Maybe it just debian idiosyncrasy.

[Rosuav]

FYI this is still a problem. After the latest update, CS:GO didn't fire up, and I needed to recreate the symlink.

[Rosuav]

FYI, this is still a problem - after the latest batch of updates, I had to reapply the workaround.

[muckee]

My friend just had this problem. He was on discord at the same time and solved it by closing discord and csgo, then opening csgo before discord. A cold reboot didn't fix the issue.

Not sure why that happened but the issue is persistent. Might be useful info for somebody.

[thomasfinstad]

@joshuaflood, after I deleted all my steam files due to steam overlay refusing to work and redownloading (fixed overlay). I Started getting random crashes, I use teamspeak and after reading your comment I started opening teamspeak after csgo, it haven't crashed since. I did however also clean dust out of my machine so it might be because of that aswell, but no more crashes.

[Rosuav]

FYI, this is still a problem, and the same workaround still applies.

[Rosuav]

Checking in to report that (a) this is still a problem, and (b) the symlink still works. Valve, please, can you just get Steam to create the symlink?