Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Is it possible to activate Unity on Linux via command line?

Discussion in 'Linux' started by Improbable-Licences, May 11, 2016.

  1. Improbable-Licences

    Improbable-Licences

    Joined:
    Mar 2, 2016
    Posts:
    6
    I'm deploying Unity for Linux on several build agents, I use Puppet. My last step is to activate it without requiring user intervention. I can do it on Windows and Mac OSX but seems I can't on Linux. Here the command:

    /opt/Unity/Editor/Unity -quit -nographics -batchmode -serial R3-XXXX-XXXX-XXXX-XXXX-XXXX -username "mail@domain.com" -password "SuperStrongPassword"

    tried the parameters one by one and seems that the one that throws the error is the "-batchmode"

    Anyone know why it fails? I'm using the latest available build "unity-editor-5.3.4f1+20160503_amd64.deb" and Ubuntu 16.04.

    Something else that doesn't work is running the "Unity" command after adding /opt/Unity/Editor to the $PATH. If you use the full path (/opt/Unity/Editor/Unity) works fine.
     
    Last edited: Jun 9, 2016
    thiagofdp likes this.
  2. pixity71

    pixity71

    Joined:
    Apr 23, 2015
    Posts:
    7
    Having the same problem via Ubuntu 16.04
     
  3. Zelmor_

    Zelmor_

    Joined:
    Jun 11, 2016
    Posts:
    1
    Hi folks,

    You can start it by the following:

    /opt/Unity/Editor/Unity %U

    Make a symlink to /bin so you can start via the i3 app-finder or similar.

    Cheers!
     
    Last edited: Jun 11, 2016
  4. Tak

    Tak

    Unity Technologies

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    We've found and fixed the issue in the 5.3.6 build.