Factorio Forums

1. What did you do?
Tried playing the game after about a 6-month pause.

2. What happened?
The game won't launch correctly either when launched through Steam or by executing the standalone binary downloaded from Factorio's website.
When running in X11 compat mode (XWayland, GNOME 50), it will display a black window with a gray bar on top (where GNOME's HUD would be) and hang until terminated. With the Wayland backend, the window won't even show up and the game's process will keep running until manually killed.
I've tried deleting "~/.factorio" from my system, but it didn't help. Also, tried combining the SDL_VIDEODRIVER=wayland environment variable, --gfx-safe-mode and --fullscreen=false flags to no avail.

3. What did you expect to happen instead?
For the game to launch successfully as it once did on the same system.

4. Does it always happen, once, or sometimes?
Always.

The issues began with Fedora 43: the Steam version wouldn't launch, but the standalone version did. However, after upgrading to Fedora 44, neither does anymore.

I should add that this happens on my desktop computer (NVIDIA RTX 2060, driver 595.71.05), but it doesn't on my laptop (AMD iGPU - Ryzen 7 5700U); both running Fedora 44.
Tested every version between 2.0.76 and 2.0.73 and none launch

Your Log says " 0.483 Video driver: x11"

What's the result if you run this in terminal?
echo $XDG_SESSION_TYPE

PS: Just checked my own Fedora 44, Amd GPU, standalone - no problem

Nosferatu wrote: Wed May 13, 2026 4:03 am What's the result if you run this in terminal?
echo $XDG_SESSION_TYPE

The result is `wayland`. Fedora 44 upgraded to GNOME 50 and the code for X11 sessions has been fully removed from the codebase, it's Wayland only now.

I have also tried placing the config.ini file from 9300 - since it crashes before generating that file in .factorio - in hopes that it would contain some field which I could edit to forcibly make the game try to launch with the Wayland backend, but unfortunately it doesn't include that option.

TarsiSurdi wrote: Wed May 13, 2026 11:12 am

Nosferatu wrote: Wed May 13, 2026 4:03 am What's the result if you run this in terminal?
echo $XDG_SESSION_TYPE

The result is `wayland`. Fedora 44 upgraded to GNOME 50 and the code for X11 sessions has been fully removed from the codebase, it's Wayland only now.

I have also tried placing the config.ini file from 9300 - since it crashes before generating that file in .factorio - in hopes that it would contain some field which I could edit to forcibly make the game try to launch with the Wayland backend, but unfortunately it doesn't include that option.

In my config.ini the setting for wayland is


; Options: x11, wayland
linux-preferred-video-driver=wayland

Just tried copying the config.ini file from my laptop's ".factorio/config" folder (which works) to the desktop and I get the same crash when launching with the wayland backend. Logs attached.

This behavior can probably be attributed to some change between versions 2.0.32 (works) and 2.0.60 (doesn't work), as also discussed here 133133

A memory dump might help diagnosing this, but I do not know how to create one on linux.

I didn't either but think I managed to generate one:

1. Launched the game;
2. While it hanged, I checked for its PID;
3. Ran gcore PID (substituting PID for the actual number);
4. Compressed the dump (1.7GB -> 181 MB).
Here's the output: factorio-dump.zip (Google Drive)

Hope this helps you out on diagnosing the issue further :)

I believe this to be related to the NVIDIA proprietary driver for Linux, as I have recently swapped my RTX 2060 for an RX 9070XT and the issues mentioned in this thread, on the same setup, are completely gone.