Search Unity

Bug (Add Log text)Crashed when running Command Line in Pure Command line interface of Ubuntu 15.04

Discussion in 'Linux Editor' started by LuUDDD, Sep 23, 2015.

  1. LuUDDD

    LuUDDD

    Joined:
    Sep 23, 2015
    Posts:
    2
    I’m facing an problem:
    Today I tried to run the Unity Editor in Command Line In Ubuntu:

    /opt/Unity/Editor/Unity/ -nographics -batchmode -quit

    It worked in Graphics interface but Crushed in Pure Command line interface and throw that:

    Aborted(core dumped)

    Can I get more help to fix that?

    Thanks for sight. crush.jpg


    LogFile:
     

    Attached Files:

    Last edited: Sep 23, 2015
  2. LuUDDD

    LuUDDD

    Joined:
    Sep 23, 2015
    Posts:
    2
    Any Feedback Please?
     
  3. sirnuke

    sirnuke

    Joined:
    Aug 10, 2015
    Posts:
    4
    I think you are running into the same issue I was having, while setting up automated builds (via Jenkins). I believe the editor tries to display a splash screen even when -nographics is enabled, and handles the lack of X server very poorly.

    I can partially get around it using xfvb-run (sudo apt-get install xfvb), which runs a headless virtual X server.

    However, Unity still crashes unless the Jenkins user is logged into the actual X server. I admittedly don't know much about the inter workings of X, but my suspicion is there's environmental variables that aren't being properly followed.

    In my case, setting the Jenkins user to autologin is an acceptable solution. This might not be a secure solution for some setups.

    If you are running 100% headless with no Gnome/KDE/etc desktop environment at all, it's possible that you just need to wrap Unity in xfvb-run.