My issue is as follows:
Whenever I try to add a new disk/storage location to steam (via Steam Settings → Storage → the “+” button to add storage), it takes me directly to the Dolphin Portal to select a folder. When I choose a folder, nothing happens in steam, but when I look in the folder via Dolphin, a empty folder named steamapps has appeared if the folder was empty before.
I have tried to launch steam from the terminal, and here is the output from when I fist open the “+” button to add storage:
sh: line 1: /home/notqfthisworld/MountedDrives/GameDrive1/.steam_exec_test.sh: Permission denied
Failed system("/home/notqfthisworld/MountedDrives/GameDrive1/.steam_exec_test.sh") in execute test: 32256
Couldn't write /efi/.steam_exec_test.sh: Permission denied
sh: line 1: /home/notqfthisworld/MountedDrives/Videoprojects/.steam_exec_test.sh: Permission denied
Failed system("/home/notqfthisworld/MountedDrives/Videoprojects/.steam_exec_test.sh") in execute test: 32256
sh: line 1: /home/notqfthisworld/MountedDrives/Backups/.steam_exec_test.sh: Permission denied
Failed system("/home/notqfthisworld/MountedDrives/Backups/.steam_exec_test.sh") in execute test: 32256
sh: line 1: /home/notqfthisworld/MountedDrives/VirtualMachines/.steam_exec_test.sh: Permission denied
Failed system("/home/notqfthisworld/MountedDrives/VirtualMachines/.steam_exec_test.sh") in execute test: 32256
sh: line 1: /home/notqfthisworld/MountedDrives/Gamedrive2/.steam_exec_test.sh: Permission denied
Failed system("/home/notqfthisworld/MountedDrives/Gamedrive2/.steam_exec_test.sh") in execute test: 32256
It seems to be a list of all of the directories that I have mounted a drive to.
Has anyone encountered this issue before?
It happened on my pure archinstall too (on same system), and has been a problem since the new Steam overhaul. The issue is present in both the stable and the beta branch of Steam. I have tried to install it both from the multilib aur and from flatpak.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=D0B6-683B /efi vfat noatime 0 2
UUID=d8615f2d-16c3-4eed-82a6-480a02f36da0 / ext4 noatime 0 1
UUID=c21f3d91-87eb-493c-b8df-49651dba9e55 swap swap defaults 0 0
tmpfs /tmp tmpfs noatime,mode=1777 0 0
/dev/sda2 /home/notqfthisworld/MountedDrives/GameDrive1 ext4 users 0 0
/dev/sdb3 /home/notqfthisworld/MountedDrives/Gamedrive2 ext4 users 0 0
/dev/sdb2 /home/notqfthisworld/MountedDrives/VirtualMachines ext4 users 0 0
/dev/sdb1 /home/notqfthisworld/MountedDrives/Backups ext4 users 0 0
/dev/sdc1 /home/notqfthisworld/MountedDrives/Videoprojects ext4 users 0 0
I know that some of the drives has a bit to much “freedom” in terms of permissions… Think it was my way of trying to fix it earlier…
I may have a theory over why it happened too. I have been using KDE-Partition Manager, and each time I have mounted one of the partitions I have hooked of the ‘users can unmount and mount’ option. That may be the reason on why they were set to ‘users’ and not ‘defaults’. Just a theory tho.