Ref: https://github.com/ValveSoftware/steam-runtime/issues/705.

The issue is that Factorio is not respecting $HOME.

...and systemd breaking getpwuid for no reason


My apologies, for my unusual setup. I was experimenting with systemd-homed a long time ago and put too much thought into /home ...

I think I have made some progress about this issue.

My linux user account is systemd-homed managed btrfs subvolume and mounted to /home/zhaow at login. When I switched to a normal user, Factorio works fine. When I'm using homed-managed user, and not using Steam Linux Runtime, Factorio works fine ...

I reinstalled my physical archlinux machine, then installs steam and factorio, in hope that re-install would solve this problem - but it doesn't.

based on this link I modifies launch option to:

steam-runtime-launch-options -- %command%

which brings up a configuration UI. based on my test ...

May I ask that is Factorio for steam compiled with any steam linux runtime SDK? Valve documents that these "steam linux runtime" needs specific "steamrt-dev" etc to work. From the linked document below, I think factorio needs to be compiled with specified runtime sdk to work in specific runtime ...

I tried `-compat-force-slr off` and it works! With that option factorio can load correctly and landed me on main menu.

I wonder what's the root cause of this behavior ...

I think I have the same issue.

step for reproduce: with my dirty setup of Arch Linux, start steam and click launch from steam
expected behavior: game launches
actual behavior:
* there's no sign of game launching, steam would flip back to launch after a short duration
* in the system journal I'd ...

Sure enough, the pipes seem to choke at roughly 1GW/pipe. There doesn't seem to be any pattern as to which paths after the chokepoint get the energy, but the final electricty output is quite definitely capped at ~1GW/pipe width.
You're right about 1GW/pipe. they specified that in the base mod ...