24
Steam games with linux runtimes don't work (Mint) (lemmy.ca)
submitted 9 months ago by to c/linux_gaming@lemmy.ml
11 comments fedilink hide all child comments
 

Hi, I've got a weird issue and figured I'd see if anybody knows how to fix it. I've noticed that most of my steam games that have linux native support just crash immediately when I try to run them. Running with Proton works just fine, but I was wondering if my system might be missing something obvious I need to run linux native games?

The latest one I was trying to play was Pyre. I tried looking through the logs, but couldn't find anything obvious to me.

Edit: Whatever it is, it looks like its not something simple, but that is okay because everything seems to work fine with proton anyway. Thanks for the help anyway! :)

all 11 comments

sorted by: hot top controversial new old
[–] 9 points 9 months ago (4 children)

Try starting steam from the terminal. A lot of diagnostic info gets printed to stdout and stderr, which you can scroll through after a crash. Search up anything that looks like a serious error, it might point you in the right direction.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 5 points 9 months ago (3 children)

    Weirdly enough, it did work that time, but froze the game when I tried to exit. I tried another time and it didn't run the game and gave some errors like:

    [___](ERROR: ld.so: object '/REDACTED/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
)

    and

    Initializing steam
Setting breakpad minidump AppID = 462770
free(): invalid pointer

    and then a long stacktrace. No idea what it means.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 7 points 9 months ago

    The LD_PRELOAD one is actually harmless and annoyingly spams everyone. Steam tries to preload the 32 and 64 bit overlay library into every process and depends on one or the other failing.

    The free assert is bad and likely related to the crash. The stacktrace might be interesting if you want to share it.

    The only cause that comes to mind is something like a libc conflict between the game and your graphics driver. That's going to be annoying to diagnose/fix though.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 7 points 9 months ago (1 child)

    Switching to flatpak steam will often fix these weird steam problems.

    For actually troubleshooting it, I'm guessing you have an issue with your steam runtime for Linux games. Try running steam with the console command:

    STEAM_RUNTIME=0 steam

    and see if your games work. Basically by default Steam bundles it's own runtime packages to run Linux games with. Setting steam runtime to 0 as part of the launch will disable this functionality, and use your systems packages instead.

    Another thing you could try, you can open game properties and go to the compatibility section. There you can check "force compatibility layer" and try different steam Linux runtimes (if you have them installed).

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] 5 points 9 months ago

    Currently I prefer Windows versions of games. I understand the people who much rather have a native port, but I've come to view Windows (Wine, Proton) as the Linux Gaming API Layer. When you think of it like that, it doesn't really matter if the game has a native port or not.

    Last week I installed a game on Steam (can't remember the title, sorry) that had a Feral native port. It complained about my card not being supported and crashed. I then installed the Proton version and it simply worked.

    Even if there is a native port, it probably takes work to keep up with Linux rapidly evolving features than to keep it running on Windows relatively static APIs.

    So I thank Microsoft for the Linux Gaming API (and the intrepid Wine devs), I'm sure they didn't intend it to be this way but here we are.

  • permalink
  • fedilink
  • source
    •
    [–] 2 points 9 months ago (2 children)

    Fixed it on one buddie's computer, he installed the snap version. We fixed it by removing that one and installing Steam via apt. Which version do you have?

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •