2018.x editor versions from hub not running at all

nitrofurano · Nov 3, 2019

hi everyone!

i tried to install all Unity versions available from Unity-hub, from 2017.x to 2020.x - all runs fine, except all 2018.x versions (even 5.5 works fine, installed outside the hub)

how can we help logging and finding out what is happening? it looks like segmentation fault, the problem is that it's hard to find out since even when we run unity from terminal, the terminal gets closed as well (i wonder why..)

sad is that i'm attending a training course based on Unity, but sadly they have 2018.x version installed (on windoze... and i guess they have that version installed because it's the last lts available - i wonder why it's the last lts when it is way so unstable on GNU/Linux... ) - and since i can't have whatever 2018.x version running on GNU/Linux (Ubuntu amd64 19.04 and 19.10), i have to create projects on 2017.x for opening there, and back at home i only can open that back on 2019.x or 2020.x, and remake everything on 2017 back again for being able to open there

thanks in advance...

Tautvydas-Zilys · Nov 5, 2019

We don't really support Ubuntu 19.04 or 19.10 - Unity supports 16.04 and 18.04.

That said, does the bug reporter pop up when editor crashes?

nitrofurano · Nov 10, 2019

Tautvydas-Zilys said: ↑

We don't really support Ubuntu 19.04 or 19.10 - Unity supports 16.04 and 18.04.
That said, does the bug reporter pop up when editor crashes?
Click to expand...

i didn't know that - so i guess it might be a kind of library issue?

no popup appear, it simply closes after finishing the application opening itself - and if we try to run it from the terminal (outside the hub) it simply closes the terminal as well - so i have no idea how can we get whatever kind of bug log from there - any idea, please let me know (like if we can try to open the editor from terminal with a specific argument that logs everything to a text file, so we can send it...)

anyway, interesting is that all 5.x, 2017.x, 2019.x and 2020.x opens perfectly fine on 19.10 (as they did on 19.04) - so this might be a clue?

(would be really helpful if more people having the same issues could share some feedback here as well)

nitrofurano · Nov 11, 2019

the situation is more weird that what i imagined - unity 2018 from hub attempts to open all assets from a project, but it looks like closing totally - but when from hub i try to open the same project in another version (like 2019, which opens fine), it says that the project can't be opened because 2018 is actually running it... when it's not! (i guess that the issue is not that i'm using AwesomeWM instead of Gnome-3 - whatever Unity version, except 2018.x, runs perfectly fine...)

nitrofurano · Nov 23, 2019

hi again! i saw that 2018.4.13f1 were released available at Unity Hub recently and installed - this version doesn't run on Ubuntu 19.10 (i guess that it isn't running on whatever Ubuntu version at all as well - how can we help finding out what is happening?)

nitrofurano · Nov 23, 2019

just a question: since such bug report popup never appeared, is there some way to run these 2018.x versions that reports everything in a log text file when opening? or this actually happens into some default log file somewhere i never knew if it exist or where it is?

andrews_unity · Nov 28, 2019

There is a log file for the editor, in ~/.config/unity3d/Editor.log

nitrofurano · Dec 1, 2019

thanks, this is what i have right now, i don't know if something might get erased from that file (i never touched it) - https://pastebin.com/raw/DzcBH1M9

nitrofurano · Dec 1, 2019

(i have no idea where are the opening attempts from unity 2018 written there)

aaroncgaudette · Dec 6, 2019

that log looks like it corresponds to a previous launch of the editor--for 2017.4--and unfortunately does not shed much light on the issue. try a clean launch of your system + 2018.4 and check your log again?

nitrofurano · Dec 14, 2019

Editor.log: https://pastebin.com/raw/zKGk8DXR
upm.log (might be needed?): https://pastebin.com/raw/U82B9axG

(these files above are fresh new, and were created after only one attempt of opening 2018.x)

from what we read from Editor.log, might this be a clue of something?

Code (csharp):

=================================================================

Got a SIGILL while executing native code. This usually indicates

a fatal error in the mono runtime or one of the native libraries

used by your application.

=================================================================

