[2.0.76][linux] Crash on startup

Anything that prevents you from playing the game properly. Do you have issues playing for the game, downloading it or successfully running it on your computer? Let us know here.
cultab
Manual Inserter
Manual Inserter
Posts: 3
Joined: Fri Mar 20, 2026 8:14 pm
Contact:

[2.0.76][linux] Crash on startup

Post by cultab »

Factorio crashes on startup and the proccess remains running. It appears on the taskbar but never goes into fullscreen.

Crash log (also attached as file):

Code: Select all

   0.000 2026-03-20 22:00:08; Factorio 2.0.76 (build 84451, linux64, steam)
   0.000 Operating system: Linux
   0.000 Initializing Steam API.
   0.000 Program arguments: "/var/home/evan/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio"
   0.000 Config path: /var/home/evan/.factorio/config/config.ini
   0.000 Read data path: /var/home/evan/.local/share/Steam/steamapps/common/Factorio/data
   0.000 Write data path: /var/home/evan/.factorio [28497/476938MB]
   0.000 Binaries path: /var/home/evan/.local/share/Steam/steamapps/common/Factorio/bin
   0.009 System info: [CPU: AMD Ryzen 5 3600 6-Core Processor, 12 cores, RAM: 23967 MB]
   0.009 Environment: DISPLAY=:0 WAYLAND_DISPLAY=wayland-0 DESKTOP_SESSION=plasma XDG_SESSION_DESKTOP=KDE XDG_CURRENT_DESKTOP=KDE SDL_VIDEODRIVER=<unset> __GL_FSAA_MODE=<unset> __GL_LOG_MAX_ANISO=<unset> __GL_SYNC_TO_VBLANK=<unset> __GL_SORT_FBCONFIGS=<unset> __GL_YIELD=<unset>
   0.020 Display options: [FullScreen: true] [VSync: true] [UIScale: automatic (100.0%)] [Native DPI: true] [Screen: 255] [Special: lmw] [Lang: en]
   1.003 Video driver: x11
   1.003 Available displays: 2
   1.003  [0]: DP-1 24" - {[0,0], 1920x1080, SDL_PIXELFORMAT_RGB888, 144Hz}
   1.003  [1]: HDMI-A-1 22" - {[1920,0], 1080x1920, SDL_PIXELFORMAT_RGB888, 75Hz}
   1.183 Initialised OpenGL:[0] NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2; driver: 3.3.0 NVIDIA 580.95.05
   1.183   [Extensions] s3tc:yes; KHR_debug:yes; ARB_clear_texture:yes, ARB_copy_image:yes, ARB_pipeline_statistics_query:yes, ARB_gl_spirv:yes, ARB_ES2_compatibility:yes
   1.183   [Version] 3.3
   1.365 Error CrashHandler.cpp:643: Received 6
Factorio crashed. Generating symbolized stacktrace, please wait ...
src/Util/StacktraceToStream.cpp (52): walkStackAndPrintToStream
src/Util/StacktraceToStream.cpp (60): printStacktraceToStream
src/Util/Logger.cpp (336): writeStacktrace
src/Util/Logger.cpp (381): logStacktrace
src/Util/CrashHandler.cpp (181): writeStackTrace
src/Util/CrashHandler.cpp (644): commonSignalHandler
src/Util/CrashHandler.cpp (652): SignalHandler
0x7f0447acd28f
__pthread_kill_implementation
raise
abort
__libc_message_impl.cold
malloc_printerr
malloc_printerr_tail
0x7f042324e5fb
0x7f042325d2f5
0x7f04232cea43
0x7f04233d9223
start_thread
__GI___clone3
0xffffffffffffffff
Stack trace logging done
Tested various versions:
  • 2.0.76 crash
  • 2.0.75 crash
  • 2.0.69 crash
  • 2.0.60 crash
  • 2.0.32 works
  • 2.0.7 works
