Veracrypt virtual drives are not present as an option for manually adding an existing steam library. No option for /media under root on the "create or select new steam library folder" pop up
steamopen
ValveSoftware/steam-for-linux#8492 ·
opened 2022-03-20
by kchat0 ·
updated 2022-03-20 ·
0 comments ·
github
Steam client version (build number or date): Mar 14 2022
Distribution (e.g. Ubuntu): Pop!_OS 21.10
Opted into Steam client beta?: No
Have you checked for system updates?: Yes
Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
When trying to add a steam game library on a Veracrypt encrypted virtual drive there is no option to select the Veracrypt virtual drives. The drives are mounted under "/media/veracryptX" where "X" is the drive number in sequential order. Previous versions of steam allowed me to select my Veracrypt virtual drives and add the Steam library to it. With the current version there's no /media folder listed under root. There's also no way to manually enter a path (that I know of after talking to support.)
Steps for reproducing this issue:
Use Pop!_OS 21.11
Open steam and navigate to settings -> downloads -> steam library folders -> "+" button for new or existing steam folder
Your system information
Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
When trying to add a steam game library on a Veracrypt encrypted virtual drive there is no option to select the Veracrypt virtual drives. The drives are mounted under "/media/veracryptX" where "X" is the drive number in sequential order. Previous versions of steam allowed me to select my Veracrypt virtual drives and add the Steam library to it. With the current version there's no /media folder listed under root. There's also no way to manually enter a path (that I know of after talking to support.)
Steps for reproducing this issue:
the only options available under root are the following:
app
dev
etc
home
proc
run
sys
tmp
usr
var