Search Issue Tracker

Fixed in 2022.1.X

Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X



Found in







Issue ID




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

  1. Resolution Note (fix version 2022.1):

    Fixed in 2022.1.0a12

  2. Resolution Note (fix version 2021.2):

    Fixed in 2021.2.2f1

  3. Resolution Note (fix version 2021.1):

    Fixed in 2021.1.26f1

  4. Resolution Note (fix version 2020.3):

    Fixed in 2020.3.22f1

  5. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.32f1

Comments (1)

  1. 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

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.