see that only 2018.x versions, all of them, closes before running (Unity Editor 2018 attempts to load, but no editing window appears) - and all other versions i installed (5.x, 2017.x, 2019.x and 2020.x) runs perfectly - so i imagine it's a situation very specific to 2018.x that is preventing it for running

Tautvydas-Zilys · Dec 14, 2019

What's your CPU?

nitrofurano · Dec 16, 2019

from cat /proc/cpuinfo: https://pastebin.com/raw/5CJVUdSC
and lspci, just in case: https://pastebin.com/raw/7BhE7RkP

Tautvydas-Zilys · Dec 16, 2019

That explains a lot. It's likely that Unity "accidentally" uses an instruction introduced in later CPUs. That is a bug, since your CPU meets Unity's minimum system requirements.

Could you run Unity via GDB (just type "gdb /mnt/sdb7/opt/unity/2018.4.14f1/Editor/Unity -projectpath /mnt/sdb7/trabalhos/programacao/csharp/unity/testes/2019/1/1") and when it crashes, type these commands:

Code (csharp):

set disassembly-flavor intel

disassemble

And then, please paste the output here.

nitrofurano · Dec 17, 2019

well... :S

Code (CSharp):

guest@amd-athlon:~$ gdb /mnt/sdb7/opt/unity/2018.4.14f1/Editor/Unity -projectpath /mnt/sdb7/trabalhos/programacao/csharp/unity/testes/2019/1/1

gdb: unrecognized option '-projectpath'

