[0.18.13] Game won't start on Linux Steam

[stavros]

I am trying to run the game on Ubuntu 19.10 with Steam, but it fails to launch. 0.16.something launches fine, stable and above fail with the following error:

Code: Select all

ERROR: ld.so: object '/home/stavros/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
   0.000 Initializing Steam API.
Setting breakpad minidump AppID = 427520
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561197990061127 [API loaded no]
/home/stavros/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio: symbol lookup error: /home/stavros/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio: undefined symbol: SteamInternal_ContextInit

What could be the problem? It completely fails to launch, it doesn't even create the ~/.factorio/ directory.

[Loewchen]

Try viewtopic.php?p=441683#p441683.

[stavros]

Thanks, that's the same problem but it's unsolved.

[stavros]

Has anyone else run into this? It's making it impossible for me to play the game right now.

[Zavian]

Well it looks like a steam error. Have you tried updating your steam install? (Also do you have a 64 bit version of steam installed? The error is talking about "wrong ELF class: ELFCLASS32", which makes me think that your steam install is 32 bit).

[posila]

What version of Steam Client do you have? (Help -> About Steam)
Only difference in 0.16 and 0.17 Steam integration is that we had to update Steam API libraries. Try to reinstall Steam Client.

According to this the failed gameoverlayrenderer.so preload happens before Steam launches the game process and is harmless error https://github.com/ValveSoftware/steam- ... t-12071567

[stavros]

I have the latest non-beta version (I can give you an exact version in a few hours). I did reinstall Steam, but the error persists.

The preload error is harmless indeed, the actual problem seems to be the last line, where it can't find the symbol.

[stavros]

Here's my version info(:

Code: Select all

  "runtime" : {
    "path" : "/home/stavros/.local/share/Steam/ubuntu12_32/steam-runtime",
    "version" : "0.20200318.2",
    "issues" : [
    ],

[posila]

Well, I don't know how to help you at the moment. I'll send a Linux dev your way, as a workaround you can download non-Steam build from factorio.com (you need Factorio account linked with your Steam account)

[stavros]

Ah, I'll try that, thank you.

[wheybags]

Hello, I am the aforementioned linux dev :p
There will be an extra debug command in the next release that we can use to help debug this, but for now could you please post the output of the following commands?

Code: Select all

uname -a
ldd /home/stavros/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio
objdump -T /home/stavros/.local/share/Steam/steamapps/common/Factorio/lib/libsteam_api.so
md5sum /home/stavros/.local/share/Steam/steamapps/common/Factorio/lib/libsteam_api.so

[stavros]

Sure, here you are:

https://www.pastery.net/dnypux/

[wheybags]

Thanks for posting the above, but I wasn't able to figure out what was happening even still
However, the new debug flag is now present in v0.18.22.

Could I ask you to:
- Exit steam
- Start a new terminal, and run steam in it (so we can see the command line output)
- Start another new terminal, and run the following in it:

Code: Select all

/home/stavros/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio --debug-linux-dump-proc-maps-on-steam-init

- Steam should pop up a confirmation dialogue about running the game with a command line parameter, click accept
- Then pastebin the console output from both terminals

After that, I would ask you to repeat the process, but run the following command to launch factorio instead:

Code: Select all

/home/stavros/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio --debug-linux-dump-proc-maps

For the curious, this will dump /proc/$PID/maps to the log file, on steam init and on game start respectively. The /proc/$PID/maps file is a special file that will list what binaries are allocated to what chunks of virtual memory in the process, which will hopefully show us where the game is _really_ getting libsteam_api.so from.

[stavros]

Thanks for posting the above, but I wasn't able to figure out what was happening even still
However, the new debug flag is now present in v0.18.22.

Here you go: https://www.pastery.net/bppbpa+tvrjwe/

[wheybags]

I don't see the original error in that log anywhere (undefined symbol: SteamInternal_ContextInit). Actually, I don't think I see any errors?
Where did you get that error log from the first time, steam command line output?

[stavros]

Yes, I redirected stdout to a file and that was in it.

[stavros]

Looks like the error wasn't in Steam's stdout because of the redirect. Here it is without:

https://www.pastery.net/gmhuta/

[wheybags]

Can you run the second command (/home/stavros/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio --debug-linux-dump-proc-maps) again, without the redirect, so I can see both stderr and stdout interleaved, instead of separated?

[stavros]

Sure: https://www.pastery.net/szzmtv/

[wheybags]

Bingo:

Code: Select all

7f07808c5000-7f07808d3000 r-xp 00000000 08:01 2917405                    /usr/lib/libsteam_api.so

Something has installed a bad (just old?) libsteam_api.so in your /usr/lib. That seems unusual, it would be nice to know how it got there.
Did you install it yourself, as a workaround for another game? (eg https://www.leadwerks.com/community/top ... dwerks-32/)
Anyway, removing it should fix the problem.

EDIT: attached a copy of the paste from the preceding post, because the original link will expire