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-devicesbut 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"
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- the221100is the app ID of of DayZ on the steam store. After backing it up, delete the original221100directory 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
221100directory 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?
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:
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:
and
You've got permission errors and a GPU driver issue somewhere, likely related to the permission errors. The
flockerrors stand out to me also, as they are fonts. Maybe required fonts for the game to run?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.
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
~~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