Hi folks,
everytime I create a new project (Ubuntu 19, regardless which unity version I try). the scripts do not compile. If I open the project for the first time, I get warnings that the project would contain deprecated API calls.
If I try to create a new script, I see in the preview view
"“No MonoBehavior scripts in the file, or their names do not match the file name…”
I have the impression that the .NET assemblies are not correctly attached but I have no clue how to fix that.
Hi, Unity 2019.1.2f1 is the latest available version for Linux on the preview stream. Would you be able to post the full editor log you get when you create a fresh new project? Located at ~/.config/unity3d/Editor.log
Please note that Ubuntu 19.04 isn’t currently supported yet, but the known issues don’t usually interfere with the problems you’re seeing.
Hi,
I checked the log and I guess it is related to Unity Issue Tracker - [Linux][Editor] Package manager is missing on Ubuntu 19.04.
Same error. “No usable version of the libssl was found”. Also with the latest alpha.
—CompilerOutput:-stdout–exitcode: 134–compilationhadfailure: True–outfile: Temp/Unity.TextMeshPro.dll
-----CompilerOutput:-stderr----------
No usable version of the libssl was found
/home/xxx/Unity/Hub/Editor/2019.3.0a2/Editor/Data/Tools/RoslynScripts/unity_csc.sh: line 89: 6272 Aborted (core dumped) “/home/xxx/Unity/Hub/Editor/2019.3.0a2/Editor/Data/Tools/RoslynScripts/…/…/Tools/Roslyn/csc” /shared /noconfig @ /UnityTempFile-2ae961b7cfc3820d2aa9281b868779ee
-----EndCompilerOutput---------------
BTW. I have installed .NET core also, I do not know if that might have sideeffects too ?
So, I guess there is currently no workaround ?
For the libssl error right now a viable workaround would be to download the Cosmic package for libssl1.0 and install that alongside Disco’s libssl1.1, but since it’s not the cleanest way to get things working I’ll leave out giving full instructions - and you’d want to make sure to revert the install once we have a fix.
Thanks, works now ! 
@marcdi_unity Do you already know when the fix will be launched? Because I am currently facing this problem
and maybe this will then be solved too.
I have no ETA at this time, but it is being actively worked on
My scripts aren’t compiling either. Using 2019.3b and Windows. In the import inspector it shows the changes, but they aren’t actually applied when playing.