What you write is very strange.

Rather, this is some other problem, no permissions, live mounted catalog, live change of configuration file path or something similar.

I haven't tested this myself, but I do know steam has issues honoring sybolic links (or even seeing them) in a couple other areas (proton and symlinked game libraries iirc...)

arguably it seems they use a lower level file access API than they should

it's not a shock to see someone report a similar issue in the custom compatibility tools folder

Originally posted by Marlock:

I haven't tested this myself, but I do know steam has issues honoring sybolic links (or even seeing them) in a couple other areas (proton and symlinked game libraries iirc...)

arguably it seems they use a lower level file access API than they should

it's not a shock to see someone report a similar issue in the custom compatibility tools folder

After restarting steam?
Some paths will be loaded when the program starts, and will no longer be refreshed.

This would be the first time I've seen anything like this.

My problem is present even after rebooting the OS, so restarting Steam doesn't help either.

I also have this issue. Has anyone tested hard linking directories? What about recursive links?

I also have this issue. Has anyone tested hard linking directories? What about recursive links?

Steam will have to fix this issue if they intend to use Nix as the foundation of SteamOS.

Originally posted by grzegorz77:

Originally posted by Marlock:

I haven't tested this myself, but I do know steam has issues honoring sybolic links (or even seeing them) in a couple other areas (proton and symlinked game libraries iirc...)

arguably it seems they use a lower level file access API than they should

it's not a shock to see someone report a similar issue in the custom compatibility tools folder

After restarting steam?
Some paths will be loaded when the program starts, and will no longer be refreshed.

This would be the first time I've seen anything like this.

that may be true as well, but I meant that steam ignores symlinks sometimes even if the target is 100% dead sure valid at boot (eg: symlinking folder A to folder B inside the same partition)

this is usually the case for proton games

my guess is they needed a way to break out of symlink loops and to avoid some scenarios where symlinks to outside the proton prefix are a problem

Originally posted by Marlock:

Originally posted by grzegorz77:

After restarting steam?
Some paths will be loaded when the program starts, and will no longer be refreshed.

This would be the first time I've seen anything like this.

that may be true as well, but I meant that steam ignores symlinks sometimes even if the target is 100% dead sure valid at boot (eg: symlinking folder A to folder B inside the same partition)

this is usually the case for proton games

my guess is they needed a way to break out of symlink loops and to avoid some scenarios where symlinks to outside the proton prefix are a problem

Now I remembered that I used to have a problem with steam.
Some characters allowed in filenames, were not allowed to be used with Steam.
It was something surprising, like a space or a bottom line.

as a workaround, try mounting directories there.
https://askubuntu.com/questions/205841/how-do-i-mount-a-folder-from-another-partition