Unity Technologies

Hi everybody,
Here's the first Linux build for the 2017.3 series, and with that, we've got a new installation experience.

Beginning in 2017.3, Linux will use a download assistant like Windows and OSX do, making the installation process more unified across all three platforms.
Among other things, this means that you can now get standard assets, example project, and documentation installed alongside Unity, instead of having to download them from the Asset Store or rely on online resources.
It also means that you can install only the components you want, without using extra gigabytes for packages you'll never use.

So, here's how it works:

Get the download assistant from our sleek, ultra-minimalist download page

Make it executable, via your file manager or the command line (chmod +x UnitySetup-2017.3.0b1)

Run it, via your file manager or the command line (./UnitySetup-2017.3.0b1)

The dependencies for Unity itself have not changed. Unfortunately, the download assistant doesn't verify/preinstall them the same way the deb package would (in conjunction with your distribution's package manager), but it's possible that helper functionality in that direction could be added in the future.

Anticipated FAQ:
Q: Can I install more packages later without doing a complete reinstall?
A: Yes. Just rerun the download assistant, and deselect everything that's already installed or that you still don't want. (You may need to reselect Unity to install packages that depend on it.)

Q: Do I need a GUI to install Unity now?
A: No! Run the download assistant with --help to see the available options.
At minimum, for a command-line installation, you'll want to pass --unattended, --components, and --install-location. (The installation host will, however, still need all of the download assistant's dependencies installed.)

Q: If I chose to cache the downloaded components locally, can I do another installation without redownloading them?
A: Yes. Just set your component download directory to the location where you downloaded the components previously, and the download assistant will reuse them, provided that their checksums are correct.

If you already have write permissions to the installation location, superuser privileges are not required. If you run the installer with superuser privileges, see "Known Issues" below.

By default Unity Setup will include a default set of packages. Use the --list-components switch to see which are installed by default and a list of additional components. You can install a custom list of components using the --components switch, which accepts a comma-separated list of components names. Note that --components is case-sensitive.

Dependencies
The Unity Linux Editor Beta requires the following dependencies to be installed:

gtk2 (libgtk2.0-0)

libsoup (libsoup2.4-1)

libarchive (libarchive13)

libpng (libpng12 or later)

Known Issues

If you ran the installer with superuser privileges, you should

Code (csharp):

sudo chown -R $USER:$USER Unity-2017.3.0f1

after installation completes. This will be fixed in a future release.

Mono Bleeding Edge has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

As noted in the last bullet, the Bug Reporter will now be triggered automatically when the Editor crashes. Your Editor logs should automatically be attached to bugs submitted through this tool. I encourage everyone to also attach their projects if they're not too large, or if they are large, to try and reproduce the crash in a fresh project and send that to us. That will really help us crack down on Editor stability!

If you already have write permissions to the installation location, superuser privileges are not required. If you run the installer with superuser privileges, see "Known Issues" below.

By default Unity Setup will include a default set of packages. Use the --list-components switch to see which are installed by default and a list of additional components. You can install a custom list of components using the --components switch, which accepts a comma-separated list of components names. Note that --components is case-sensitive.

Dependencies
The Unity Linux Editor Beta requires the following dependencies to be installed:

gtk2 (libgtk2.0-0)

libsoup (libsoup2.4-1)

libarchive (libarchive13)

libpng (libpng12 or later)

libgconf (libgconf-2-4)

Known Issues

If you ran the installer with superuser privileges, you should run

Code (csharp):

sudo chown -R $USER:$USER Unity-2017.3.0p2

after installation completes. This will be fixed in a future release.

Mono Bleeding Edge has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

Mono Bleeding Edge (Experimental/.NET 4.6 Equivalent) has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

Mono Bleeding Edge (Experimental/.NET 4.6 Equivalent) has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If you experience this, and the callstack printed in your editor log contains __do_global_ctors_aux, then you are seeing the same issue. Please file a bug report with your system information, and revert to the 2017.x series as a workaround.

Unity Technologies

Beginning with Unity 2018.2b2, the minimum required version of Gtk+ is 3.4.

Known Issues

If you ran the installer with superuser privileges, you should run

Code (csharp):

sudo chown -R $USER:$USER Unity-2018.2.0b2

after installation completes. This will be fixed in a future release.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If you experience this, and the callstack printed in your editor log contains __do_global_ctors_aux, then you are seeing the same issue. Please file a bug report with your system information, and revert to the 2017.x series as a workaround.

