Team Fortress 2 on the Steam Deck hangs connecting to a server and crashes, or relays "An Issue with your computer is blocking the VAC System."

[CorpseSea]

Hello, I've owned a Steam Deck for approximately 2 months now, and no matter what I've done has fixed this issue. Rarely I'll have no issues and can play a match, but for 9/10 attempts I will get the aforementioned issue.

Is there anyone else experiencing this, and have they been able to fix it?

[Midnoclose]

Try verifying your game files and then clearing your steam download cache if you can.

[CorpseSea]

Try verifying your game files and then clearing your steam download cache if you can.

Tried it, also followed mastercomfigs cleaninstall tutorial on how to completely nuke any settings i may have had, downloaded it in desktop mode too to see if it was just a game mode issue. Installed it on my SD, Internal, nothing. As a last ditch effort I completely reinstalled Steam OS and still, the issue persists.

[Heavy-WeaponsGuy]

bump

[billw1]

same issue :/

[TheMemeSniper]

same issue on EndeavourOS, only difference from the steamOS that would matter is i'm using the zen kernel

[Zeron100Z]

Same Issue on Pop!_OS, so it's not localized to arch based distros

[Ten0]

Same issue on NixOS. Would be nice if there was a way to get more logs than just this error message. Maybe related: https://github.com/ValveSoftware/Source-1-Games/issues/2825

[turboxgts]

Bumping, only seems to fix itself after an unreasonable amount of Steam Deck restarts

EDIT: Would also like to clarify this happens on community servers (which I exclusively play on)

[NULLYUKI]

Similar issue was reported in #4779 #2150 and #3617

[UnixTMDev]

Doesn't happen for me on Mint, i3wm, NVIDIA. Wonder what's causing this. (Sidenote: My Deck is doing this crap too)

[DavidRLTG]

Happens to me too, on Devuan Linux OpenRC.

[NULLYUKI]

Soon a x64 Linux update for Team Fortress 2 will be released, probably fixing this issue as well. https://steamdb.info/app/440/depots/

[Tiagoquix]

@kisak-valve Needs to be retested, should be somewhat fixed with the update to 64 bits. I assume this can be safely closed.

[d-k-bo-2]

After a long time of not having this issue, I had it multiple times today (using the 64 bit version).

[jr551]

I'm also getting

Disconnect: An issue with your computer is blocking the VAC system. You cannot play on secure servers.

Running Solus linux

[bigstiffy]

I am also facing this issue since the release of the x64 update. I get kicked from every server after approximately 15 minutes with the exact same error. Cannot rejoin server without relaunching the game. I haven't seen any errors logged when launching steam from terminal, there is nothing in TF2's console except the same message in the popup. Switching the steam runtime version does not help. Switching between the new launch option and the legacy opengl option does not help. Updating my OS did not help. Deleting TF2 configs, workshop content, and verifying integrity did not help. Removing launch options for TF2 did not help.

Running x86_64 gentoo linux kernel: 6.6.0 cpu: AMD Ryzen 7 3800x gpu: AMD Radeon RX 5600 XT llvm: 17.0.4 opengl driver: radeonsi kernel driver: amdgpu

[sumixodia]

same issue on Fedora 40. oddly worked fine a few days ago after deleting all files and reinstalling. after a reboot went back to booting me to the desktop every single time.

whenever I try to join a server the loading bar reaches about 60%, freezes the game, and then crashes. After attempting several times, I got the VAC message (Disconnect: An issue with your computer is blocking the VAC system. You cannot play on secure servers.)

OS: Fedora Linux 40 (Budgie) x86_64 Kernel: 6.8.9-300.fc40.x86_64 CPU: AMD FX-8350 8 cores 4.00ghz GPU: AMD Radeon RX 6600xt RAM: 23.43 WM: KWin DE: KDE Plasma 6.0.4

[zpatten]

Happening for me too. Pretty much zero information online about this other than lots of people running into it. Would be nice if we could get more specifics as to why this gets triggered. Having always played tf2 behind a firewall via NAT VAC has never had the ability to make a connection back to my computer so the error implies that someting is blocking an outbound connection. Outside of a temporary network issues there is nothing which would be doing this.

When dual booting, running on windows on the same system the error never occurs however in linux it does. Linux firewall is only blocking inbound network connections (exact same behaviour as in windows with it's firewall).

Could we at least get some detailed clarification as to what exactly triggers this state in the game? That would at least help with debugging since the error itself is vague and unhelpful as are the troubleshooting tips listed in the steam article it references (as they only really apply to windows and are very generic troubleshooting techniques which based on other posts online don't work or are irrelevant).

[nfox18212]

Experiencing this issue on Fedora 40 as well. No packages were changed as far as I can tell, and firewalld was not changed either. I was able to successfully play on 20204-07-29 without issue, and I rebooted since then. Today I attempt to play and it doesn't let me. I am using the 64-bit version.

OS: Fedora 40 Kernel: Linux 6.9.10-200.fc40.x86_64 CPU: AMD Ryzen 7 5800X (16) @ 3.80 GHz GPU: AMD Radeon PRO WX 3100 @ 1.22 GHz [Discrete] OpenGL Version: 4.6 (Compatibility Profile) Mesa 24.1.4

[NULLYUKI]

Replying to https://github.com/ValveSoftware/Source-1-Games/issues/4291#issuecomment-2263865649

Was by any chance your public IP changed over the night by your router?