powergod: From your description this is a different issue than the one described in the first post.
What do you mean with "after they turn offline" ?
ArlekinV: Currently i have four connection - EGS, Origin, Uplay and Steam. EGS after insertion of credentials never connects and in infinite "connecting" status. Others connection do connect, but after few minutes they turn into "Connection offline" with retry option that does nothing. If i restart Galaxy app with connections that are offline - everything just resets to the point that none of the accounts is connected and none of account info was added. To do a little summary - i can use only gog account and can't use any other connections, that's started after 2.0.58 update.
Then your problem seems created by the EGS integration, because Galaxy launches integrations one after another, if one integration fails to finish its job or goes to a loop, all the others after that one will not even start.
I don't have this issue, but a similar one, that makes visible how Galaxy works with integrations, and looking at their list on the settings at the start of Galaxy, this is what happens:
- All of the ones that are starting are without a button
- The first 2 at some point shows a button with the "Disconnect" label, while all the others still have no button
- Then Indiegala starts connecting, and it is SUPER SLOW... when it finally is connected (because in this case it is actually able to finish the connection), ALL the integrations that still weren't connected are in a "Retry" status.
- I then "Retry" the remaining ones and them connects without issues.
If I remove the Indiegala integration, all the others connects without issues at the beginning.
In your case, the EGS integration seems not only slow, but unable to finish its job, and because it doesn't finish, Galaxy will never starts the integrations that are in line after it.
The integration launch order chosen by Galaxy is obscure to me, but it's always the same at every start.
In my case, could have been useful to put Indiegala as the last Integration launched, but I don't know if it's possible to hack the launch order...
In your case, should be better to remove or substitute that not working integration, at least until you can find a solution to that connection problem.