Hi All,

Been bashing my head against this one, rebuild my OS yesterday, running linux mint and reinstalled steam, but can’t get anything to run on a proton version higher than 5 - i’m sure i’m missing something but don’t know what.

Any suggestions would be appreciated.

OS: Linux Mint 21.2 x86_64 Kernel: 6.2.0-31-generic CPU: AMD Ryzen 7 3800XT GPU: AMD ATI Radeon RX 5500/5500M

  • @PheonixtailOP
    link
    English
    141 year ago

    Ok so I’ve fixed it, appears to have been an issue with the tool having come from my backup rather than installed directly.

    couldn’t uninstall due to “missing shared content” so i deleted the file and verified integrity so it downloaded them - everything is now running perfectly, tried a few different games and they are working great.

    cheers for all the help!

    • @FinalBoy1975
      link
      English
      61 year ago

      but that’s awesome you figured it out and shared the solution here. There’s nothing about this out there that is searchable. Thanks for the learning lesson!

    • @[email protected]
      link
      fedilink
      English
      21 year ago

      I just started a foray into Linux gaming with Mint, as well, and had similar problems. I’ll be looking back at this to see if I can get it working.

  • ono
    link
    fedilink
    English
    5
    edit-2
    1 year ago

    Somewhere late in the Proton 5.x cycle (I think it was 5.13) Valve introduced Steam Runtime version 2: Soldier, which uses bubblewrap containers to solve various problems with host system libraries, but also broke some things. For example, it wants a newish version of bwrap and no longer works inside most other containers (except for Flatpak, which added special functionality to accommodate it).

    If you’re not using your own containers, I imagine upgrading to a recent version of Linux Mint might help, by giving you a newer version of bubblewrap, and/or enabling user namespaces (which bwrap uses) if they weren’t already enabled.

    Alternatively, if you’re comfortable running code from Flathub, you might consider using the Steam flatpak instead of your distro’s native package.

    Once upon a time, Flathub also had community-built versions of Proton that were stripped of their container functionality. I don’t know if those are still maintained.

  • @FinalBoy1975
    link
    English
    31 year ago

    If you could show an error message in the terminal either I or another person could help you. I’m guessing you’ve already searched the internet for a solution since you went through the painful process of re-installing the whole nine. What a marathon you’re running! Anyway, to run steam game in the terminal, you have to know the game id, which is a long number. If I’m correct (someone, if this is wrong, please correct me!), you would type something like this in the terminal: steam steam://rungameid/{YourGameID}

    • @PheonixtailOP
      link
      English
      31 year ago

      steam steam://rungameid/6060 steam.sh[7146]: Running Steam on linuxmint 21.2 64-bit steam.sh[7146]: STEAM_RUNTIME is enabled automatically setup.sh[7263]: Steam runtime environment up-to-date! steam.sh[7146]: Steam client’s requirements are satisfied [2023-09-02 19:26:36] Startup - updater built Jul 28 2023 18:44:09 [2023-09-02 19:26:36] Startup - Steam Client launched with: ‘/home/lewis/.steam/debian-installation/ubuntu12_32/steam’ ‘steam://rungameid/6060’ 09/02 19:26:36 Init: Installing breakpad exception handler for appid(steam)/version(1690583737)/tid(7342) [2023-09-02 19:26:36] Loading cached metrics from disk (/home/lewis/.steam/debian-installation/package/steam_client_metrics.bin) [2023-09-02 19:26:36] Using the following download hosts for Public, Realm steamglobal [2023-09-02 19:26:36] 1. https://client-update.akamai.steamstatic.com, /, Realm ‘steamglobal’, weight was 1000, source = ‘update_hosts_cached.vdf’ [2023-09-02 19:26:36] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm ‘steamglobal’, weight was 1, source = ‘update_hosts_cached.vdf’ [2023-09-02 19:26:36] 3. https://cdn.steamstatic.com, /client/, Realm ‘steamglobal’, weight was 1, source = ‘baked in’ [2023-09-02 19:26:36] Verifying installation… [2023-09-02 19:26:36] Verification complete XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe80eb9c0 XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe80ea1f0 /usr/share/themes/Mint-Y-Teal/gtk-2.0/main.rc:1053: error: unexpected identifier ‘direction’, expected character ‘}’ GetWin32Stats: display was not open yet, good GetWin32Stats: display was not open yet, good steamwebhelper.sh[7368]: Runtime for steamwebhelper: defaulting to /home/lewis/.steam/debian-installation/ubuntu12_64/steam-runtime-heavy steamwebhelper.sh[7368]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3() CAppInfoCacheReadFromDiskThread took 112 milliseconds to initialize BRefreshApplicationsInLibrary 1: 69ms BuildCompleteAppOverviewChange: 571 apps RegisterForAppOverview 1: 19ms RegisterForAppOverview 2: 20ms /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point: 285: exec: /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/run: Permission denied /bin/sh\0-c\0/home/lewis/.steam/debian-installation/ubuntu12_32/reaper SteamLaunch AppId=6060 – /home/lewis/.steam/debian-installation/ubuntu12_32/steam-launch-wrapper – ‘/home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper’/_v2-entry-point --verb=waitforexitandrun – ‘/home/lewis/.steam/debian-installation/compatibilitytools.d/GE-Proton8-14’/proton waitforexitandrun ‘/home/lewis/.steam/debian-installation/steamapps/common/Star Wars Battlefront II Classic/GameData/BattlefrontII.exe’\0 chdir “/home/lewis/.steam/debian-installation/steamapps/common/Star Wars Battlefront II Classic/GameData” ERROR: ld.so: object ‘/home/lewis/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object ‘/home/lewis/.steam/debian-installation/ubuntu12_64/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. ERROR: ld.so: object ‘/home/lewis/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object ‘/home/lewis/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object ‘/home/lewis/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so’ from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point: 285: exec: /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/run: Permission denied Uploaded AppInterfaceStats to Steam

      Hadn’t thought of doing it that way, looks like a permissions error (which makes little sense to me tbh

      • @FinalBoy1975
        link
        English
        31 year ago

        Yeah, the glaring “permissions denied” is right smack in the middle of all that. Then it just continues like that to the very end. One thing that makes no sense to me: manually changing the permissions on every single game. I’m a basic Linux boy and I do basic things, so don’t do what I’d do. What I’d try doing: changing the permissions in the .steam folder to the correct permissions, applying them to all the enclosed files and folders. I’d even have the stones to do it in the graphical UI left clicking on the .steam folder out of sheer basic laziness. My solution is totally basic and dumb, because it does not foresee new games being acquired through steam, which could revert back to the erroneous permissions. I searched for the error message to see what is relevant, nobody is reporting this problem, so, you’re unique. What a way to feel special, right? I’ll keep looking shit up like you’re doing. While we’re busy with that, someone more competent will come to your rescue, for sure.

        • @Falmarri
          link
          English
          31 year ago

          It’s possible they installed with sudo or something, which ruined the permissions. First try find /home/lewis/.steam ! -user lewis. That will show if any files got owned incorrectly. If so, do chown -R lewis:lewis /home/lewis/.steam.

          Not sure this is a permission/owner issue though. My guess is /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point: 285: exec: /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/run doesn’t have the executable bit. try chmod +x /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point: 285: exec: /home/lewis/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper/run.