[14.22] Linux: Steam: Freeze or crash on startup

[Xavienth]

I recently reinstalled Ubuntu so this might have something to do with that. A fresh install of Factorio doesn't even start. It just gets stuck at the Steam dialogue saying "preparing to launch..." After restarting my computer or steam it will freeze when cropping bitmaps (sometimes). I have to kill it in system monitor to get it to close. After a couple restarts it then freezes at loading graphics. Again, I have to kill it in system monitor for it to work. Going through the questions on the bug report guidelines I guess I have to answer what I expected, so I expected the progress bar to reach 100% and the main menu to show.

Restarting my computer doesn't work, entering steam offline mode doesn't work, entering any of the suggested commands (from the graphics bugs thread) into the steam start options doesn't work, verifying game cache doesn't work, deleting the game and ~/.factorio doesn't work, disconnecting all but one of my monitors doesn't work.

I have noticed that it doesn't create a config.ini file in ~/.factorio if that's of any significance.

Might be a duplicate of viewtopic.php?f=30&t=41143 so I'm sorry if it is. Better safe than sorry though, eh?

[Loewchen]

Code: Select all

   0.000 2017-04-16 03:17:52; Factorio 0.14.22 (build 25342, linux64, steam)
   0.111 Operating system: Linux (Ubuntu 16.04)
   0.111 Program arguments: "/home/josh/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio" 
   0.111 Read data path: /home/josh/.local/share/Steam/steamapps/common/Factorio/data
   0.111 Write data path: /home/josh/.factorio
   0.111 Binaries path: /home/josh/.local/share/Steam/steamapps/common/Factorio/bin
   0.140 System info: [CPU: AMD A10-6700 APU with Radeon(tm) HD Graphics   , 4 cores, RAM: 11960MB]
   0.153 Display options: [FullScreen: 0] [VSync: 0] [UIScale: 100%] [MultiSampling: OFF] [Screen: 255]
   0.177 Available display adapters: 3
   0.177  [0]: resolution 1360x768px at [0,312]
   0.177  [1]: resolution 1360x768px at [3280,312]
   0.177  [2]: resolution 1920x1080px at [1360,0]
   0.177 Create display on adapter 0. Size 1280x720 at position [30, 6].
   0.273 Initialised OpenGL:[0] AMD Radeon (TM) RX 480 Graphics; driver: 4.5.13474 Compatibility Profile Context 17.10.2
   0.328 Graphics options: [Graphics quality: normal] [Video memory usage: high] [Light scale: 25%] [DXT: false]
   0.408 Loading mod core 0.0.0 (data.lua)
   0.414 Loading mod base 0.14.22 (data.lua)
   0.528 Checksum for core: 1291735968
   0.528 Checksum for mod base: 786624017
   1.070 Info PlayerData.cpp:57: Local player-data.json unavailable
   1.071 Info PlayerData.cpp:60: Cloud player-data.json available, timestamp 1492122595
   1.169 Initial atlas bitmap size is 16384
   1.176 Created atlas bitmap 16384x5589
   1.177 Created atlas bitmap 4096x968
   1.178 Created atlas bitmap 4096x3644
   3.284 Error CrashHandler.cpp:230: Received SIGSEGV
Factorio crashed. Generating symbolized stacktrace, please wait ...
#0  0x000000000088c8bd in Logger::logStacktrace(StackTraceInfo*) at /tmp/factorio-X5N2Rm/src/Util/Logger.cpp:391
#1  0x00000000005c71bb in CrashHandler::writeStackTrace() at /tmp/factorio-X5N2Rm/src/Util/CrashHandler.cpp:105
#2  0x00000000005c7454 in CrashHandler::SignalHandler(int) at /tmp/factorio-X5N2Rm/src/Util/CrashHandler.cpp:235
#3  0x00007f0d85cef4b0 in ?? at ??:0
#4  0x00007f0d86c605a6 in ?? at ??:0
#5  0x00007f0d86ecbae3 in ?? at ??:0
   5.136 Error Util.cpp:77: Unexpected error occurred. If you're running the latest version of the game you can help us solve the problem by posting the contents of the log file on the Factorio forums.
Please also include the save file(s), any mods you may be using, and any steps you know of to reproduce the crash.

[xng]

I have the same or very similar problem, tried on 5 very different computers (amd/intel/radeon/nvidia) running Ubuntu 16.04 LTS based linuxes (Normal, Gnome3 and Mint-Cinnamon), all of the steam version (fresh installs) crash or hang during startup. Then I downloaded the 64 bit tar.gz from factorio's download page, and that starts up without issue.

The crashes are identical, here is one log:

Code: Select all

   0.000 2017-04-22 10:09:39; Factorio 0.14.22 (build 25342, linux64, steam)
   0.040 Operating system: Linux (Ubuntu 16.04)
   0.040 Program arguments: "/home/tkarlsson/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio" 
   0.040 Read data path: /home/tkarlsson/.local/share/Steam/steamapps/common/Factorio/data
   0.040 Write data path: /home/tkarlsson/.factorio
   0.040 Binaries path: /home/tkarlsson/.local/share/Steam/steamapps/common/Factorio/bin
   0.048 System info: [CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz, 8 cores, RAM: 32126MB]
   0.049 Display options: [FullScreen: 0] [VSync: 0] [UIScale: 100%] [MultiSampling: OFF] [Screen: 255]
   0.050 Available display adapters: 2
   0.050  [0]: resolution 1920x1200px at [1920,0]
   0.050  [1]: resolution 1920x1200px at [0,0]
   0.050 Create display on adapter 1. Size 1280x720 at position [310, 222].
   0.229 Initialised OpenGL:[1] AMD Radeon (TM) R9 390 Series; driver: 4.5.13474 Compatibility Profile Context 17.10.2
   0.250 Graphics options: [Graphics quality: normal] [Video memory usage: high] [Light scale: 25%] [DXT: false]
   0.293 Loading mod core 0.0.0 (data.lua)
   0.296 Loading mod base 0.14.22 (data.lua)
   0.353 Checksum for core: 1291735968
   0.353 Checksum for mod base: 786624017
   0.561 Info PlayerData.cpp:57: Local player-data.json unavailable
   0.561 Info PlayerData.cpp:62: Cloud player-data.json unavailable
   0.606 Initial atlas bitmap size is 16384
   0.609 Created atlas bitmap 16384x5589
   0.609 Created atlas bitmap 4096x968
   0.610 Created atlas bitmap 4096x3644
   3.100 Error CrashHandler.cpp:230: Received SIGSEGV
