• 1 Post
  • 40 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle






  • 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.







  • Because you’re arbitrarily restricting yourself to old versions of tools and software. The idea is you don’t want unexpected conflicts to bring down your system. But, what that means is when you do go to upgrade on something like a server, you would test the whole thing on the new version, and then migrate. That’s not how people use desktops. You just feel like one day upgrading from 20.04 to 20.10, and then get a massive burst of differences. It’s really hard to pin down what specifically goes wrong when something does.

    So unless you have a staging environment for your desktop where you test the new version before migrating, then what is the purpose of running old versions of stuff?