Steam won't launch today, logs flooding with "websocket unexpectedly closed" and "websocket error" lines (Seemingly no system updates, no changes, nothing. Just booted today)

[ipaqmaster]

Your system information

• System information from steam (Steam -> Help -> System Information) in a gist: I cannot get this because Steam is stuck.

GPU: NVIDIA 2080Ti (nvidia-dkms/545.29.06-1) OS/Kernel: Archlinux/6.6.9-arch1-1

• Have you checked for system updates?: [Yes/No]

Yes, I also tried steam --reset which didn't help.

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large pastes as a Github Gist.

Was using Steam last night and playing CS2. Went to play CS2 today and the desktop icon was not doing anything and neither was the Steam tray UI icon.

I checked tail -f -n0 ~/.steam/steam/logs/* and the various log files are being flooded indefinitely with lines such as:

[2024-02-17 11:08:51] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: failed to connect: 2 - failed to connect to websocket
[2024-02-17 11:08:51] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: re-try connection 0/20
[2024-02-17 11:08:51] SP Shared JS Context-'SharedJSCo': ERROR: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=6b324421ffcd9c747ef2:1: failed to connect to websocket

[0217/110851.572649:INFO:CONSOLE(1)] "failed to connect to websocket", source: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=6b324421ffcd9c747ef2 (1)
[0217/110851.572735:INFO:CONSOLE(1)] "websocket error", source: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=6b324421ffcd9c747ef2 (1)
[2024-02-17 11:08:51] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: re-try connection 1/20
[2024-02-17 11:08:51] SP Shared JS Context-'SharedJSCo': ERROR: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=6b324421ffcd9c747ef2:1: websocket error
[0217/110851.573488:INFO:CONSOLE(1)] "websocket unexpectedly closed", source: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=6b324421ffcd9c747ef2 (1)
[2024-02-17 11:08:51] SP Shared JS Context-'SharedJSCo': ERROR: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=6b324421ffcd9c747ef2:1: websocket unexpectedly closed
[0217/110851.573560:INFO:CONSOLE(1)] "websocket error", source: https://steamloopback.host/chunk~2dcc5aaf7.js?contenthash=6b324421ffcd9c747ef2 (1)

I was just playing CS2 last night. No system changes, updates or anything and now Steam refuses to launch. Tried launching it with --reset and the tray icon won't even appear now.

That domain resolves to 127.0.0.1 successfully and these logs are flooding hundreds of these error lines per second.

Steam still launches perfectly fine on my Laptop of an identical environment though it only has an intel iGPU, so no NVIDIA driver. But an identical SOE. This laptop is on the same vlan as my desktop featuring the same DNS settings (my search domain plus the gateway IP as the nameserver IP, which itself runs named) ruling out any local routing or DNS problems.

Steps for reproducing this issue:

1. Open Steam or have the desktop auto-launch it like any other morning
2. Despite working yesterday and a few varying titles, today it does not launch. Steams logs are being flooded with websocket errors.

[ipaqmaster]

After over an hour of troubleshooting and screwing around... it suddenly popped up asking for login. I closed Steam again and rsync'd my steam home .local/Steam environment back to undo my earlier --reset call and yeah everything is working again. I logged out of my DM/WM and back in and it started on login successfully too (?????).

Inconclusive issue but suddenly everything works now after doing what seemed like nothing special whatsoever.

[ipaqmaster]

A collection of things I tried which didn't seem to help:

1. Rolled back my rootfs (periodic zfs snapshots) back to 10PM last night where Steam was working and games were launchable
2. Ran rndc flush against the home router's named service to flush cached DNS entries immediately rather than waiting out their TTLs to void any potentially bad DNS records cached.
3. Restarted the router's named service too.
4. Tried a full system upgrade (reverted) in desperation
5. Opened up local firewall rules (iptables) temporarily in case Steam's websocketing may have been denied access (Seemingly not the problem)

I will refer back to this issue if I run into this problem again and potentially find an answer.

[ipaqmaster]

This issue passed a while ago but could be related to another problem I'm having (#3717)

Here's a gist from System Information today: https://gist.github.com/ipaqmaster/488b1d0c438c2a17c960e9100b12181d

I got Steam the Archlinux official multilib package repo with its package manager.

It appears as multilib/steam 1.0.0.79-2 [installed]

[lostgoat]

Can you also post the output of pstree while steam is running? I mostly want to see the steam process hierarchy.

[lostgoat]

@ipaqmaster The new steam beta has some extra debugging info around this failure. Can I trouble you to:

1. Start Steam
2. Wait 2 minutes
3. Collect ~/.steam/steam/logs/transport_steamui.txt
4. Also collect the output of pstree

[OdinVex]

How about native instead of CEF? >_> Edit: Halo MCC is a perfect example of unplayable. Steam_API calls were over 4000 (depot/dlc) for just 60 seconds of process time. One frame maybe every 30 seconds. I recall the log being absolutely filled with 'CEF is horrible, go back to native'-suggestions about it timing out.