Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2020.2
2020.2.0a8
2020.2.0b2
Issue ID
1278063
Regression
Yes
[Linux] "Fatal error" is thrown when trying to install the Editor using a standalone installer through the terminal
Reproduction steps:
1. Download the Unity standalone installer
2. Perform the unattended install through the terminal
Expected result: The Editor is installed
Actual result: "Fatal error: required formats (xar, cpio, tar, gzip, xz) are not supported by system libarchive" error is thrown and the installation is aborted
Reproducible with: 2020.2.0a8, 2020.2.0b11, 2021.1.0a2
Not reproducible with: 2018.4.29f1, 2019.4.14f1, 2020.1.13f1, 2021.1.0a3
Notes:
- Tested on Ubuntu 18.04
- The error is thrown even though both libarchive-dev and libarchive-tools are installed on the system
- Command for the installation:
./UnitySetup --unattended --install-location="/PathTo/Location"
Comments (1)
-
jonas_unity305
Nov 19, 2020 11:58
Will this also be fixed for 2020.2? Kind of a bummer for all CI related builds ...
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- 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
Resolution Note (fix version 2021.1):
Fixed in version 2021.1.0a3
Resolution Note (fix version 2020.2):
Fixed in 2020.2.3f1