blank games list after login -2

provide a log with steam-tui 2> error.log

Closing because it seems like the initial error was fixed. Also added custom scripts to help with executables being off

Originally posted by @dmadisetti in #62 (comment)

I did do that, but the error.log is absolutely empty!

Woops. Thought I responded to this. Are you getting blank games or is the caching screen stuck?

Try flushing cache by removing ~/.cache/steam-tui/*

Okay, I did that. Same behavior!

So after flushing, I was not logged in, so I pressed l to sign in, and confirmed with enter.
After that, I see just a blank list!

But now we got one entry in error.log:

steamcmd.sh[3073582]: Restarting steamcmd by request...

I then ran steamcmd again, and logged in, then I ran the latest git build again, and logged in.
List is empty

Then I relaunched it, logged in again, and now suddenly I got a list, and it even found installed games!
But... the error.log doesnt contain anything new!
A bit unfortunate that the games launching that were set to proton do not launch in the same context and instead try baseline wine.

Cool! So can we close this out? What system/ shell do you use though? This is still weird.

You can now write a script to do the launching yourself with proton. Or you can just replace wine with proton here

steam-tui/src/client.rs

Line 234 in f5d2a4f

"wine".to_string(),

Thinking more on windows support, we'll probably have to change launching with wine (no need on windows!)- so maybe we can make the launcher configurable. But let's make a dedicated issue for that

Cool! So can we close this out?

That would be no good choice.
So far, the experience had been inconsistent.
Remember how much effort you put into this project
People might deem it broken and never enjoy it, before they jump through the hoops...

We need to have better error / issue handling.

What system/ shell do you use though? This is still weird.

I do use zsh with zimfw defaults

Blank list of games for me as well. I do not get any errors though.

Can you try off zsh? I can't fix this if I can't replicate it

I'm on zsh

OK- good to have some commonality. Can you try bash on xterm?

same result

I'm on bash/dash (/bin/sh is dash but I used bash interactively, not sure what this program calls on), in st terminal and getting the same behaviour along with no error outputting when I try to make a log file.

Cool, so windows verifiably breaks without logging because line character endings are weird. I'm wondering if whatever steamcmd versions you are using have a similar response.
I just pushed something that adds logging around the problematic area.

If you could respond with your steamcmd version and an error log from "steam-tui 2> error.log" after building the source, that would go a long way.

what is the command for building from source?

cargo build https://doc.rust-lang.org/cargo/getting-started/installation.html

How are you currently getting steam-tui? arch?

the AUR

Seems to work when building from source - the problem is likely in the aur package.

Ok cool. The AUR release commit was borked. I just repushed. Please try from AUR now.

This ended up being a pretty easy fix- so sorry about all the back and forth.

What do you think could have made the process go easier?
Once I guessed it was an issue with AUR, it was pretty easy to find the problem

Should I make a PR template?
Should I have a standard copy pasta for asking for debugging issues?

please give some feedback, because this was needlessly drawn out

Having the standard copy pasta asking for package version & OS, would probably help in this case.

Same error here when building from flake

It appears that running steamcmd manually can help sometimes...
But it's super annoying.

So it's not AUR, and there are no debug logs? Even with the latest commit? I don't know what more I can do, because I cannot replicate

would love to provide debug logs if you tell me how to

steam-tui 2> error.log

error.log
I'm sorry i don't think that gonna be helpful

So it's not AUR, and there are no debug logs? Even with the latest commit? I don't know what more I can do, because I cannot replicate

I think what happens is that when steam is launched, it re-validates the user and invokes steamcmd and gets some kind of token.

When steam-tui is being ran, it doesn't first invoke steam to check if we are up-to-date and what not.
My guesses:

When a update is available on steam

The list may still be there from one time it worked, but no game appears as installed

When the user tried on a bad connection or on VPN

Then the authentication for the login may be revoked

And yes. the log is absolutely empty!

The following I have to do each time:

steamcmd login ... for auth
remove steam-tui caches
steam-tui ... r for reload
steam-tui will hang, need to press q/ctrl+c
start steam-tui again and press r again, then exit
start steam-tui yet another time
game list appears with installed games

My suggestions:

If never ran - then start steamcmd beforehand for initial auth.
Download and install the last steam update programmatically (like steam itself would)
Remove/Clear caches programmatically
Revalidate login token/auth

Step 3 might prompt the user to login again, or its possible to re-use the cookie or something.

The log actually looks very useful, steam version is embedded and we know that at least "info" was invoked. I'll take another look at it this weekend. If others can provide logs that would also be useful.

@zDEFz I will try that

Issue still present