Use `gdb --help' for a complete list of options.

guest@amd-athlon:~$

nitrofurano · Dec 17, 2019

i also tried this:

Code (CSharp):

guest@amd-athlon:~$ gdb "/mnt/sdb7/opt/unity/2018.4.14f1/Editor/Unity -projectpath /mnt/sdb7/trabalhos/programacao/csharp/unity/testes/2019/1/1"

GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3

Copyright (C) 2019 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.

Type "show copying" and "show warranty" for details.

This GDB was configured as "x86_64-linux-gnu".

Type "show configuration" for configuration details.

For bug reporting instructions, please see:

<http://www.gnu.org/software/gdb/bugs/>.

Find the GDB manual and other documentation resources online at:

<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".

Type "apropos word" to search for commands related to "word"...

/mnt/sdb7/opt/unity/2018.4.14f1/Editor/Unity -projectpath /mnt/sdb7/trabalhos/programacao/csharp/unity/testes/2019/1/1: No such file or directory.

(gdb)

Tautvydas-Zilys · Dec 17, 2019

Yup that sounds about right. Type “run” to start it.

nitrofurano · Dec 17, 2019

Code (CSharp):

guest@amd-athlon:~$ gdb "/mnt/sdb7/opt/unity/2018.4.14f1/Editor/Unity -projectpath /mnt/sdb7/trabalhos/programacao/csharp/unity/testes/2019/1/1"

GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3

Copyright (C) 2019 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.

Type "show copying" and "show warranty" for details.

This GDB was configured as "x86_64-linux-gnu".

Type "show configuration" for configuration details.

For bug reporting instructions, please see:

<http://www.gnu.org/software/gdb/bugs/>.

Find the GDB manual and other documentation resources online at:

<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".

Type "apropos word" to search for commands related to "word"...

/mnt/sdb7/opt/unity/2018.4.14f1/Editor/Unity -projectpath /mnt/sdb7/trabalhos/programacao/csharp/unity/testes/2019/1/1: No such file or directory.

(gdb) run

Starting program:

No executable file specified.

Use the "file" or "exec-file" command.

(gdb)

Tautvydas-Zilys · Dec 17, 2019

Sorry, it's been a while since I last used GDB. Arguments apparently go to the run command. So you need to do this:

Code (csharp):

gdb /mnt/sdb7/opt/unity/2018.4.14f1/Editor/Unity

run -projectpath /mnt/sdb7/trabalhos/programacao/csharp/unity/testes/2019/1/1

nitrofurano · Dec 18, 2019

seems working?
https://pastebin.com/raw/NbvRUKqg
(right now, the window got frozen with "Starting Unity..." in the window caption, and nothing appearing inside, just the window border and the wallpaper from the window manager... i imagine it's this way it is expected to behave now as it is)

Tautvydas-Zilys · Dec 19, 2019

You're on the right track, but this isn't a crash. Looks like the debugger stops on the garbage collector signal. Can you try this?

Code (csharp):

gdb /mnt/sdb7/opt/unity/2018.4.14f1/Editor/Unity

handle SIGXCPU SIGPWR nostop noprint

run -projectpath /mnt/sdb7/trabalhos/programacao/csharp/unity/testes/2019/1/1

nitrofurano · Dec 20, 2019

i'm getting this: https://pastebin.com/raw/spj5Drr4

nitrofurano · Dec 20, 2019

another attempt, seems that the result is the same: https://pastebin.com/raw/Hh9qkNrf - it's freezing on "Hold on... - com.unity.collab-proxy/Editor/Resources/Styles/CollabHistoryLight.uss"

Tautvydas-Zilys · Dec 20, 2019

It's not the same! It let us figure out that the problem is in here:

Code (csharp):

Thread 1 "Unity" received signal SIGILL, Illegal instruction.

0x00007fffbb58471b in embree::precomputedBSplineBasis::precomputedBSplineBasis(int) () from /mnt/sdb7/opt/unity/2018.4.14f1/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so

This gives me enough leads to follow up on. Thank you.

If you could do a disassemble thing at that point, it would help even more.

nitrofurano · Dec 21, 2019

Code (csharp):

gdb /mnt/sdb7/opt/unity/2018.4.14f1/Editor/Unity

handle SIGXCPU SIGPWR nostop noprint

run -projectpath /mnt/sdb7/trabalhos/programacao/csharp/unity/testes/2019/1/1

set disassembly-flavor intel

disassemble

nitrofurano · Dec 21, 2019

sorry if it looks a bit chaotic, because that paging issue - can't that be logged into a text file?
https://pastebin.com/raw/QxLytbd2
https://pastebin.com/raw/4cbcr1mH
https://pastebin.com/raw/hHuu43mG

Tautvydas-Zilys · Dec 23, 2019

Perfect.

Basically, code in "/mnt/sdb7/opt/unity/2018.4.14f1/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so" uses SSE 4.1 instructions and your CPU doesn't support them, and thus crashes.

This is a bug in Unity, and if you could report a bug report, we can look at fixing it.

As a temporary workaround, can you try deleting that file and the .meta file next to it? Make sure to backup them somewhere outside of Unity installation before doing that, though.

nitrofurano · Dec 24, 2019

is moving these both files to /mnt/sdb7/opt/unity/2018.4.14f1/Editor/Data/UnityExtensions/Unity/VR/_Linux64_disabled enough? now i try to run it again and see what happens?

(and eventually, i guess that the eventual bug fix for this are sources from 2017.x, 2019.x and 2020.x, since no versions of them shown whatever behaviour like this?)

and how or where could we report that bug? i have no idea how to do that.... (perhaps this forum thread url can be a starting point for this? i have no idea...)

nitrofurano · Dec 24, 2019

(i needed to move these files outside /mnt/sdb7/opt/unity/2018.4.14f1/ )

nitrofurano · Dec 24, 2019

opening fine now: https://i.postimg.cc/6t69nZXg/unity-Screenshot-at-2019-12-24-18-02-31.png

nitrofurano · Dec 25, 2019

i think i could report the bug, i'm more comfortable with ticket systems... (i don't know if it arrived there, and if what i sent was useful enough)

nitrofurano · Dec 26, 2019

i don't know if it is supposed the bug report appear here: https://issuetracker.unity3d.com (i'm struggling to find...)

Tautvydas-Zilys · Dec 27, 2019

Here's a guide on how you can report a bug:

https://unity3d.com/unity/qa/bug-reporting

If you already did those steps, you should have received a 7-digit bug number. Please post the bug number here so I can follow up with it.

nitrofurano · Dec 28, 2019

received as e-mail message? i can't find it, how the e-mail title should look like, for searching?

Tautvydas-Zilys · Dec 30, 2019

Found it, it's case 1207680. We'll take a look and try fixing it!

nitrofurano · Dec 31, 2019

thanks! and happy new year!

Search Unity

Unity ID

Useful Searches

2018.x editor versions from hub not running at all

Unity Technologies

Attached Files:

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies

Unity Technologies