Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
0
Found in
2019.2.0a7
2019.3.0a1
2019.3.0a11
Issue ID
1176211
Regression
Yes
[Linux] Bugreporter is collecting Editor.log from wrong location for 2019.2.0a7+
To reproduce:
Create a new project and submit a bug report
Expected: Logs should be grabbed from ~/.config/unity3d/ (assuming default XDG_CONFIG_HOME value)
Actual: Logs are grabbed from ~/.config/unity3d/Unity/Editor/ (which 2019.1 and early 2019.2 alpha versions used)
Reproduced in 2019.2.0a7, 2019.2.0f1, 2019.3.0a1, 2019.3.0a12
"Not reproduced" in 2019.2.0a6, 2019.1.13f1 (the longer path is used there for storing editor logs)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment