Search Issue Tracker
Won't Fix
Won't Fix in 3.4.X
Votes
0
Found in [Package]
3.4.0
Issue ID
PPB-47
Regression
Yes
[Linux] Getting "File could not be read" errors when installing Post Processing package with git url
{}Reproduction steps{}:
- Create a new Unity Project
- Open Package Manager Window (Window > Package Manager)
- Click on the plus icon in the Package Manager Window
- In the dropdown select 'install package from git URL...'
- Enter this link '[https://github.com/Unity-Technologies/Graphics.git?path=com.unity.postprocessing]' and press Install
- Wait for the install to complete and check the console
{}Expected result{}: No errors or warnings are shown
Actual result: "File could not be read" errors are shown
{}Reproduced on{}: Ubuntu 22.04.3 LTS, Intel® Core™ i7-8850H CPU @ 2.60GHz × 12, NVIDIA GP107M
{code:java}
Could not create asset from Packages/com.unity.postprocessing/PostProcessing/Textures/SpectralLUTs/SpectralLut_RedBlue.tga: File could not be read{code}
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
- "No GUI Implemented" is displayed when using PhysicsMask with a CustomEditor
- "Report is from another project" popup warning is shown on domain reload when Project Auditor was previously ran in a different project
- Addressables Analyzer flags duplicate resource references from ScriptableObjects incorrectly when the corresponding field has been removed
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (3.4.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.