ValveSoftware / csgo-osx-linux

Counter-Strike: Global Offensive
http://counter-strike.net
784 stars 69 forks source link

Cs2 won't start #3516

Open samscalet opened 1 year ago

samscalet commented 1 year ago

Your system information gist:

pid 30029 != 30028, skipping destruction (fork without exec?) pid 30030 != 30028, skipping destruction (fork without exec?) Loaded /home/samx/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/bin/linuxsteamrt64/libengine2.so, got 0x558ae91c78d0 Using breakpad crash handler [S_API] SteamAPI_Init(): Loaded '/home/samx/.local/share/Steam/linux64/steamclient.so' OK. Setting breakpad minidump AppID = 730 Forcing breakpad minidump interfaces to load Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit 10/24 19:15:05 Init: Installing breakpad exception handler for appid(730)/version(8432264)/tid(30032) Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit

Setting breakpad minidump AppID = 2347771 Loaded libSDL3.so.0, got 0x558ae9469c10 Loaded /home/samx/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/bin/linuxsteamrt64/libtier0.so, got 0x558ae91b1880 Loaded /home/samx/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/bin/linuxsteamrt64/libfilesystem_stdio.so, got 0x558ae94badb0 Loaded /home/samx/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/bin/linuxsteamrt64/libinputsystem.so, got 0x558ae94bb700 Loaded /home/samx/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/bin/linuxsteamrt64/liblocalize.so, got 0x558ae94bbce0 Loaded /home/samx/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/bin/linuxsteamrt64/librendersystemvulkan.so, got 0x558ae94bc6b0 Loaded /home/samx/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/bin/linuxsteamrt64/libresourcesystem.so, got 0x558ae9522bc0 Loaded /home/samx/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/bin/linuxsteamrt64/libschemasystem.so, got 0x558ae9535080 Fossilize INFO: Overriding serialization path: "/home/samx/.local/share/Steam/steamapps/shadercache/730/fozpipelinesv6/steamapprun_pipeline_cache". crash_20231024191505_2.dmp[30056]: Uploading dump (out-of-process) /tmp/dumps/crash_20231024191505_2.dmp /home/samx/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/cs2.sh: line 118: 30032 Segmentation fault (core dumped) ${STEAM_RUNTIME_PREFIX} ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@" crash_20231024191505_2.dmp[30056]: Finished uploading minidump (out-of-process): success = yes crash_20231024191505_2.dmp[30056]: response: Discarded=1 crash_20231024191505_2.dmp[30056]: file ''/tmp/dumps/crash_20231024191505_2.dmp'', upload yes: ''Discarded=1'' pid 30056 != 30055, skipping destruction (fork without exec?) Game 730 created interface STEAMAPPLIST_INTERFACE_VERSION001 / Game 730 created interface STEAMAPPS_INTERFACE_VERSION008 / Game 730 created interface STEAMHTMLSURFACE_INTERFACE_VERSION_005 / Game 730 created interface STEAMHTTP_INTERFACE_VERSION003 / Game 730 created interface STEAMINVENTORY_INTERFACE_V003 / Game 730 created interface STEAMMUSICREMOTE_INTERFACE_VERSION001 / Game 730 created interface STEAMMUSIC_INTERFACE_VERSION001 / Game 730 created interface STEAMPARENTALSETTINGS_INTERFACE_VERSION001 / Game 730 created interface STEAMREMOTESTORAGE_INTERFACE_VERSION016 / Game 730 created interface STEAMSCREENSHOTS_INTERFACE_VERSION003 / Game 730 created interface STEAMUGC_INTERFACE_VERSION018 / Game 730 created interface STEAMUSERSTATS_INTERFACE_VERSION012 / Game 730 created interface STEAMVIDEO_INTERFACE_V003 / Game 730 created interface SteamController008 / Game 730 created interface SteamFriends017 / Game 730 created interface SteamInput006 / Game 730 created interface SteamMatchGameSearch001 / Game 730 created interface SteamMatchMaking009 / Game 730 created interface SteamMatchMakingServers002 / Game 730 created interface SteamNetworking006 / Game 730 created interface SteamUser023 / Game 730 created interface SteamUser023 / User Game 730 created interface SteamUtils010 / Game 730 method call count for IClientUtils::RecordSteamInterfaceCreation : 24 Game 730 method call count for IClientUtils::InitFilterText : 1 Game 730 method call count for IClientUtils::IsSteamChina : 1 Game 730 method call count for IClientUtils::GetLauncherType : 1 Game 730 method call count for IClientUtils::GetAppID : 27 Game 730 method call count for IClientUtils::GetIPCountry : 1 Game 730 method call count for IClientFriends::GetFriendPersonaName_Public : 2 Game 730 method call count for IClientUser::GetUserDataFolder : 1 Game 730 method call count for IClientUser::GetSteamID : 6 Uploaded AppInterfaceStats to Steam

Steps for reproducing this issue:

  1. Launch the game and make some breakfast
  2. Game won't run
  3. Me not happy and running fast as i can with my dog like no tomorrow
  4. Have been 3 month i'm trying to get some fun with new CS2 game without luck
  5. Please solve this error ASAP!
  6. i mean its freaking update everyday!!
alioguzhan commented 1 year ago

For future readers:

I had the same issue for the last 2 days. I checked the logs and saw that it was the Mangohud that caused the crash, not CS. I removed the Mangohud from the startup command and it started to work again. Those other bugs still remain but it is playable at least.

limitedAtonement commented 1 year ago

@alioguzhan Where are the logs, my friend?

alioguzhan commented 1 year ago

Hey @limitedAtonement, you are right I should have shared the logs. But the issue is still open on the MangoHud side:

https://github.com/flightlessmango/MangoHud/issues/1139

I had the same error in my logs. It might be irrelevant to this, but I shared it just in case someone uses MangoHud and thinks the error is caused by CS 2.

limitedAtonement commented 1 year ago

I actually don't care what your logs say, I want to know where to find logs for my own sake ;-)

alioguzhan commented 12 months ago

Ah :)

  1. Open CS2
  2. Wait for the crash.
  3. Then, from terminal, run journalctl -r
  4. You should see the error logs.

PS: -r argument will reverse the sorting so you will see the latest errors on the top of screen. @limitedAtonement