Search Unity

[2018.2.0f2] Installation problem - Deb 9

Discussion in 'Linux' started by KingLy85, Jul 12, 2018.

  1. KingLy85

    KingLy85

    Joined:
    Jul 12, 2018
    Posts:
    4
    Hi,

    I just downloaded the UnitySetup-2018.2.0f2. I launched it perfectly, but I can't install ; in the Unity Download Assistant, I cannot choose any component to install, hence I'm stuck.

    Running on Deb 9 (Stretch).

    Any idea on how to fix this ?

    Thanks !
     
    KingLy85, Jul 12, 2018
    #1
    Esus_Spectrum likes this.

  2. Esus_Spectrum

    Esus_Spectrum

    Joined:
    Feb 5, 2017
    Posts:
    4
    also experiencing the same issue running Ubuntu 18.04LTS
     
    Esus_Spectrum, Jul 12, 2018
    #2

  3. mageaster

    mageaster

    Joined:
    Sep 1, 2015
    Posts:
    85
    Are all dependencies satisfied? What is outcome in terminal?
     
    mageaster, Jul 12, 2018
    #3
    Esus_Spectrum likes this.

  4. Esus_Spectrum

    Esus_Spectrum

    Joined:
    Feb 5, 2017
    Posts:
    4
    I believe all dependencies are satisfied, terminal output is ' Failed to load module "canberra-gtk-module" '

    I tired to resolve the issue with
    sudo apt-get install libcanberra-gtk-module:i386
    but ./UnitySetup-2018.2.0f2 still shows no components to download and kicks ' Gtk-Message: 14:57:32.165: Failed to load module "canberra-gtk-module" ' in the terminal
     
    Esus_Spectrum, Jul 12, 2018
    #4

  5. KingLy85

    KingLy85

    Joined:
    Jul 12, 2018
    Posts:
    4
    So, I tried re-running it again one more time, and let the Assistant run until it would eventually crashed, and the terminal gave me this :

    Unable to download any valid component lists, aborting
    (UnitySetup-2018.2.0f2:6538): GLib-CRITICAL **: g_key_file_get_value: assertion 'key != NULL' failed
    (UnitySetup-2018.2.0f2:6538): libsoup-CRITICAL **: soup_message_new: assertion 'uri_string != NULL' failed
    (UnitySetup-2018.2.0f2:6538): libsoup-CRITICAL **: soup_message_set_flags: assertion 'SOUP_IS_MESSAGE (msg)' failed
    (UnitySetup-2018.2.0f2:6538): GLib-GObject-WARNING **: invalid (NULL) pointer instance
    (UnitySetup-2018.2.0f2:6538): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
    (UnitySetup-2018.2.0f2:6538): GLib-GObject-WARNING **: invalid (NULL) pointer instance
    (UnitySetup-2018.2.0f2:6538): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
    (UnitySetup-2018.2.0f2:6538): libsoup-CRITICAL **: soup_session_queue_message: assertion 'SOUP_IS_MESSAGE (msg)' failed
     
    KingLy85, Jul 13, 2018
    #5

  6. Tak

    Tak

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    This is the issue. Do you get a bunch of messages before this about ini downloads failing?
     
    Tak, Jul 13, 2018
    #6

  7. KingLy85

    KingLy85

    Joined:
    Jul 12, 2018
    Posts:
    4
    Nope, that's all I get. Nothing more, nothing less.
     
    KingLy85, Jul 13, 2018
    #7

  8. KingLy85

    KingLy85

    Joined:
    Jul 12, 2018
    Posts:
    4
    Up,
    I was thinking about something. Can the installer be "blocked" by my school's proxy ?
     
    KingLy85, Jul 16, 2018
    #8

  9. Tak

    Tak

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    Yes, potentially - libsoup, which the installer is using to manage downloads, is supposed to automatically use a configured proxy, but we've found that it depends on how the proxy is configured on the system (and we're working on fixing this).
     
    Tak, Jul 30, 2018
    #9

  10. RobJessop

    RobJessop

    Unity Technologies

    Joined:
    Mar 8, 2017
    Posts:
    2
    I've tested a version of the code that enables automatic proxy resolution in gnome, but it relies on having configured the proxy in the system dialog on my test system (Ubuntu 16.04). The auto-resolve doesn't look up the proxy environment variables in your shell if you just set them there (in .bashrc, say).

    We might add support for proxies that are just configured in bashrc.

    Automatic proxy resolve isn't in any released version of Unity at the time of writing. We're working with a customer right now to help them resolve their proxy issues and our fixes should get backported to current Tech and LTS Unity releases when they're ready.
     
    RobJessop, Jul 31, 2018
    #10

  11. TheFellhuhn

    TheFellhuhn

    Joined:
    Feb 3, 2017
    Posts:
    42
    The problem is just that the URLs in the installer are broken.

    Those are the URLs it checks:

    ini_url1=https://netstorage.unity3d.com/unity/48afb4a72b1a/unity-2018.2.1f1-linux.ini
    ini_url2=https://download.unity3d.com/download_unity/48afb4a72b1a/unity-2018.2.1f1-linux.ini
    ini_url3=https://beta.unity3d.com/download/48afb4a72b1a/unity-2018.2.1f1-linux.ini
    ini_url4=https://files.unity3d.com/bootstrapper/48afb4a72b1a/unity-2018.2.1f1-linux.ini

    The first two are broken. So try the third one. This will leave you with a simple txt-file which includes the relative URLs to the binaries/tarballs. Like https://beta.unity3d.com/download/48afb4a72b1a/LinuxEditorInstaller/Unity.tar.xz. Download them manually.

    Sadly I am stuck afterwards as Unity fails to log me in thanks to the proxy and/or the strange sandbox stuff. The logs aren't very helpful.
     
    TheFellhuhn, Aug 8, 2018
    #11

  12. Tak

    Tak

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    This is normal. The files could be hosted in a variety of places depending on release line, etc., so the installer checks a series of them.
     
    Tak, Aug 10, 2018
    #12

  13. TheFellhuhn

    TheFellhuhn

    Joined:
    Feb 3, 2017
    Posts:
    42
    Strange. The installer I have only checks the first and then freezes. Perhaps again a problem with the proxy. Still couldn't start Unity.
     
    TheFellhuhn, Aug 14, 2018
    #13