Tested:
both x11 and wayland in factorio's config.ini
Attachments
factorio-current.log
(2.26 KiB) Downloaded 3 times
User avatar
pioruns
Filter Inserter
Filter Inserter
Posts: 271
Joined: Tue Nov 05, 2024 3:38 pm
Contact:

Re: [2.0.76][linux] Crash on startup

Post by pioruns »

Try running directly, not through Steam. Download the game from https://factorio.com/download
cultab
Manual Inserter
Manual Inserter
Posts: 3
Joined: Fri Mar 20, 2026 8:14 pm
Contact:

Re: [2.0.76][linux] Crash on startup

Post by cultab »

pioruns wrote: Sat Mar 21, 2026 9:49 am Try running directly, not through Steam. Download the game from https://factorio.com/download
Huh, works just fine this way. Any idea why? I'd like to avoid having to move my saves, blueprints, etc. out of the steam cloud.

EDIT: changed write data directory to .factorio and got all my saves etc.
User avatar
pioruns
Filter Inserter
Filter Inserter
Posts: 271
Joined: Tue Nov 05, 2024 3:38 pm
Contact:

Re: [2.0.76][linux] Crash on startup

Post by pioruns »

Glad you sorted it.

I think that's the reason:

Code: Select all

Environment: DISPLAY=:0 WAYLAND_DISPLAY=wayland-0
Video driver: x11
You are running Wayland but X11 gets involved somehow, and game crashes. Maybe Steam is telling it to do it - do you have Steam installed indirectly via some Snap or Flatpak?

I've checked my logs (running Factorio directly), and I see:

Code: Select all

WAYLAND_DISPLAY=wayland-0
Video driver: wayland
That's how it should be I guess.
cultab
Manual Inserter
Manual Inserter
Posts: 3
Joined: Fri Mar 20, 2026 8:14 pm
Contact:

Re: [2.0.76][linux] Crash on startup

Post by cultab »

pioruns wrote: Sat Mar 21, 2026 11:51 pm Glad you sorted it.

I think that's the reason:

Code: Select all

Environment: DISPLAY=:0 WAYLAND_DISPLAY=wayland-0
Video driver: x11
You are running Wayland but X11 gets involved somehow, and game crashes. Maybe Steam is telling it to do it - do you have Steam installed indirectly via some Snap or Flatpak?

I've checked my logs (running Factorio directly), and I see:

Code: Select all

WAYLAND_DISPLAY=wayland-0
Video driver: wayland
That's how it should be I guess.
Probably not, because the same env vars show up in the standalone version. I don't know exactly how Bazzite installs steam, but I know it's deliberately not a snap nor flatpak, to avoid issues.

Code: Select all

   0.000 2026-03-21 22:06:56; Factorio 2.0.76 (build 84451, linux64, full)
   0.011 Operating system: Linux (Bazzite 43)
   0.011 Program arguments: "/home/evan/Games/factorio/bin/x64/factorio" 
   0.011 Config path: /var/home/evan/Games/factorio/config/config.ini
   0.011 Read data path: /var/home/evan/Games/factorio/data
   0.011 Write data path: /var/home/evan/Games/factorio [22809/476938MB]
   0.011 Binaries path: /var/home/evan/Games/factorio/bin
   0.018 System info: [CPU: AMD Ryzen 5 3600 6-Core Processor, 12 cores, RAM: 23967 MB]
   0.018 Environment: DISPLAY=:0 WAYLAND_DISPLAY=wayland-0 DESKTOP_SESSION=plasma XDG_SESSION_DESKTOP=KDE XDG_CURRENT_DESKTOP=KDE SDL_VIDEODRIVER=<unset> __GL_FSAA_MODE=<unset> __GL_LOG_MAX_ANISO=<unset> __GL_SYNC_TO_VBLANK=<unset> __GL_SORT_FBCONFIGS=<unset> __GL_YIELD=<unset>
Anyway, the workaround works, thank you :D !
Post Reply

Return to “Technical Help”