• Vilian@lemmy.ca
      7·
      29 days ago

      I remember this lol, to be fair no one knew how the guy managed todo it, because steam(the launcher) has checks for that, they assume the guy tried to run the steam command instead of clicking the launcher(don’t do that)

            • slacktoidEnglish
              1·
              9 days ago

              Makes sense… I was curious what your solution was… Sounds like I should invest some time into that … Thanks.

              • raspberriesareyummy@lemmy.world
                2·
                9 days ago

                On debian testing (trixie):

                $ cat bin/steam-jailed.sh

                #!/bin/sh
firejail --private=/home/user/steamjail --profile=/etc/firejail/steam.profile ~/steam $1

                Sometimes an update breaks something, and I have to experiment with the profile settings, for which it helps to launch a bash with the same jail and start steam on the command line inside the jail to see output messages.

                #!/bin/sh
firejail --private=/home/user/steamjail --blacklist=${HOME}/.inputrc --profile=/etc/firejail/steam.profile bash

                What happens most of the time is that a steam update depends on a newer system library that I didn’t yet install and I then have to do a system update - steam is shit at managing OS dependencies (i.e.: it doesn’t)

    • exu@feditown.comOPEnglish
      16·
      29 days ago

      I ran the command without sudo first. It had a bunch of permission errors removing stuff in /tmp. So I retried but with sudo

      • superkret@feddit.org
        15·
        29 days ago

        /tmp is world-writable. If you get permission-errors, you should become suspicious.
        Also, whenever you write “sudo rm -rf” you should quadruple-check if that’s really what you want to do.
        Non-interactively deleting entire directories in root space isn’t something you should have to do normally.

          • shoki@lemmy.world
            3·
            29 days ago

            Exactly! if a service running under root creates a file, it belongs to root. if that file has permissions that don’t allow other users to write (most do), then you can’t delete it without sudo afaik

        • exu@feditown.comOPEnglish
          3·
          29 days ago

          Agreed, I should have been more careful. Fortunately it was just my downloads folder.
          In wanted to clear my /tmp, because I’d run out of space there for extracting an ISO file. It lives on a tmpfs, so space is quite limited.

  • chicagohuman@lemm.ee
    3·
    28 days ago

    I’m tired of my Downloads folder filling up, so I usually have a startup script that empties it. This has actually been really helpful!

    Make it a habit!

  • Dagamant@lemmy.world
    3·
    29 days ago

    The worst I have done is wipe out my home directory. Backups are good, I was able to copy everything back and it was like it never happened