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…
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?
1 Like
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)
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…)
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?)
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?
There is a log file for the editor, in ~/.config/unity3d/Editor.log
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
(i have no idea where are the opening attempts from unity 2018 written there)
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?
1 Like
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?
=================================================================
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
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:
set disassembly-flavor intel
disassemble
And then, please paste the output here.
1 Like
well… :S
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:~$
i also tried this:
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)
Yup that sounds about right. Type “run” to start it.
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)
Sorry, it’s been a while since I last used GDB. Arguments apparently go to the run command. So you need to do this:
gdb /mnt/sdb7/opt/unity/2018.4.14f1/Editor/Unity
run -projectpath /mnt/sdb7/trabalhos/programacao/csharp/unity/testes/2019/1/1
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)
