Search Unity

Bug Unity messes up environment variables

Discussion in 'Linux' started by adabrowski, Aug 7, 2019.

  1. adabrowski

    adabrowski

    Joined:
    Dec 17, 2018
    Posts:
    3
    Unity 2019.x is not usable for me on Linux.

    Previously (the 2018.3 version) it launched directly and preserved the environment vars (e.g. LD_LIBRARY_PATH, but I don't mean only this one).

    Now it launches the Hub first and the environment variables are dropped. This is unacceptable and a reason I am staying with 2018.3.

    I am also unable to run Unity directly, there's no command line argument for that (I really don't want the Hub to lunch).
     
    adabrowski, Aug 7, 2019
    #1

  2. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    You can do "Unity -projectPath "<path/to/your/project>" and Unity will not attempt to launch the hub.

    Can you file a bug on the environment variable issue?

    EDIT: Hub team tells me this is fixed in Hub 2.1 which should be coming out later today.
     
    Tautvydas-Zilys, Aug 7, 2019
    #2
    Eyap and adabrowski like this.

  3. adabrowski

    adabrowski

    Joined:
    Dec 17, 2018
    Posts:
    3
    Wonderful, thank you!
     
    adabrowski, Aug 8, 2019
    #3

  4. rbehshad

    rbehshad

    Joined:
    Jul 19, 2017
    Posts:
    5
    Path environment variable is not preserved when launching from Hub 3.0.0-beta.2. But it's working in the latest 2.x hub
     
    rbehshad, Aug 14, 2021
    #4

  5. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    Report a bug please.
     
    Tautvydas-Zilys, Aug 14, 2021
    #5