Mono Bleeding Edge (Experimental/.NET 4.6 Equivalent) has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If you experience this, and the callstack printed in your editor log contains __do_global_ctors_aux, then you are seeing the same issue. Please file a bug report with your system information, and revert to the 2017.x series as a workaround.

Unity Technologies

Beginning with Unity 2018.2b2, the minimum required version of Gtk+ is 3.4.

Known Issues

If you ran the installer with superuser privileges, you should run

Code (csharp):

sudo chown -R $USER:$USER Unity-2018.2.0b5

after installation completes. This will be fixed in a future release.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If you experience this, and the callstack printed in your editor log contains __do_global_ctors_aux, then you are seeing the same issue. Please file a bug report with your system information, and revert to the 2017.x series as a workaround.

There are issues with window resizing and touchpad scrolling that came with the Gtk2 => Gtk3 migration. These will be resolved in a later 2018.2 release.

Mono Bleeding Edge (Experimental/.NET 4.6 Equivalent) has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If you experience this, and the callstack printed in your editor log contains __do_global_ctors_aux, then you are seeing the same issue. Please file a bug report with your system information, and revert to the 2017.x series as a workaround.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If you experience this, and the callstack printed in your editor log contains __do_global_ctors_aux, then you are seeing the same issue. Please file a bug report with your system information, and revert to the 2017.x series as a workaround.

Unity Technologies

Beginning with Unity 2018.2b2, the minimum required version of Gtk+ is 3.4.

Known Issues

If you ran the installer with superuser privileges, you should run

Code (csharp):

sudo chown -R $USER:$USER Unity-2018.2.0b7

after installation completes. This will be fixed in a future release.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If you experience this, and the callstack printed in your editor log contains __do_global_ctors_aux, then you are seeing the same issue. Please file a bug report with your system information, and revert to the 2017.x series as a workaround.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If you experience this, and the callstack printed in your editor log contains __do_global_ctors_aux, then you are seeing the same issue. Please file a bug report with your system information, and revert to the 2017.x series as a workaround.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If you experience this, and the callstack printed in your editor log contains __do_global_ctors_aux, then you are seeing the same issue. Please file a bug report with your system information, and revert to the 2017.x series as a workaround.

Mono Bleeding Edge (Experimental/.NET 4.6 Equivalent) has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

Unity Technologies

Beginning with Unity 2018.2b2, the minimum required version of Gtk+ is 3.4.

Known Issues

If you ran the installer with superuser privileges, you should run

Code (csharp):

sudo chown -R $USER:$USER Unity-2018.2.0f1

after installation completes. This will be fixed in a future release.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If your symptoms resemble those reported here, please try removing Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so and reporting your results to that thread. Alternatively, you can revert to the 2017.x series as a workaround.

Unity Technologies

Beginning with Unity 2018.2, the minimum required version of Gtk+ is 3.4.

Known Issues

If you ran the installer with superuser privileges, you should run

Code (csharp):

sudo chown -R $USER:$USER Unity-2018.2.0f2

after installation completes. This will be fixed in a future release.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

Unity Hub is not available for testing on Linux yet.

Some users with particular CPUs (AMD Phenom, AMD E-series) are reporting startup crashes with the 2018 series. If your symptoms resemble those reported here, please try removing Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so and reporting your results to that thread. Alternatively, you can revert to the 2017.x series as a workaround.

Mono Bleeding Edge (Experimental/.NET 4.6 Equivalent) has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

Mono Bleeding Edge (Experimental/.NET 4.6 Equivalent) has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

Mono Bleeding Edge (Experimental/.NET 4.6 Equivalent) has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

Mono Bleeding Edge (Experimental/.NET 4.6 Equivalent) has a bug that causes the Editor to become unstable. Please use regular Mono. See this thread for more information.

The contracted installer option for --unattended (-u) doesn't function. Please use the full --unattended switch instead of -u.

You may see warnings in your Editor.log along the lines of:

Code (csharp):

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

This is benign and can be ignored.

There was a bug in the installer that would lead to it cleaning up the parent of the selected installation directory in some circumstances. We believe we have resolved the issue, but if it happens to you, your files are not lost - they're in the trash folder for the affected volume.

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

[0122/155902:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

Oops...

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S. and elsewhere (more info here). Other names or brands are trademarks of their respective owners.