TF2 not launching on Linux

[Frances Halladay]

I'm playing this using Proton on Arch Linux, until yesterday I had zero issues starting up the game except for the occasional wait; today it won't launch at all.

Right now when I launch the game it gives me the "set up" window for EA's new program -- where it says "Customize setup" and "Let's go" and only the latter option works -- after "going", a bar slowly fills up and then gives me an error message from the installation window itself and nothing else happens when I close this window.

It seems if I annoy my computer enough it will just say "running EA install script" in my Steam library and then not even give me the window for the installation script. This thing was already installed before today and working perfectly so I'm not sure what the problem is and I don't believe in that rock and astrology stuff in-case somebody tells me it's the universe giving me a sign.

Help would be greatly appreciated, thanks in advance.

[Kyral]

force experimental or use northstar proton
otherwise it's a distro issue, arch is garbage in terms of reliability

[Frances Halladay]

Originally posted by Kyral:

force experimental or use northstar proton
otherwise it's a distro issue, arch is garbage in terms of reliability

Neither of these work.

[Kyral]

Originally posted by Frances Halladay:

Originally posted by Kyral:

force experimental or use northstar proton
otherwise it's a distro issue, arch is garbage in terms of reliability

Neither of these work.

distro issue then

[Frances Halladay]

Originally posted by Kyral:

distro issue then

I can believe that but is there really nothing else I can do? It was working just fine before and I don't recall updating anything before it stopped.

[Aom]

try reinstall. ea app games have so many problems with linux.

[Frances Halladay]

Originally posted by Aom:

try reinstall. ea app games have so many problems with linux.

I didn't end up trying this because this morning it just started working again. I saw one other Arch Linux user with I think the same problem and I'm assuming it had something to do with EA updating but I'm unsure whether it did or not.

Since the problem has seemingly fixed itself I'll just mark this as solved.