Can confirm. Debian Bookworm, same exact phenomena.
The description of the images was missing.
The first captured image shows SteamCMD in operation.
The second one shows stderr.txt.
Hey @danieljennings, can you fix this? This is a serious problem. We should at least have a way to redirect the stderr to stdout. app_info_print should not be redirected to stderr in the first place...
Why does Valve keep breaking existing functionality? Ugh...
Should be fixed in latest update.
Confirmed working now.
Nothing extracted yet.
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
Sorry if this is difficult to read as I am using machine translation.
I am experiencing the same problem on Fedora38.
When I run steamcmd.sh, the "Steam>" that is normally displayed is not displayed, and even typing commands in a cursory manner does not produce any errors.
All commands and execution results on the console are redirected to "logs/stderr.txt" as error output, so even if the command is successful, everything is treated as an error.
steam-logs.tar.gz