Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a6
Issue ID
1173662
Regression
Yes
[Linux] Cannot run editor as Glibc 3.4.20-21 is required but unavailable in CentOS 7
[Linux] Cannot run editor as Glibc 3.4.20-21 is required but unavailable in CentOS 7
As of 2019.3.0a11, Unity (Linux) requires Glibc 3.4.20/3.4.21. As these versions of Glibc are currently unavailable in CentOS 7, the editor cannot be run, reporting the following errors:
~/Unity-2019.3.0a6/Editor/Unity: /lib64/libstdc+.so.6: version `GLIBCXX_3.4.20' not found (required by ~/Unity-2019.3.0a6/Editor/Unity)
~/Unity-2019.3.0a6/Editor/Unity: /lib64/libstdc+.so.6: version `GLIBCXX_3.4.21' not found (required by ~/Unity-2019.3.0a6/Editor/Unity)
Steps to reproduce:
1) On a machine running CentOS 7, install Unity 2019.3.0a6
2) Open the Unity installation
3) Observe the noted Glibc errors reported to console and that the editor will fail to run
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
- 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
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2019.3):
Cannot reproduce in 2019.3.0a12