This may not be a Linux specific problem as I had the exact same issue earlier with Windows 7 and it’s one of the reasons I installed Linux in the first place.

The specific game I’m trying to play is DayZ but it may not be issue specific to this game. It worked flawlessly untill this point. I had made no changes to anything. Basically when I try to launch the game it starts loading up normally and then just apparently quits and the “Play” button goes back green. No error, no black screen, no freezing or anything. It just stops launching the game.

I’ve tried checking the integrity of files, deleting downloads catche, disabling steam cloud, removing launch options… nothing. Almost like it gets blocked by firewall or something. However I feel like it may be an issue with steam itself or then it’s a hardware issue (I’ve got really old PC)

Few things I’ve noticed that may or may not be related:

  • When opening up steam it almost always used to download some updates first and check the integrity of them or something. Now it doesn’t. It just opens up Steam. When I click “check for updates” it says everything is up to date.

  • The firmware updater shows available updates for my SSD and HDD but no option to update. I also tried with sudo fwupdmgr get-devices but it says “UEFI firmware can not be updated in legacy BIOS mode See https://github.com/fwupd/fwupd/wiki/PluginFlag:legacy-bios for more information.”

  • In the privacy settings it says “checks failed” and gives me this message:

  • I’ve tried reinstalling Proton BattlEye Runtime but it wont let me uninstall it and says “missing shared content”
  • version_unsorted@lemmy.ml
    link
    fedilink
    arrow-up
    8
    ·
    10 months ago

    Usually I start debugging this type of thing by killing all instances of steam and then launching it from command line. Steam logs a bunch of good stuff and putting it in context of your interactions helps. That said, based on what you’ve described, I would try older versions of proton, targeting releases back when games were launching. Proton/wine versions don’t always work for all games and sometimes you’ll need to launch particular titles with specific versions. Proton has been absolutely revolutionary, but these issues still pop up. ProtonDB might have reports on specific versions for specific games/titles.

      • lemmyvore@feddit.nl
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 months ago

        You can also try starting a Linux game, if you have any, just to figure out if Proton is the issue.

      • Critical_Insight@feddit.ukOP
        link
        fedilink
        arrow-up
        2
        ·
        10 months ago

        Yeah I followed the instructions there and it worked without an issue for several weeks and then just stopped working.

    • Critical_Insight@feddit.ukOP
      link
      fedilink
      arrow-up
      1
      arrow-down
      3
      ·
      10 months ago

      But what’s strange is that it worked with proton experimental untill this point and that I had this exact same issue earlier on Windows 7 aswell on this same PC. I however did try using proton 8 but that made no difference. I need to try those other versions too

      • Dremor@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        10 months ago

        Proton experimental moves quite a lot. Maybe they moved to a new version of something that broke your install for a reason or another.