Steam connection fails on Arch Linux (Steam using system libraries) about isaac-racing-client HOT 4 CLOSED

I haven't tested the client on Linux for a while, but it should work.

What is the app trying to do in this phase?

It's trying to get your steam ID so that it can use that to login. Here are the relevant lines:

https://github.com/Zamiell/isaac-racing-client/blob/master/src/steam.js#L74-L129

(line 115 looks like a debug line that I forgot to cleanup, so ignore that)

This steam.js is a child process. It talks to the other steam.js (in the renderer process, through the main process) here:
https://github.com/Zamiell/isaac-racing-client/blob/master/src/js/steam.js

First off, try inserting print statements all through both steam.js files to see exactly what line it is getting stuck on.

from isaac-racing-client.

To clarify: You actually can't put print statements in a child process. You have to do:

process.send('getting here lol');

as alluded to from line 115. In the renderer process, you do:

globals.log.info('getting here poop');

from isaac-racing-client.

Thanks for the tips, I got it to work. On Arch Linux (maybe on other distributions too) there are different ways to run the Steam client. One is with Steam's own installed libraries and another is to use the system's libraries. I'm usually using the latter, native method, because it's more stable and a lot of the times there are various issues with the libs provided by Steam.

So, running Steam using the runtime method (with it's own libraries) solves the issue, and the racing client can connect successfully almost instantly.

I'd guess greenworks tries to call something that doesn't exist or just doesn't respond the way it's expected? Since it's probably not related to the Isaac racing client, I close the issue.

from isaac-racing-client.

Nice, good to hear.

from isaac-racing-client.