You are not logged in.
Hello,
I have been trying to add three libraries to steam. All three are on seperate drives however the built-in steam file browser cant find them and not only that it can only find files inconsistently.
I am pretty sure at this point that the drives are no longer to blame but maybe someone can point out a mistake in the way my drives are mounted so I have included the fstab information for those drives.
Dolphin(I am using kde-plasma) shows them they are fully accessible and "ls -l" shows the drives with the correct owners/groups
# UUID="5FC65A6145701391" LABEL="drivea"
/dev/sda1 /home/me/drivea ntfs-3g rw,relatime,uid=me,gid=me 0 3
# UUID="1356911E50EAE12D" LABEL=driveb
/dev/sdb1 /home/me/driveb ntfs-3g rw,relatime,uid=me,gid=me 0 4
#UUID="7AB0E88A41F0FEE3" LABEL="drivec"
/dev/sdc1 /home/me/drivec ntfs-3g rw,relatime,uid=me,gid=me 0 5The LABEL addition is just for me if I change the directory name.
I have also tried the solution on the arch troubleshooting page using $ stat path and $ touch path.
This also seems to not have worked and $ stat path didnt show any folders being made in the future regardless.
If anyone knows of a good solution or a reason why I would greatly appreciate it.
Last edited by shockwave (2022-09-24 17:52:18)
Offline
Solved it.
I was just looking in the wrong place.
Steam itself wasnt the issue but it was the fact that it was installed as a flatpak and therefore only had access to specific folders. This solution has been posted before but by simply adding
flatpak override --user --filesystem=/home com.valvesoftware.SteamIt granted access to all the files/drives in my home folder
Offline