Search Unity

2017.3.0b1 Linux Standalone Project Crashes On Init

Discussion in 'Linux' started by wreuven, Sep 30, 2017.

  1. wreuven

    wreuven

    Joined:
    Sep 26, 2017
    Posts:
    3
    Installed UnitySetup-2017.3.0b1
    The editor seems to run fine and I built an empty project.
    Ubuntu 16.10
    Nvidia OpenGL Drivers

    Here is the Unity3D log.

    Set current directory to /home/gigo/DefApp
    Found path: /home/gigo/DefApp/aaa.x86_64
    Mono path[0] = '/home/gigo/DefApp/aaa_Data/Managed'
    Mono config path = '/home/gigo/DefApp/aaa_Data/Mono/etc'
    Preloaded 'ScreenSelector.so'
    Receiving unhandled NULL exception
    #0 0x007fffd6b88500 in funlockfile
    #1 0x007fffd6b88958 in (Unknown)


    Thread 1 (Thread 0x7f4b839bab80 (LWP 30357)):
    #0 0x00007f4b833b26ad in read () at ../sysdeps/unix/syscall-template.S:84
    #1 0x00007f4b7a7d757b in ?? () from /home/grabya/DefApp/aaa_Data/Mono/x86_64/libmono.so
    #2 <signal handler called>
    #3 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
    #4 0x00007f4b825623ea in __GI_abort () at abort.c:89
    #5 0x00000000009dd83c in ?? ()
    #6 0x00007f4b7a817b71 in ?? () from /home/grabya/DefApp/aaa_Data/Mono/x86_64/libmono.so
    #7 0x00007f4b7a77614f in ?? () from /home/grabya/DefApp/aaa_Data/Mono/x86_64/libmono.so
    #8 <signal handler called>
    #9 0x0000000000000000 in ?? ()
    #10 0x0000000000e05e9b in ?? ()
    #11 0x0000000000e0460f in ?? ()
    #12 0x00007f4b7279d0c2 in ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
    #13 0x00007f4b7279f409 in FT_Open_Face () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
    #14 0x00007f4b7279fa0b in FT_New_Face () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
    #15 0x00007f4b73da3e2b in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
    #16 0x00007f4b73da7952 in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
    #17 0x00007f4b73d52892 in cairo_scaled_font_create () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
    #18 0x00007f4b782a93dd in ?? () from /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0
    #19 0x00007f4b782a9f89 in ?? () from /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0
    #20 0x00007f4b73512c6f in ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
    #21 0x00007f4b735163a9 in pango_layout_line_get_extents () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
    #22 0x00007f4b7351872f in ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
    #23 0x00007f4b73518a12 in ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
    #24 0x00007f4b73518c86 in pango_layout_get_pixel_extents () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
    #25 0x00007f4b7918fdd8 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
    #26 0x00007f4b79190147 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
    #27 0x00007f4b79192862 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
    #28 0x00007f4b78c8df75 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
    #29 0x00007f4b78c9f95c in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
    #30 0x00007f4b78ca8bcc in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
    #31 0x00007f4b78ca945b in g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
    #32 0x00007f4b792925c8 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
    #33 0x00007f4b7919e392 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
    #34 0x00007f4b791a0ab4 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
    #35 0x00007f4b791a0c1d in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
    #36 0x00007f4b78c8df75 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
    #37 0x00007f4b78c9ff82 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
    #38 0x00007f4b78ca8bcc in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
    #39 0x00007f4b78ca8faf in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
    #40 0x00007f4b79221814 in gtk_list_store_insert () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
    #41 0x00007f4b79769f8e in LoadScreenSelectorWindow () from /home/grabya/DefApp/aaa_Data/Plugins/x86_64/ScreenSelector.so
    #42 0x00000000012bd1fa in ?? ()
    #43 0x0000000000460273 in ?? ()
    #44 0x00007f4b8254b3f1 in __libc_start_main (main=0x45f630, argc=1, argv=0x7ffc72c33c18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc72c33c08) at ../csu/libc-start.c:291
    #45 0x000000000046de89 in ?? ()
    #46 0x00007ffc72c33c08 in ?? ()
    #47 0x000000000000001c in ?? ()
    #48 0x0000000000000001 in ?? ()
    #49 0x00007ffc72c358f4 in ?? ()
    #50 0x0000000000000000 in ?? ()

    =================================================================
    Got a SIGABRT while executing native code. This usually indicates
    a fatal error in the mono runtime or one of the native libraries
    used by your application.
    =================================================================

    Aborted (core dumped)
     
    Last edited: Sep 30, 2017
  2. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,618
    If you think you found a bug in Unity, I recommend to submit a bug-report following the advice in this document.

    Using the bug-reporter seems to be an important step, because it makes sure the report is in Unity Technologies bug-tracking pipeline and has to be processed at some point. Using the forum is often used to add to a little more attention to a bug-report, but does not replace submitting the bug-report.

    It's from advantage to attach a project to the bug-report that UT can use to reproduce the issue and test their fix against. The easier an issue can be reproduced by QA, the more likely it is to get forwarded to a developer, who might or might not work on a bug-fix for that at some point.

    After you submitted the bug-report, you receive a confirmation email with a Case number. UT often asks us to post the Case number in the forum thread, which allows them to find that bug-report if they look at your post.

    Following these steps will increase the chance that UT is looking at your issue tremendously.
     
    hippocoder likes this.
  3. hippocoder

    hippocoder

    Digital Ape

    Joined:
    Apr 11, 2010
    Posts:
    29,723
    Moved to the 2017.3 forum.
     
  4. Tak

    Tak

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    This appears to be something in your system's freetype crashing while initializing the screen selector dialog.
    You can work around this locally by disabling the screen selector in the player build preferences.
     
  5. Tak

    Tak

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    We've discovered an issue where our internal freetype can conflict with the system freetype and cause a crash like this - the fix will come in an upcoming 2017.3 release.