Hello @z0rti, https://github.com/ValveSoftware/steam-for-linux/issues/8081#issuecomment-954352996 notes that Steam is looking at /proc/mounts to generate the list of potential partitions that could be used to add a secondary Steam library folder and this basic test is to check if your regular unprivileged user is allowed to write an executable file to it. Trying and failing to write to these partitions should be harmless.
Steam-Version: 1686880776
Steam-Client: Build-Datum: Fr., 16. Juni 3:41 UTC -08:00
Steam: Webbuild-Datum: Fr., 16. Juni 3:10 UTC -08:00
Steam-API-Version: SteamClient020
Ubuntu 20.04.6 LTS
No but yes.
Please describe your issue in as much detail as possible:
Trying to add a new SteamLibrary dir to Storage
stdout log:
It probably should not try to write to the main root dir, and other user's dirs and every mounted HDD's root dir?
It seems like it does scan every user that is currently logged in and has a gvfsd running
Maybe it should only scan dirs for the current user that is actually running steam
And for the root dir of every mounted disk: maybe scan only disks that are added manually? Or a dir in the home?
Steps for reproducing this issue:
While multiple users are logged in (start a new term, 'sudo -i -u user2')
Start steam client (as user1), Settings, Storage, PLUS (+)