Steam stuck at login with websocket error

ryuukk commented 2 weeks ago

vvvvvvvvvvvvvvvvvvvv 📣 WORKAROUND FOUND: start steam with steam -tcp https://github.com/ValveSoftware/steam-for-linux/issues/11216#issuecomment-2318253260 ^^^^^^^^^^^^^^^^^^

Your system information

Steam client version (build number or date): steam 1.0.0.81-2
Distribution (e.g. Ubuntu): arch linux
Opted into Steam client beta?: No
Have you checked for system updates?: Yes
Steam Logs: steam-logs.tar.gz
GPU: AMD RX 6600 XT

Please describe your issue in as much detail as possible:

Doesn't start, nothing show up

If i start with the command -v, it's stuck on the sign-in menu

Steps for reproducing this issue:

$ steam -nofriendsui -v

steam.sh[74695]: Running Steam on arch rolling 64-bit
steam.sh[74695]: STEAM_RUNTIME is enabled automatically
setup.sh[74770]: Steam runtime environment up-to-date!
steam.sh[74695]: Steam client's requirements are satisfied
[2024-08-29 18:02:04] Startup - updater built Jul 16 2024 23:21:18
[2024-08-29 18:02:04] Startup - Steam Client launched with: '/home/ryuukk/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened' '-nofriendsui' '-v'
08/29 18:02:04 minidumps folder is set to /tmp/dumps
08/29 18:02:04 Init: Installing breakpad exception handler for appid(steam)/version(1721173382)/tid(74823)
[2024-08-29 18:02:04] Loading cached metrics from disk (/home/ryuukk/.local/share/Steam/package/steam_client_metrics.bin)
[2024-08-29 18:02:04] Using the following download hosts for Public, Realm steamglobal
[2024-08-29 18:02:04] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2024-08-29 18:02:04] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2024-08-29 18:02:04] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2024-08-29 18:02:04] Verifying installation...
[2024-08-29 18:02:04] Verification complete
UpdateUI: skip show logo
Steam logging initialized: directory: /home/ryuukk/.local/share/Steam/logs

/usr/share/themes/Arc-Dark/gtk-2.0/main.rc:1090: error: unexpected identifier 'direction', expected character '}'
/usr/share/themes/Arc-Dark/gtk-2.0/apps.rc:91: error: unexpected identifier 'direction', expected character '}'
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xd8660dc0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xd865f500
CAppInfoCacheReadFromDiskThread took 72 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 75054
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
src/clientdll/cminterface.cpp (3556) : m_VecAddressWebSocketCMs.Count()
src/clientdll/cminterface.cpp (3556) : m_VecAddressWebSocketCMs.Count()
assert_20240829180206_28.dmp[75157]: Uploading dump (out-of-process)
/tmp/dumps/assert_20240829180206_28.dmp
assert_20240829180206_28.dmp[75157]: Finished uploading minidump (out-of-process): success = yes
assert_20240829180206_28.dmp[75157]: response: CrashID=bp-734ef9e5-430e-4a03-9b64-69cbe2240829
assert_20240829180206_28.dmp[75157]: file ''/tmp/dumps/assert_20240829180206_28.dmp'', upload yes: ''CrashID=bp-734ef9e5-430e-4a03-9b64-69cbe2240829''

mahlersand commented 2 weeks ago

I have the same issue. Resetting the steam runtime using steam-runtime --reset does NOT help. The client is stuck at the login screen (Post sign-in).

Rosentti commented 2 weeks ago

Oops. Filed a duplicate issue :D I'll copy my findings here.

Your system information

Steam client version (build number or date): 1724878532
Distribution (e.g. Ubuntu): Arch Linux
Opted into Steam client beta?: Families Beta
Have you checked for system updates?: No
Steam Logs: steam-logs.tar.gz
GPU: AMD

Please describe your issue in as much detail as possible:

Steam does not get past logging in. Websocket CMs are gone, and the linux client seemingly does not support anything else. This can be confirmed by visiting https://api.steampowered.com/ISteamDirectory/GetCMListForConnect/v1/?cellid=5&cmtype=websockets, which results in "Internal Server Error", or not specifying a filter results in only netfilter CMs. The cell does not seem to matter, they are gone globally.

Steps for reproducing this issue:

Try to launch steam.
Permanently stuck here

kisak-valve commented 2 weeks ago

Until this gets looked at closer, starting Steam with -tcp might workaround the issue.

kattjevfel commented 2 weeks ago

steam -tcp workaround works for me, hope this gets fixed for real soon

JStrategic commented 2 weeks ago

having the same issue!

Tannenfels commented 2 weeks ago

steam -tcp workaround works for me, hope this gets fixed for real soon

It starts, true, but now my Steam Clowd is unavailable.

prplwtf commented 2 weeks ago

Same issue over here as well! Tried multiple devices, happening on both my laptop and desktop. (both running Arch Linux and Hyprland, different configurations)

Both devices had the same problem on both the Flatpak versions and pacman repository versions. Running Steam with the -tcp argument appears to work.