protonscr

0x30XX error occurring at startup and randomly when running Steam

steamopen Distro Family: Arch
ValveSoftware/steam-for-linux#13256 · opened 2026-05-24 by agokule · updated 2026-05-28 · 1 comments · github
Aagokule 2026-05-24 github

System Information

Please describe your issue in as much detail as possible:

At startup, and randomly while running Steam, the following dialog pops up:

Image

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/hosts file and I don't think there is anything weird in there but here it is anyway:

# Static table lookup for hostnames.
# See hosts(5) for details.
127.0.0.1        localhost
::1              localhost

Running lsof -c steam | grep IPv4 while it's running gives the following:

steam     36941 atharv  40u     IPv4            1390965       0t0     TCP localhost:57343 (LISTEN)
steam     36941 atharv  45u     IPv4            1382278       0t0     TCP localhost:45417 (LISTEN)
steam     36941 atharv  88u     IPv4            1368787       0t0     TCP localhost:27060 (LISTEN)
steam     36941 atharv  90u     IPv4            1384261       0t0     TCP localhost:57343->archlinux:48748 (ESTABLISHED)
steam     36941 atharv  97u     IPv4            1384165       0t0     TCP localhost:42163 (LISTEN)
steam     36941 atharv 120u     IPv4            1364870       0t0     TCP archlinux:50509->162-254-193-75.valve.net:27018 (ESTABLISHED)
steam     36941 atharv 123u     IPv4            1364876       0t0     UDP *:27036 
steam     36941 atharv 125u     IPv4            1364877       0t0     TCP *:27036 (LISTEN)
steamwebh 37168 atharv 102u     IPv4            1392063       0t0     TCP localhost:48748->localhost:57343 (ESTABLISHED)
steamwebh 37168 atharv 167u     IPv4            1384277       0t0     UDP mdns.mcast.net:mdns 
steamwebh 37258 atharv  28u     IPv4            1403339       0t0     TCP archlinux:37462->a23-54-41-174.deploy.static.akamaitechnologies.com:https (ESTABLISHED)
steamwebh 37258 atharv  32u     IPv4            1403343       0t0     TCP archlinux:caerpc->151.101.127.52:https (ESTABLISHED)
steamwebh 37258 atharv  33u     IPv4            1390219       0t0     TCP archlinux:37476->a23-54-41-174.deploy.static.akamaitechnologies.com:https (ESTABLISHED)
steamwebh 37258 atharv  35u     IPv4            1403347       0t0     TCP archlinux:50796->a23-223-170-105.deploy.static.akamaitechnologies.com:https (ESTABLISHED)
steamwebh 37258 atharv  38u     IPv4            1364983       0t0     TCP archlinux:42516->151.101.127.52:https (ESTABLISHED)
steamwebh 37258 atharv  39u     IPv4            1403369       0t0     TCP archlinux:50800->a23-223-170-105.deploy.static.akamaitechnologies.com:https (ESTABLISHED)
steamwebh 37258 atharv  40u     IPv4            1403365       0t0     TCP archlinux:42524->151.101.127.52:https (ESTABLISHED)

Changing the grep to IPv6 gives no output.

Steps for reproducing this issue:

  1. Run Steam
  2. Click on "VO: Continue Anyway"
  3. Eventually the dialog will show up again.
  4. You can keep pressing continue anyway indefinitely, hitting restart Steam does not solve the issue.
Aagokule 2026-05-28 github

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.conf in 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.