Cannot start steam, "Steamwebhelper is not responding" dialog appears consistently

[Schuldkroete]

Your system information

• Steam client version (build number or date): Mar 6 2024 (pacman packet version 1.0.0.78-2)
• Distribution (e.g. Ubuntu): Artix Linux
• Opted into Steam client beta?: No
• Have you checked for system updates?: Yes
• Steam Logs: steam-logs.tar.gz
• GPU: AMD Radeon RX 6900 XT

Please describe your issue in as much detail as possible:

Steam worked flawlessly until roughly the start of this month.
Since then, when launching steam (steam-runtime or steam), only the dialog window "Steamwebhelper is not responding" appears. (none of the options in the dialog help)
After reading through a lot of similar Issues I tried deleting ~/.steam and ~/.local/share/Steam (except for the ~/.steam/steam/steamapps/common and ~/.steam/steam/steamapps/compatdata folder) but this did not resolve the problem.

Steps for reproducing this issue:

1. Start steam
2. "Steamwebhelper is not responding" dialog appears

[smcv]

I think the relevant error message here is:

[0325/105134.224938:ERROR:directory_reader_posix.cc(42)] opendir /tmp/dumps/attachments/6444653e-e946-4fd0-b1f5-e21f6f1c7298: No such file or directory (2)

This looks a bit like #10549. Check that /tmp/dumps is either owned by your user ID or deleted.

If you are running Steam on a multi-user system, each user will need to delete /tmp/dumps before the other user can run Steam successfully.

[Schuldkroete]

I tried both deleting the /tmp/dumps folder and changing the permissions to 777 recursively (it was already owned by my user), and neither option changed the outcome.
This was also one of the things I tried before. (I forgot to list it in the Issue)

[ipr]

This is duplicate of #10577 I think.

[smcv]

This is duplicate of #10577 I think.

The symptom is the same, but there is not enough information available to the public to know whether the root cause is the same. steamwebhelper developers might be able to get more information from any crash dumps that are uploaded (but coming from the Steam Runtime side, I don't have access to those).

Mixing up more than one root cause with similar symptoms in the same issue report tends to lead to long, confusing issue reports where it's never clear whether the issue is fully fixed or not, so it might be better to keep separate issue reports separate.