Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1084208
Regression
No
[Linux Hub] If Flash drive is selected as location for installs, Hub still looks at the hard drive for disk space
To reproduce:
1) Have your main drive filled up with files - It should have not enough space to download Unity from Hub
2) Insert a flash drive which would have enough space to download Unity from Hub
3) Open Unity Hub
4) Change your editor location to point at flash drive
5) Try downloading any editor version
Actual: When selecting components, "Space Left" is reported for "Home" drive, not Flash drive. If you go over that amount of space (but not over the space of flash drive), the download fails.
Reproduced in Unity Hub 1.0.0
Not reproduced in Windows 10
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (2019.2.X):
In Linux, it is currently checking for download size availability, the workaround is to change the TMPDIR to the external volume.