Unity Editor for linux stalls in Debian Jessie

Unity Engine
1

When I start the Unity editor in Debian Jessie, it immediately pushes the CPU to 100% when I select the license (Personal). I can make it to the survey screen before it becomes entirely unresponsive. I can select my country and state, but, after that, I can’t scroll down to complete the form. When I start the application from the command-line, there is no output to the console, so no clues there.

Has anyone experienced this?

This issues makes the editor completely unusable on Debian Jessie.

2

I don’t even get the survey screen in my Unity editor (not through Wine) installation on Debian Jessie. All required libs, as listed here: Unity on Linux: Release Notes and Known Issues, were grabbed. Then there was an additional library file, libpq.so.5, that was needed when trying to open the editor, so I added the corresponding package: libpq5. Then the editor starts but now stalls at the splash screen with an empty window titled “Recent”, and no error info is shown in the Terminal. And one of my CPU cores is running at 100%.

I guess there is something which prevents the editor to launch properly or maybe the Unity Editor relies too much on the Ubuntu packages, which would be kind of sad but understandable. I would like to investigate further on this matter but I still do not have a good knowledge of the Linux environment, coming from Windows.

I have tried the unity-editor-installer-5.4.0b16+20160503.sh version. I will now try the unity-editor-installer-5.3.4f1+20160503.sh to see if it works.

After reading some other posts, I have the same behavior as for a Fedora user: Trouble getting Unity to start in Fedora 23 - Unity Engine - Unity Discussions

3

Nope, does not work. Even with 5.3.3f1. :frowning:

4

So I have tried the latest specific Ubuntu package (5.3.4f1) and it works like a charm! Upon installation, there were missing dependencies:

So I ran this command to download 30MB of packages (a pack of 71 packages was downloaded with it on my PC):

To make sure the install is properly configured, I ran again the dpkg command:

And here, I was able to enter my credentials and create a project, closing Unity and reopen it without any problem. :smile:

I still have a CPU core running at 100% though, but at least, it works. :stuck_out_tongue:

As a side note, the Ubuntu specific editor and the “other distributions” editor work now.