u/Common_Move_3624

I'm relatively new to immutable distros (running Fedora Kinoite), and I've run into an issue with file locations I'm not able to solve.

I've installed a program through steam which needs to be able to load from a specific folder. When I browse to local game installation location in Steam, it gives the following location:

~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/<game_etc>

However, when browsing files from the game, it says the files should be listed in the S: drive. I've tracked the S drive down to here:

~/.var/app/com.valvesoftware.Steam/data/Steam/steamapps/compatdata/<id>/pfx/dosdevices/s\:/common/<game_etc>

What's interesting is that the program cannot access files that *I* copy in these locations. It can find the default files just fine. Also of note: When I coped the files to the first, they also appeared in the second, so I'm assuming some kind of linking is happening.

The only time I was able to get the program to see one of my custom files at all was when I put it in my home folder and ran the following:

flatpak run --filesystem=~/filename com.valvesoftware.Steam

At this point I'm not really clear on the best way forward, or which part of the Steam -> Flatpak -> Proton stack is causing the issue, or whether it's a problem with the program itself.

Anyone else run into these issues, or can point me in the right debugging direction?

reddit.com
u/Common_Move_3624 — 20 days ago

I'm relatively new to immutable distros, and I've run into an issue with file locations I'm not able to solve.

I've installed a program through steam which needs to be able to load from a specific folder. When I browse to local game installation location in Steam, it gives the following location:

~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/<game_etc>

However, when browsing files from the game, it says they're listed in the S: drive. I've tracked the S drive down to here:

~/.var/app/com.valvesoftware.Steam/data/Steam/steamapps/compatdata/<id>/pfx/dosdevices/s\:/common/<game_etc>

What's interesting is that the program cannot access files that *I* copy in these locations. It can find the default files just fine. Also of note: When I coped the files to the first, they also appeared in the second, so I'm assuming some kind of linking is happening.

The only time I was able to get the program to see one of the files at all was when I put it in my home folder and ran the following:

flatpak run --filesystem=~/filename com.valvesoftware.Steam

At this point I'm not really clear on the best way forward, or which part of the Steam -> Flatpak -> Proton stack is causing the issue, or whether it's a problem with the program itself.

Anyone else run into these issues, or can point me in the right debugging direction?

reddit.com
u/Common_Move_3624 — 20 days ago