[beta][linux] the client is not starting anymore after today update

[MrΩ]

I get a window saying "transport error" 0x3008. Whatever I do I cannot get the update beta client to work (I reverted to non beta, removing $steam_dir/package/beta file).

(I cannot post issues on github anymore because microsoft broke noscript/basic (x)html browser interoperability very recently).

[lostgoat]

Can you try installing `lsof` and let me know if that fixes the issue?

[MrΩ]

Originally posted by lostgoat:

Can you try installing `lsof` and let me know if that fixes the issue?

I have lsof.

[lostgoat]

That is the most likely root cause for this error message. Can you check ~/.steam/steam/logs/console_log.txt to verify why it is failing?

Steam searches for lsof in the following locations:
"/usr/sbin/lsof", "/usr/bin/lsof", "/sbin/lsof", "/bin/lsof", "lsof" (from PATH)

[MrΩ]

My version of lsof is in PATH. And it is busybox version 1.36.1. Don't tell me a hard dependency on some bloaty lsof was added in the latest update :'(

I am going to restart the client in beta mode.

EDIT ---

console_log.txt:
[2025-02-06 22:46:54] Error: GetIPCConnectionDetails: lsof is required to run steam - please install

Then I guess the client now require a specific version of lsof (which you should distribute as a statically linked ELF64 binary), come on dudes...

[lostgoat]

> Then I guess the client now require a specific version of lsof

No, a specific version is not required.

The error you pasted above means it couldn't find the binary in the first place.

Can you try symlinking your version of lsof to one of the locations I pasted above? I suspect the PATH search might be what is broken.

[MrΩ]

Did a symlink in /bin. My lsof is now found, but the beta client is still not loading but with 0x3009 as an error code:
here a pastebin of my console_log.txt https://paste.c-net.org/MerrierEdition

EDIT---

But now the non-beta client does restart every few minutes!

[lostgoat]

Looks like your version of lsof does not support either the -i or -F parameters. It is listing all files instead of just the specific file we are querying. And it is not returning machine readable output via -F.

So it does seem like your version of lsof is indeed incompatible.

I will take a look at the PATH search logic. However, you will still have the second problem. We aren't going to re-distribute an lsof binary with steam, so I'd recommend installing a version that supports the features mentioned above in your system.

[MrΩ]

Originally posted by lostgoat:

We aren't going to re-distribute an lsof binary with steam, so I'd recommend installing a version that supports the features mentioned above in your system.

I hope you understand why this is wrong, no offence intended.

I'll try to get some plain and simple C code version implementing a compatible lsof, I'll compile it and test it tomorrow (sorry, had a long day, need a change of mind).

I did remove the symlink since it makes the current non-beta client restart every few minutes.

I'll keep you posted here of the results.

EDIT ---

Got myself a lsof implementation on microsoft https://github.com/lsof-org/lsof version
4.99.4.
I did build this implementation as a static pie binary. I did put this binary in /bin since the PATH lookup does not work.
The beta client is now starting again and seems to be working ok.

Guys, this implementation has a liblsof with a permissive licence, please have the decency to statically link it to your binaries (or you could have copied the relevant code which does parse sysfs/procfs), come on...

[76561197968101289]

I have the same error after the update. I launch Steam on Macbook via the Whisky utility.

[KaBAN4ik]

Hello everyone, I encountered this situation. I often use the "Whiskey" tool to run Windows programs on a Mac, after reinstalling Steam in Whiskey it stopped running, errors 0x3009 and 0x3008. Completely clearing the cache, removing Wine and Whiskey did not help, reinstalling Steam also did not give results. Even manually installing Homebrew and Wine did not give results. The only thing that helped was completely removing the operating system from the Mac and installing a new one. Maybe this will be useful to someone, if someone has encountered such a problem and solved it in another way, I will be grateful for the information.