Daniel Johnson

Well, the log shows this: ``Which flatpak-spawn: None`` That means it could not find ``flatpak-spawn``- it's using shutil.which() to find it, but that returns None. I've added a bypass- it...

I haven't a clue- but maybe the logs would help. My idea is that that logs have timestamps in them, and if we can see a 30-second gap in the...

I think this specific crash got a fix back in April. In any case I've made some effort to improve the robustness of the PreferencesDialog. Please download [the latest master](https://github.com/lutris/lutris)...

That is a different issue; you should file that separately, with a full (debug) log. Hopefully we'll be able to tell what it is trying to download.

I think this is fixed.

It might help if you could provide a debug log. Add the ``-d`` option to your command and give us the log spam, please.

Didn't have time to do much about this today, but I note that the log does not show the debug message I expected to see- "Game thread stopped". That should...

Hmm. Did a little testing, and I didn't have the same problem. I killed the game with Monitor; just terminated the game process (not lutris-wrapper). Is that how I should...

I am not too clear on this. Your terminal dump seems to me to show you killing *Lutris*, but that can't be right. You are stopping the game, right?

Oooh. I didn't understand. I don't know why we shouldn't react to SIGTERM with a more controlled shutdown. But I have to ask- why do you want to do this?