protonscr

Steam client keeps creating empty temp folders owned by user "nobody" and group 100 on btrfs

steamclosed Steam clientDistro Family: Arch
ValveSoftware/steam-for-linux#10358 · opened 2024-01-06 by queenbiscuit311 · updated 2024-12-13 · 10 comments · github
Qqueenbiscuit311 2024-01-06 github

Your system information

  • Steam client version (build number or date): Steam Version: 1702079146 Steam Client Build Date: Thu, Dec 7 18:33 UTC -08:00

  • Distribution (e.g. Ubuntu): Arch Linux

  • Opted into Steam client beta?: No

  • Have you checked for system updates?: Yes

  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]

Am i supposed to include all of these here? Here's a zipped version and if needed ill send individual logs.
logs.zip

  • GPU: Nvidia RTX 3060 Laptop GPU

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist

When starting a game or updating, steam will randomly fail saying that there are "missing file permissions". Here are some examples:
image

image

When inspecting the folder shown in the vrchat error message, the problem can be seen clearly:
image

For some reason these temp folders will randomly be set to being owned by this user and this group. Steam is the only program I have that does this, and this happens regardless of the drive the steam library of a game is on, as long as its on btrfs. I've had this problem on 4 separate btrfs drives on this computer, so it is not a problem with my specific drive as far as i know.

In order to solve this problem, I must either use root user to delete these folders and have steam recreate them, or use chown to give myself full ownership of the steamlibrary folders. After doing this everything works as expected until it inevitably happens again. This happens extremely often, at least twice a week or more.

As you can see from these screenshots my steam client has a theme applied via adwsteamgtk, I have made absolutely certain that this is not the source of the problem, especially since it started long before i installed this theme. I've also attempted full clean installs of steam to no avail. This issue has persisted since I converted my system to brtfs about 7 or 8 months ago.

As for what I expected should happen, steam's temp folders should not have permission problems.

Steps for reproducing this issue:

  1. Have a steam library on a btrfs drive
  2. Install games on it
  3. This happens
Ppwalsh0 2024-01-15 github

Works fine on btrfs for me, but I am running flatpak version. Is there anything else strange about your setup? Running steam as what user? Installed steam how?

Maybe you have strange mount options?

Qqueenbiscuit311 2024-01-17 github

Works fine on btrfs for me, but I am running flatpak version. Is there anything else strange about your setup? Running steam as what user? Installed steam how?

Maybe you have strange mount options?

i didn't get an email for this for some reason. i can send my fstab file but I don't believe I have any problematic mount options set. I'm using steam from arch repos as user id 1000 since I'm the only person that uses this computer. I'm not sure of anything specifically odd about my setup. I'm using a non-standard kernel in the form of linux-ck but Ive been having this issue long before I installed that and I don't think a custom scheduler should cause issues with file permissions. other than that my setup is normal

Aactioninja 2024-12-12 github

Bumping, just ran into the same issue.

Qqueenbiscuit311 2024-12-12 github

Bumping, just ran into the same issue.

are you by any chance dual booting windows with winbtrfs

Aactioninja 2024-12-12 github

Bumping, just ran into the same issue.

are you by any chance dual booting windows with winbtrfs

You know, thinking about it it did manifest after booting back in to a windows partition. I thought nothing of it because while I did use winbtrfs at one point I moved off of it due to occasional issues and filesystems are the last thing I want to be having problems with, but I do in fact still have the driver installed. Very strange issue, I wonder if steam is doing something goofy on windows when it hits the btrfs partition or if it's a bug with winbtrfs.

Qqueenbiscuit311 2024-12-12 github

For me, the problem was that winbtrfs automatically uses uid 100 and gid 100 for whatever reason, this means that when steam on windows creates temp folders, steam on linux can't erase or add to them. If you want I can find what I did to change it to the Linux default of 1000:1000 and see if it works for you.

Kkisak-valve maintainer 2024-12-12 github

Hello @queenbiscuit311, "Application files installed by Steam for Linux should not be shared (e.g. between Windows and Linux). This is a requirement of the Steam for Linux client." noted at https://github.com/ValveSoftware/steam-for-linux/blob/master/RelNotes.md, sharing Steam Library folders between OSes is not supported and this is yet another example of undefined behavior that can happen. It might be worthwhile to report your findings to the WinBtrfs dev(s).

Qqueenbiscuit311 2024-12-12 github

For anyone else with this problem: https://github.com/maharmstone/btrfs#Mappings go to the mappings section of this page and follow the instructions to make sure your windows users accesses btrfs with the same uid and gid as your linux user, for example 1000:1000 or 1001:1001. changing the uid only should work but i'd recommend just doing both. You could also use chmod -R 0777 to change the permissions on your steam library folder to allow every user read and write access regardless of individual folder or file permissions, but be aware this will allow everyone on your computer to access it. I did this a while ago and this problem has not appeared since. This is seemingly intended behavior that isn't usually a problem except for things like steam.

Qqueenbiscuit311 2024-12-12 github

also thanks for closing the issue since i forgot

Aactioninja 2024-12-13 github

I think it was just a perfect storm here because the drive was completely reformatted and I didn't intentionally readd it to steam, but said drive previously had a steam library at the exact same directory and windows just happened to pick up the drive on the same letter. Highly unusual case, sane closure.

Nothing extracted yet.