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

Bug Unity 2018 not able to open/create projects

Discussion in 'Linux' started by The-Little-Guy, Oct 20, 2018.

  1. The-Little-Guy

    The-Little-Guy

    Joined:
    Aug 1, 2012
    Posts:
    297
    I am having trouble opening and creating new projects with all Unity 2018 versions. I can open and create with Unity 2017 though.

    When I create/open a project, the loader/importer opens and runs, then it crashes. I don't know if it is in the middle of an import or after it completes and starts to load the UI. I never get to the UI, just a bug report screen.

    Has anyone else had issues and resolved them? I am not sure what to do.

    Code (csharp):
    1. Desktop is 3520 x 1080 @ 60 Hz
    2. [Package Manager] Server::Start -- Port 40068 was selected
    3. npm ERR! extraneous: unityeditor-collab-history@0.6.15-fix-history-revisions.1 /home/ryan/.local/share/unity3d/Packages/node_modules/unityeditor-collab-history
    4. ListPackages failed, output: {
    5.   "name": "unity-editor",
    6.   "version": "5.7.0",
    7.   "problems": [
    8.     "extraneous: unityeditor-collab-history@0.6.15-fix-history-revisions.1 /home/ryan/.local/share/unity3d/Packages/node_modules/unityeditor-collab-history"
    9.   ],
    10.   "dependencies": {
    11.     "unityeditor-collab-history": {
    12.       "version": "0.6.15-fix-history-revisions.1",
    13.       "extraneous": true,
    14.       "problems": [
    15.         "extraneous: unityeditor-collab-history@0.6.15-fix-history-revisions.1 /home/ryan/.local/share/unity3d/Packages/node_modules/unityeditor-collab-history"
    16.       ],
    17.       "from": "unityeditor-collab-history-0.6.15-fix-history-revisions.1.tgz",
    18.       "resolved": "file:unityeditor-collab-history-0.6.15-fix-history-revisions.1.tgz"
    19.     },
    20.     "unity-editor-home": {
    21.       "version": "2.1.4",
    22.       "from": "unity-editor-home.2.1.4.tgz",
    23.       "resolved": "file:unity-editor-home.2.1.4.tgz"
    24.     },
    25.     "unityeditor-cloud-hub": {
    26.       "version": "0.0.15",
    27.       "from": "unityeditor-cloud-hub-0.0.15.tgz",
    28.       "resolved": "file:unityeditor-cloud-hub-0.0.15.tgz"
    29.     },
    30.     "unityeditor-collab-toolbar": {
    31.       "version": "0.7.16",
    32.       "from": "unityeditor-collab-toolbar.0.7.16.tgz",
    33.       "resolved": "file:unityeditor-collab-toolbar.0.7.16.tgz"
    34.     }
    35.   }
    36. }
    37.  
    38.  
    39. LICENSE SYSTEM [20181020 12:3:55] Next license update check is after 2018-10-14T15:38:50
    40.  
    41.  
    42. COMMAND LINE ARGUMENTS:
    43. /home/ryan/Unity/Editor/2018.2.13f1/Editor/Unity
    44. -projectpath
    45. /home/ryan/Unity/Games/Bootstrap
    46. -useHub
    47. -cloudEnvironment
    48. production
    49. -hubSessionId
    50. 11b527a0-cefe-11e8-9be9-65c755b4598f
    51.  
     
    SNS_Case and Jeepty like this.
  2. APSchmidtOfOld

    APSchmidtOfOld

    Joined:
    Aug 8, 2016
    Posts:
    4,473
  3. The-Little-Guy

    The-Little-Guy

    Joined:
    Aug 1, 2012
    Posts:
    297
    I have an AMD CPU, and NVIDIA graphics card.
     
  4. The-Little-Guy

    The-Little-Guy

    Joined:
    Aug 1, 2012
    Posts:
    297
    The last BIOS update for my motherboard was 2012/07/27 I don't think doing that will help...
     
  5. Jeepty

    Jeepty

    Joined:
    Mar 9, 2016
    Posts:
    3
    I have this problem as well, right down to the 'npm err' in the Error.log. Linuxmint 19 cinnamon. I currently have installed, and use, unity 2018.2.7f1 and 2017.3.0f1. Those work just fine.

    I have tried updating node to the most current version to get around the npm error, but no luck. I have not yet reported as a bug.