Steam client version (build number or date):
Steam Beta Branch: Steam Beta Update
Steam Version: 1740182889
Steam Client Build Date: Fri, Feb 21 5:43 PM UTC -05:00
Steam Web Build Date: Fri, Feb 21 4:44 PM UTC -05:00
Steam API Version: SteamClient021
Distribution (e.g. Ubuntu):
EndeavourOS / Arch, replicated on Kubuntu and Fedora 41
Opted into Steam client beta?: [Yes/No]
Yes
Have you checked for system updates?: [Yes/No]
Yes
Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs] steam-logs.tar.gz
GPU: Nvidia/Intel/AMD
Nvidia
Please describe your issue in as much detail as possible:
When I add a drive via fstab to a mount point (ex: /mnt/slow-storage) the drive appears to be attached but shows the wrong amount of storage available. A drive auto-mounted at media seems to show correctly though.
In my example, the mounted drive is a 4tb HDD given the name "slow-storage" it appears that the drive isn't showing the correct amount of free storage and is instead showing the same storage that the system has available.
Steps for reproducing this issue:
Mount a drive to /mnt/ using fstab
Add the drive to Steam (in my example, /mnt/slow-storage/steamlibrary)
Your system information
Steam Beta Branch: Steam Beta Update
Steam Version: 1740182889
Steam Client Build Date: Fri, Feb 21 5:43 PM UTC -05:00
Steam Web Build Date: Fri, Feb 21 4:44 PM UTC -05:00
Steam API Version: SteamClient021
EndeavourOS / Arch, replicated on Kubuntu and Fedora 41
Yes
Yes
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]steam-logs.tar.gz
Nvidia
Please describe your issue in as much detail as possible:
When I add a drive via fstab to a mount point (ex: /mnt/slow-storage) the drive appears to be attached but shows the wrong amount of storage available. A drive auto-mounted at media seems to show correctly though.
In my example, the mounted drive is a 4tb HDD given the name "slow-storage" it appears that the drive isn't showing the correct amount of free storage and is instead showing the same storage that the system has available.
Steps for reproducing this issue: