-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blank games list after login -2 #73
Comments
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. But now we got one entry in error.log:
I then ran Then I relaunched it, logged in again, and now suddenly I got a list, and it even found installed games! |
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 Line 234 in f5d2a4f
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 |
That would be no good choice. We need to have better error / issue handling.
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. 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?
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... |
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 |
|
error.log |
I think what happens is that when When steam-tui is being ran, it doesn't first invoke steam to check if we are up-to-date and what not. When a update is available on steam
When the user tried on a bad connection or on VPN
And yes. the log is absolutely empty! The following I have to do each time:
|
My suggestions:
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 |
I did do that, but the
error.log
is absolutely empty!The text was updated successfully, but these errors were encountered: