You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My system:
Linux Mint 21.3 Cinnamon
GeForce GTX 1060 3GB
nvidia-driver 535
Please describe your issue in as much detail as possible:
Since an update in early June CS2 refuses to launch: it freezes at valve-logo screen and does not launch further. -sw and other options do not help. Also different (up- and downgraded) nvidia-drivers brought no change, neither helped re-installation of the game and of the steam client (deb-version).
I run a native linux version via steam but if I activate Proton 9 or experimental, the game starts normally but I can not join servers due to VAC (unfortunately this is normal with proton). Launching cs2.sh via terminal does not reveal any obvious errors: the script simply hangs forever after the line "Loaded libmpg123.so.0, got 0x578e8a758160". Has anyone a suggestion except waiting for mint 22 and hoping it works then?
Steps for reproducing this issue:
Open steam client
Launch the game
The text was updated successfully, but these errors were encountered:
Your system information
My system:
Linux Mint 21.3 Cinnamon
GeForce GTX 1060 3GB
nvidia-driver 535
Please describe your issue in as much detail as possible:
Since an update in early June CS2 refuses to launch: it freezes at valve-logo screen and does not launch further. -sw and other options do not help. Also different (up- and downgraded) nvidia-drivers brought no change, neither helped re-installation of the game and of the steam client (deb-version).
I run a native linux version via steam but if I activate Proton 9 or experimental, the game starts normally but I can not join servers due to VAC (unfortunately this is normal with proton). Launching cs2.sh via terminal does not reveal any obvious errors: the script simply hangs forever after the line "Loaded libmpg123.so.0, got 0x578e8a758160". Has anyone a suggestion except waiting for mint 22 and hoping it works then?
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: