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:

  • BCsven@lemmy.ca
    0·
    10 months ago

    Maybe a change in thr game patches or steam updates altered Proton behaviour, have you tried a different Proton version?

    • Critical_Insight@feddit.ukOP
      0·
      10 months ago

      Yeah I tried proton 8 and 7 too and no difference. I had this exact same issue in win7 too before I switced to Linux so I don’t think it’s an issue with proton.

  • hollyberries@programming.dev
    0·
    10 months ago

    I don’t have any idea about your hardware issues. They’re likely unrelated if the game has already been played without issue.

    For the steam diagnosing, start with running steam from your terminal, by running steam. You may get lucky and the error is clearly identified in the console.

    If that fails, backup $HOME/.local/share/Steam/steamapps/compatdata/221100 - the 221100 is the app ID of of DayZ on the steam store. After backing it up, delete the original 221100 directory and re-launch the game. This doesn’t delete the game, but rather deletes the Proton prefix for the game.

    If the game launches, copy any save files (if any) you may have in the backed-up 221100 directory over to the new one.

    The above worked for me when I had similar issues when playing Batman: Arkham Asylum.

    To be thorough, have you tried any other games to rule out your hardware being an issue?

    • Critical_Insight@feddit.ukOP
      0·
      10 months ago

      I installed DayZ Experimental and I have the same issue with that. I haven’t tried with other games as I have none installed.

      Trying to run steam via terminal gives me this wall of text:

      
(process:18363): GLib-GIO-CRITICAL **: g_settings_schema_source_lookup: assertion `source != NULL' failed
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xf6b24370
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xf6b22cc0
steamwebhelper.sh[18409]: Runtime for steamwebhelper: defaulting to /home/pokko/snap/steam/common/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
/home/pokko/snap/steam/common/.local/share/Steam/ubuntu12_64/steamwebhelper.sh: line 53: /proc/sys/kernel/unprivileged_userns_clone: Permission denied
/home/pokko/snap/steam/common/.local/share/Steam/ubuntu12_64/steamwebhelper.sh: line 60: /proc/sys/user/max_user_namespaces: Permission denied
steamwebhelper.sh[18409]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()
steamwebhelper.sh[18409]: CEF sandbox already disabled
flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13flock /usr/share/fonts/truetype/liberation/LiberationSans-Bold.ttf LOCK_SH failed. errno = 13CAppInfoCacheReadFromDiskThread took 44 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 18505
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13vkEnumeratePhysicalDevices failed, unable to init and enumerate GPUs with Vulkan.
BInit - Unable to initialize Vulkan!
BRefreshApplicationsInLibrary 1: 0ms

(steam:18363): GLib-GIO-CRITICAL **: g_settings_schema_source_lookup: assertion `source != NULL' failed
flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13BuildCompleteAppOverviewChange: 183 apps
RegisterForAppOverview 1: 18ms
RegisterForAppOverview 2: 18ms

