intermittent GUI errors on Windows 11

[otizonaizit]

On Windows 11, with a fresh Anaconda installation and git-bash and after installing the current release using pip, starting pelita the first time terminates with the error in the screenshot.

Starting pelita again seems to work. At some point after starting pelita the first time, a security pop-up from the Windows-Firewall appears, asking to allow pelita to do stuff on the network. It could be that the two facts are related, but it is super difficult to reproduce.

[otizonaizit]

Exactly the same procedure on Windows 10 did not throw any error

[Debilski]

Actually, I could just reproduce the same problem on my Linux at work. It is related to #778. The issue happens when the network players are slow to start. (See the PlayerDisconnected notice.) This could be due to a slow file system (my problem at work) or due to a firewall requesting action.
It usually only happens once per session. As soon as the libraries are cached, startup will be faster and there won’t be a network timeout.

Of course, the Tk instance should not fail when this happens. (And we should adjust the initial timeouts so that it does happen less often.)