Factorio crashed. Generating symbolized stacktrace, please wait ...
#0  0x000000000088c8bd in Logger::logStacktrace(StackTraceInfo*) at /tmp/factorio-X5N2Rm/src/Util/Logger.cpp:391
#1  0x00000000005c71bb in CrashHandler::writeStackTrace() at /tmp/factorio-X5N2Rm/src/Util/CrashHandler.cpp:105
#2  0x00000000005c7454 in CrashHandler::SignalHandler(int) at /tmp/factorio-X5N2Rm/src/Util/CrashHandler.cpp:235
#3  0x00007f515a3044b0 in ?? at ??:0
#4  0x00007f515b25d5a6 in ?? at ??:0
#5  0x00007f515b4c8ae3 in ?? at ??:0
   3.949 Error Util.cpp:77: Unexpected error occurred. If you're running the latest version of the game you can help us solve the problem by posting the contents of the log file on the Factorio forums.
Please also include the save file(s), any mods you may be using, and any steps you know of to reproduce the crash.
   4.065 Error CrashHandler.cpp:230: Received SIGSEGV
Factorio crashed. Generating symbolized stacktrace, please wait ...
#0  0x000000000088c8bd in Logger::logStacktrace(StackTraceInfo*) at /tmp/factorio-X5N2Rm/src/Util/Logger.cpp:391
#1  0x00000000005c71bb in CrashHandler::writeStackTrace() at /tmp/factorio-X5N2Rm/src/Util/CrashHandler.cpp:105
#2  0x00000000005c7454 in CrashHandler::SignalHandler(int) at /tmp/factorio-X5N2Rm/src/Util/CrashHandler.cpp:235
#3  0x00007f515a3044b0 in ?? at ??:0
#4  0x00007f51507f884b in ?? at ??:0
#5  0x00007f5153317965 in ?? at ??:0
#6  0x00007f5153317731 in ?? at ??:0
#7  0x00007f5153317db4 in ?? at ??:0
#8  0x00007f515278e47c in ?? at ??:0
#9  0x00007f515279a96b in ?? at ??:0
#10 0x00007f515279aa3d in ?? at ??:0
#11 0x00007f515c3386ba in ?? at ??:0
#12 0x00007f515a3d582d in ?? at ??:0
   4.909 Error Util.cpp:77: Unexpected error occurred. If you're running the latest version of the game you can help us solve the problem by posting the contents of the log file on the Factorio forums.
Please also include the save file(s), any mods you may be using, and any steps you know of to reproduce the crash.
  34.907 Received SIGTERM, shutting down

Please note that this bug seems to only exist in the steam version of the executable.

[xng]

I didn't want to leave any stone unturned, and tried turning off steam overlay in the steam settings, and then the steam version of factorio starts up just fine too.

Extra info: To make sure where the error lies I installed a bunch of other games (Prison Architect, RimWorld, Reassembly), turned on overlay, and started them, and they worked fine, then I started factorio again and it hangs during loading (same crash in log after having to do a xkill and then pkill). Then turned off overlay and started factorio again, and it works.

[Xavienth]

Thanks! I'll be using the steam overlay workaround until it's fixed.

[posila]

Hmm, I tried it on our Ubuntu 16.04 computer, and the game worked even with Steam overlay. I noticed you both have Radeon GPU and same version of driver, couldn't it be caused by the driver?

[xng]

Hmm, I tried it on our Ubuntu 16.04 computer, and the game worked even with Steam overlay. I noticed you both have Radeon GPU and same version of driver, couldn't it be caused by the driver?

It is possible, although I did get the same on one computer with Geforce GTX 960, and it does work with overlay in at least 3 other opengl games (all I tried) that seemingly works similar with using sprite texture techniques for its graphics.

Sadly I can't easily do a doublecheck on the Geforce computer anymore as it has Windows only now on its only drive.

I wouldn't count this issue as a dealbreaker anyway. Firstly there is a workaround unless you feel you have to use the overlay for some reason, and secondly, linux have a very small playerbase. I'm really happy for every game where the devs are trying to make it work for us excentrics too. =)

[xng]

[0.15.6] Update:

Changed to oibaf open source mesa drivers, and I don't have problem with overlay in factorio anymore. It doesn't explain everything but it means there is a link between GPU driver version and Factorio implementation for this. (as other opengl games doesn't have this problem).

(For people seeing this and thinking of this solution performance-wise, it is just about the same performance as amdgpu-pro drivers, but you'll be opting out from Vulkan for now)

[Rseding91]

Since switching drivers "fixes" the problem for you I'm going to say this is some external issue to Factorio and not something we're going to spend additional time on.