Hi there, I’ve recently installed the Os and have been playing Factorio for a while and after some time playing it my whole system simply frezees. I cant open the console to kill the game cant reboot from console, literally can’t do anything but hold down the power button till the pc shuts down.
I’ve tried some fixes that i found for similar problems both here and on the arch wiki, like:
Changing the kernel to LTS
Updating all drivers
Adding a swap file
I would also like to note that I previously had installed PopOs and never had this problem, and that my machine is dual booting EndeavourOs with Windows 11.
I really don’t know why this could be happening, I’d be very grateful if someone could help.
My guesses are that it has to do something with arch based distros or with Kde Plasma, but i don’t know, I’m not experienced in this environment.
Specs-
CPU- 8 × 11th Gen Intel® Core™ i7-1195G7 @ 2.90GHz
Memory- 15,4 GiB of RAM
Graphics- Mesa Intel® Xe Graphics
Kernel - 6.6.44-3-lts (64-bit)
The swap file is 4gb
I’d like to apologize for my English as it isn’t my native language.
Let’s get some details, to hopefully help diagnose possible causes. Each of these commands will generate a link that you can share here, so we can see the output.
First up, you might provide us with some detailed hardware information:
inxi -Fxxc0z | eos-sendlog
When the crash happens, immediately reboot and run this. It will output the last 100 lines of your system journal from your previous session (right up to the moment it crashed).
Here is the link provided by the first command you recommended, as soon as there is a game crash I’ll update you with the other one.
I’d like to mention that while searching for more similar issues to mine, I’ve changed the kernel to zen (6.10.3-zen1-2-zen), and have run a memtest with all the outputs deemed as ok.
So not even 10 minutes into my session ant the whole system froze, I reboot the machine and first thing ran the command you told me to, and it gave me this as output. https://0x0.st/XWwN.txt
After reading this report a little bit at the end, I saw some complaints about Wayland, taking into account that Factorio supports it is not the game’s fault. So with this in mind I started the pc in X11 but (barely played yet) I can now notice some major screen tearing. Only after turning VSync on does it go away
Sorry forgot to edit the comment and enter it I did, and it worked my only issue now (that the crashing and tearing is fixed) is to know why Wayland and is crashing and if there’s any way to fix the issue since Wayland is supposedly lighter on the system.
Well, Factorio runs native on Linux, but maybe the Wayland implementation is not up to par. You could try to switch to a Proton version, maybe the Windows version runs better.
Ok this really seems like a Wayland bug with factorio I’ve been playing a little bit and got another crash, this was the output of the journal command.
It does look like Wayland is the culprit. It’s still pretty fresh on the scene, and it’s certainly not without its bugs. I’d suggest just giving it time.
The hard locks and forced resets can’t be healthy for your system. Each one of those risks more serious problems. Perhaps try again after a few months, once updates have progressed a bit more (I’m in the same boat with my workstation, as a Nvidia user).
The same bug currently exists when playing World of Warcraft through proton (or other runners, tried several).
The whole system freezes after about an hour when using wayland but if you choose a X session in kde upon login instead it works just fine.
My System:
7800x3d
64GiB RAM
7900xt
Kernel: 6.10.X default arch kernel (not sure this was some weeks ago)
Open source amd drivers / mesa
I also spoke to a guy in the lutris discord who has the exact same problem with WoW.
He was using 6700xt on a different distro, different WM, different DE.
I tried GE-Proton9-11(Bottles), GE-Proton9-10(Bottles), GE-Proton8-26 (lutris), and Proton 9.0.2(Steam).
I did encounter the freeze on all of them when using wayland.
It happens with applications running on vulkan (or in a layer like proton on vulkan).
It happens both on native and on apps running on proton/wine.
For me, @Steath and @kpgm it has only happen while using mesa’s drivers.
At least on my experience, Running on windowed doesn’t seem to cause the crash, only on fullscreen.
For me, the moments that had lead to a Freezz were always after I alt-tab on fullscreen after playing for a while, examples are:
A. Running a game on proton.
B. Running a Xwayland application like duckstation or ppsspp and booting a game on vulkan render.
C. Running a Native Vulkan Game.
If I run duck or ppsspp on openGL render I never encounter this crash, neither if I play on x11.
#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
#QT_QPA_PLATFORMTHEME=qt5ct
#QT_STYLE_OVERRIDE=kvantum
BROWSER=firefox
EDITOR=nano
I posted an issue like this several months ago. Still happens actually. The only way I can play horizon zero dawn is windowed. When I make it full screen it freezes bout 20 seconds into the game. It plays fine with window the size of the screen. Something about full screen…