(steam:18363): GLib-GIO-CRITICAL **: g_settings_schema_source_lookup: assertion `source != NULL' failed
      • hollyberries@programming.dev
        0·
        10 months ago

        Oh damn, you’re using the snap version of Steam, this is unfortunately outside of my area of experience :(

        Some key error messages I see are:

        /home/pokko/snap/steam/common/.local/share/Steam/ubuntu12_64/steamwebhelper.sh: line 53: /proc/sys/kernel/unprivileged_userns_clone: Permission denied
/home/pokko/snap/steam/common/.local/share/Steam/ubuntu12_64/steamwebhelper.sh: line 60: /proc/sys/user/max_user_namespaces: Permission denied

        and

        flock /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf LOCK_SH failed. errno = 13vkEnumeratePhysicalDevices failed, unable to init and enumerate GPUs with Vulkan.
BInit - Unable to initialize Vulkan!

        You’ve got permission errors and a GPU driver issue somewhere, likely related to the permission errors. The flock errors stand out to me also, as they are fonts. Maybe required fonts for the game to run?

        • Critical_Insight@feddit.ukOP
          0·
          10 months ago

          I’ve been using Linux for only a couple of weeks and all this is complete hebrew to me. I have no clue what is snap version of steam.

          • Yuumi@lemmy.worldEnglish
            0·
            10 months ago

            I’m not trying to steal hollyberry’s job here but here is my understanding of snaps (and why they aren’t good).

            Snaps were created by Canonical (The company behind Ubuntu) to fix the issue of inconsistent dependencies. The problem with the format is that the market is proprietary and they just aren’t very good. Also they perform somewhat worse than Appimages and Flatpak.

            Personally I reccomend you look into Flatpak, as it’s a better sandboxing format than snap is.

            Also the reason you ended up with the SNAP version of steam is because Ubuntu prioritizes the snap version over the native version when using

            apt install steam
            • itslilith@lemmy.blahaj.zone
              0·
              10 months ago

              the last part is not true, apt installs things natively. Ubuntu software (the graphical app store) uses snap, however

              I stand corrected. The apt packages on Ubuntu sometimes just install snaps under the hood. really strange move by Canonical

          • hollyberries@programming.dev
            0·
            10 months ago

            Thankfully someone stepped in about snap… I don’t like it and would have gone on a rant without circling back to the issue on hand lmao

            As recommended somewhere up the chain, try a different version of Proton. Support for your hardware may have been deprecated.

            From here, I’m out of my element. Best of luck, sorry I couldn’t have been of more help!

    • Critical_Insight@feddit.ukOP
      0·
      10 months ago

      Interestingly that file doesn’t seem to be located in the location you mentioned but rather: home/snap/steam/common/.steam/steamapps/steam/comptdata

      There is no steam folder at “share”

      I’ll try deleting that anyways. I’ll report back in a moment

      EDIT: Nope, nothing.

  • Doods@infosec.pub
    0·
    10 months ago

    You press play and it goes off after a while, you have problems with vulkan, you have an old PC.

    I had this exact issue before, try tuning an older version of proton, as newer versions require more recent vulkan versions, which your PC most likely doesn’t support.

    steam auto updates to the latest proton version usually, that’s probably why.

    • Critical_Insight@feddit.ukOP
      0·
      10 months ago

      I did get the “Processing vulcan shaders” pop-up sometimes when I opened the game (back when it was still working) So I should not be using the Proton experimental? It worked just fine untill now. That’s what’s so strange about it. I do have an old PC but my GPU is brand new though.

      I’m trying to re-install steam right now but it’s been uninstalling it for about an hour and doesn’t seem to be progressing anywhere…

      • Doods@infosec.pub
        0·
        10 months ago

        1 - Proton experimental is a moving target and is rapidly evolving.

        2 - What exactly is your GPU, and maybe tell us your pc specs (even if it’s just through the info tab in the settings menu) (also put it in your post for others)

        3 - that sometimes happens to me when using gnome-software (which Ubuntu uses? or something really similar?), I usually just surrender and use the terminal, not like I install more than 1 thing in a normal month anyway.

        4 - if the issue is with proton, then other games wouldn’t work. (try running a very light, single player game to test proton, many F2P games under 20 mbs exist on Steam)

  • nous@programming.devEnglish
    0·
    10 months ago

    Have you tried updating and rebooting your system? I have had this happen a few times and almost always that is what fixes it for me (more so the rebooting but it is generally good to have your system up to date). Other times it is typically something missing on your host system (like properly installed drivers), though if the game was running before then this is less likely to be the issue and a reboot is typically enough - so start with that.

    • Critical_Insight@feddit.ukOP
      0·
      10 months ago

      I have checked all drivers, atleast I think I have, and have rebooted the system many times. Even took off the power cord for a minute

  • Guenther_Amanita@feddit.de
    0·
    10 months ago

    First - post upvoted because of the detailled report. Helpful. Thanks!

    I’ve had the same problem a longer while ago.

    Do you really have this few games in your library? I haven’t used the normal Steam mode for a while, but on your game list is a small Penguin. I believe that’s due to the filter “show Linux native only”.
    If you forgot to activate Proton, go into the Steam settings, gameplay and hit the checkbox “Compatibility for other games”. Use that all the time, even for Linux native games. They are usually way buggier than the Windows version, and Proton works great today.

    Second, if you are already using Proton and my first guess is wrong, use another Proton version. Either the most recent one (proton-experimental), an older one or the “proton-GE” versions.

    What distro are you using?

    Did you try using Flatpak instead of the native package? Maybe, there’s something missing in the native app.

    Oh, and I also wouldn’t worry much about the firmware errors and such. This panel is very new and some things are basically impossible to archive. But don’t trust my statement, maybe I’m wrong.

    • Critical_Insight@feddit.ukOP
      0·
      10 months ago

      Do you really have this few games in your library?

      Yes. I don’t play anything else except DayZ currently.

      Second, if you are already using Proton and my first guess is wrong, use another Proton version.

      Yeah I had all this enabled. The game worked perfectly before and then just all of a sudden stopped launching. I tired Proton 8 and 7 aswell but no difference.

      What distro are you using?

      Ubuntu

      Did you try using Flatpak instead of the native package?

      I was using the snap version of Steam that I had installed from Ubuntu App Store. I uninstalled it and installed the native version using terminal. Obviously I had to re-download and re-install the game aswell and it started working again after that. I’m not entirely sure what was causing the issue in the first place but I’m suspecting it was an issue in the steam app itself. What is curious though is that the exactly same issue occured to me previously with Windows 7 aswell and judging by the reports online, I’m not the only one.

      The problem is however solved - atleast for now, and that’s the most important thing. Thanks for the help though! The assistance I got from this community is invaluable. I’d be completely stuck with this on my own.

      • Guenther_Amanita@feddit.de
        0·
        10 months ago

        Yes. I don’t play anything else except DayZ currently.

        Sorry! Just in case this came out rude or judgy. It’s just a bit rare that ones’ library is so empty. It was just a thought because mine looks similar when I don’t activate Proton.

        I was using the snap version of Steam that I had installed from Ubuntu App Store.

        Aaah, yes. Just what I’ve thought. There are reasons why Snaps are hated this much in the Linux community.

        I personally recommend Flatpaks for everything, especially proprietary software like Steam. With the permission management, it has way less access to your device.
        Also, they usually “just work” better, because they provide themselves with all they need and can be improved by everyone, not just the devs of Ubuntu.

        With native apps you can get a few problems. In the best case, they’re just not as spread and bugs may occour more often. Flatpaks are more reproducible and bugs are fixed universally, no matter what distro.
        They’re more up to date too.
        And, they don’t come with dependencies. There was this one case, when a popular YouTuber accidentally deleted his whole user interface because he tried to uninstall Steam. That won’t happen with Flatpaks.

        Thanks for the help though! The assistance I got from this community is invaluable. I’d be completely stuck with this on my own.

        Of course, you’re welcome! Glad to help!

        I think it’s something of a generational contract. I got help a few years ago, when I was a noob, and now I’m more experienced and try to help as many newcomers as I can. And you will do the same in 3 years hopefully! 😁

  • version_unsorted@lemmy.ml
    0·
    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.nlEnglish
        0·
        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
        0·
        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
      0·
      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