"VAC was unable to verify your game session" message for matchmaking.

[wallmenis]

Your system information

• System information from steam (Steam -> Help -> System Information) in a gist: https://gist.github.com/wallmenis/50e7369ac657b36178578bdb127a6613
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

I installed the game normally, used gamemoderun %command% -vulkan (also tried without) to search matchmaking for a deathmatch round. When I pressed play, the message shown in the attached screenshots popped up. I tried all versions of steam on Arch and flatpak. Nothing worked. The issue was happening only on matchmaking. I did try joining 3rd party VAC enabled servers and they let me join and play normaly.

Steps for reproducing this issue:

1. Install the game from library.
2. Open the game.
3. Select a matchmaking option.
4. Press "GO".

[Cloudperry]

I started getting this error as well around the time you created this bug report. This issue affects only the Vulkan renderer.

I can get it to work again by doing steam --reset, but at least adding gamescope to launch options seems to break it until I reset Steam again. Just removing gamescope from launch parameters somehow doesn't fix it.

[kirinpaul]

Hi! I'm having the same issue - trouble finding ranked games in CS:GO. Game session verification error. I don't have any third party software installed. My operating system is openSUSE Tumbleweed. Linux kernel 6.1.12-1. Nvidia drivers 525.89.02-5.2-x86_64 from the official Nvidia repository, steam client from openSUSE repository. I just installed the system, steam client and CS:GO and immediately got this error. I can't play due to this error for a long time. System information (https://gist.github.com/kirinpaul/5ee6292235f4ede3ee7fd76b1db83f31)

[kirinpaul]

@Cloudperry is probably right. Apparently the problem with the Vulkan API. Just not sure what exactly is the issue. In my case, the problem was solved by adding -gl_enablesamplerobjects parameter (use OpenGL Sampler Objects for better texture preloading) in launch options. Moreover, if this parameter is later removed from the launch options, the game will still successfully search for ranked games, at least for a while. This, of course, does not solve the root cause. Very strange. Hope this workaround helps someone.

One more gist: https://gist.github.com/kirinpaul/ecd2161658e9e86d2162bf2e84e938fb I have several errors when collecting video data in graphics-details. Could this be related to the root cause of the error?

[mdilai]

Have same issue tonight on Manjaro with Nvidia. But i am using OpenGL and already have "-gl_enablesamplerobjects" in my launch options. "steam --reset" and game reinstalling not helped as well. Last month everything worked fine. My HW info: https://gist.github.com/mdilai/e12fab166da95ace41b1abd93464cd1a

[mdilai]

Upd: Tested my account on Windows right now, everything was great, including green trust factor. Also tested fresh new account on my Manjaro setup, also great (but non-prime, obviously). But for some reason, my account on my Manjaro throw VAC error.

[HAV0X1014]

I'm having this issue when I am on openGL. I have not used Vulkan. Reinstalling the game didn't do anything to solve the issue.

[HAV0X1014]

issue seems to have fixed itself. No actions were taken on my behalf to solve the issue. I did play on some VAC protected community servers through the server browser for a while (about an hour or two max) during this time.

[kirinpaul]

I still have an issue.

[mdilai]

Can confirm that issue has solved for me. Still same setup without any changes. But i had sent a mail to CSGOTeamFeedback@valvesoftware.com about this problem, don't know if that helped

[NightProwler-dc]

Can confirm that issue has solved for me. Still same setup without any changes. But i had sent a mail to CSGOTeamFeedback@valvesoftware.com about this problem, don't know if that helped

How did you solve? What did you do to solve it? Send mail to CSGOTeamFeedback@valvesoftware.com? I'm having this problem too now. Also I notice that both native steam client and flatpak steam have this issue. Then on the same machine with windows (dual boot with linux) it works fine.

[Glubb]

I'm having the same issue, it only started after Tuesday's maintenance though

launch options: %command% -nojoy -novid -fullscreen -vulkan system information: https://gist.github.com/Glubb/8e214d6186b491122d19cde124ad7218

[Glubb]

problem fixed itself? cool. Though it looks like it is rebuilding the vulkan cache in-game, so that might give a hint

[mdilai]

Can confirm that issue has solved for me. Still same setup without any changes. But i had sent a mail to CSGOTeamFeedback@valvesoftware.com about this problem, don't know if that helped

How did you solve? What did you do to solve it? Send mail to CSGOTeamFeedback@valvesoftware.com?

I'm having this problem too now. Also I notice that both native steam client and flatpak steam have this issue. Then on the same machine with windows (dual boot with linux) it works fine.

Sent them screenshot of your VAC error message, your profile's URL, system information log from Steam and some summary about what you already tried. Then just wait. No need to change launch options, configs etc. - this is a pure placebo. VAC issue is somehow linked to your account, so don't forget to mention URL of your profile. Do not expect any answer from Valve, just send mail and relax for couple days, eventually it will fix itself.

[tmnvanderberg]

Seeing the same issue

[pranshuthegamer]

same issue observed on arch linux

▶ uname -a
Linux pranshu-arch 6.2.12-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Thu, 20 Apr 2023 16:11:27 +0000 x86_64 GNU/Linux

using nvidia/radeon with ryzen cpu on a laptop

[everlyy]

Same issue since yesterday on Debian testing.

[tmnvanderberg]

Magically solved itself for me.

[pranshuthegamer]

solved for me aswell

[Cheaterman]

Just broke out of nowhere for me

EDIT: Wait WHAT? And then fixed itself by starting twice in a random lobby with strangers, screenshot here:

[ipaqmaster]

This seems to happen without warning on my Archlinux system throughout the past month or so. Then the issue eventually goes away on its own hours later without any correlation of an outage or anything of the sort visible on steamstat.us.

Reboots and updates never resolve the problem. Desktop zpool has no corruption or checksum mismatches to report - so verifying game files can't be relevant.

I'm glad matchmaking has done this to me on the menu rather than in the middle of a competitive match this time. That was not a fun nor earned derank last month.

[ipaqmaster]

It seems the magic solution is to complain in the official issue threads. I am now suddenly able to queue and nothing has changed. I didn't even restart the game after the first restart and persisting VAC error.. now queuing is suddenly possible in the same csgo_linux64 session and I'm in a de_mirage match. 🤷 OK!

E:

I asked everyone on the server (10 players, MM, de_mirage) and one teammate said they also had VAC issues this past half hour. One enemy on T side also confirmed they had issues too. This seems to be a valve side problem and impacts more than just an individual at a time. At least tonight's particular variant.

Though, it's also possible they just lied.

[pranshuthegamer]

I am observing this issue as well right now

[Samueru-sama]

Having this issue right now on arch linux for the past 6 hours, I've tried everything, from checking integrity, reinstalling the game and steam, using the beta steam client, rebooting, clearing everything steam related from the home folder, reset internet, etc, etc.

[tonikelope]

Same here from Archlinux. Yesterday it was working.

Edit: now its working.

[Samueru-sama]

Having this issue right now on arch linux for the past 6 hours, I've tried everything, from checking integrity, reinstalling the game and steam, using the beta steam client, rebooting, clearing everything steam related from the home folder, reset internet, etc, etc.

The issue just fixed on its own. 5 days it took!

[pappacena]

I have the same issue. It has been like this for a week or so!

[tonikelope]

Since yesterday it has been happening again.

VAC status: no ban. File integrity: OK

Mistery.

[d3ads1lence]

I've been having the same problem since Tuesday.....

[Ultan-Kearns]

Turning off proton in compatibility settings fixed it for me

[pranshuthegamer]

my proton is alr off

[berysaidi]

does anyone know how to fix this?

[ipaqmaster]

If you're using proton it won't work. Otherwise, if the history of this thread is anything to go by; this is a transient error and it goes away on its own without you having to do anything. If it came up out of nowhere it goes away in about 30 minutes without having to do anything.

It may or may not be something on Valve's side but it just goes away. There are thousands of different "solutions" all over internet results because that's just what people try before the issue goes away on its own. Only in a few special circumstances is action actually required. But if it just came up out of nowhere for your with no updates or other system changes. Its probably already done.