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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Add comment