Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2018.4
2019.4
2020.3
2020.3.7f1
2021.1
2021.2
Issue ID
1339398
Regression
No
Linux build executable fails to start when being run through an environment variable
How to reproduce:
1. Create a new project
2. Name the executable "test" and build the project
3. In the system's terminal add the full build executable's path (without the executable itself) to the $PATH environment variable by running: export PATH=$PATH:[Build Path]
4. In the terminal navigate out of the build directory and start the executable by running: test.x86_64
Expected result: the player starts
Actual result: the player doesn't start and a "no boot config - using default values" error is thrown in the terminal
Reproducible with: 2018.4.35f1, 2019.4.28f1, 2020.3.12f1, 2021.1.11f1, 2021.2.0a19
Note: Reproducible on Ubuntu 18.04
-
hecker_de
Feb 06, 2022 01:08
Actually, if the executable is named "test" it is possible that the shell command "test" is run instead.
It's a very poor choice for a program's name.Perhaps it would be useful to check if a given executable name already exists in the path and reject it as configuration for the project (or at least ask for explicit confirmation)?
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
- [Android][Vulcan] "UNITY_DISPLAY_ORIENTATION_PRETRANSFORM" is always 0 when the render pipeline is URP
- Editor loads for a long time when doing an Undo action in a large Shader Graph
- Memory leak when building AssetBundles
- [Asset Bundle] AudioSource output field not staying connected correctly when loaded from Asset Bundle
- [Android] Duolashock4 controller is not detected after disconnecting and reconnecting controller while the Player is running in the background
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a12
Resolution Note (fix version 2021.2):
Fixed in 2021.2.2f1
Resolution Note (fix version 2021.1):
Fixed in 2021.1.26f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.22f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.32f1