Interestingly, in this section of the arch wiki, it does explicitly mention:
If using systemd-resolved for DNS, follow the steps to fix
/etc/resolv.confin order for Steam to be able to resolve hostnames.
I am pretty sure that the logs said that this was a problem with some steam component not being able to connect to the main steam via websocket or something, so it is definitely possible for the connection to have failed because of hostname resolution problems.
This would be something to check if you are someone from the future trying to troubleshoot a similar problem and are using systemd-resolved, unfortunately I didn't see this until I had already deleted and reinstalled arch 😭 (although truthfully, I don't know if I was using systemd-resolved). Steam works fine now (I am not using systemd-resolved now).
I will still leave the issue open just in case there was an issue internally with steam that was causing those issues, although if no one else speaks up with their own similar experience for a while, then the maintainers can feel free to close this issue.
Nothing extracted yet.
System Information
Please describe your issue in as much detail as possible:
At startup, and randomly while running Steam, the following dialog pops up:
This would seem very similar to #10879 but there is a twist: If I click "VO: Continue Anyway" the Steam client appears to work completely fine, there are no issues as far as I can tell. That is until the exact same dialog pops up again randomly, you have to keep clicking on continue anyway and its annoying.
The exact error code starts at 0x3008 or 0x3009, but then increases (usually by 8) every time I click continue anyway (so it goes to 0x3016 then 0x3024, etc).
I have checked my
/etc/hostsfile and I don't think there is anything weird in there but here it is anyway:Running
lsof -c steam | grep IPv4while it's running gives the following:Changing the grep to IPv6 gives no output.
Steps for reproducing this issue: