Unity Hub on Linux

[Invector]

@erikso_unity

Could you give a few more details on what the issue is? We have internally encountered an issue on Hub startup that can be worked around by adding the following arguments to your Hub launch command:
--appimage-extract-and-run --no-sandbox
If this does not work for you, please open up a bug so we can track and fix it!

It doesn’t open or open a window but doesn’t show any content

Here is another user that somehow manage to fix but he doesn’t know how:
https://discussions.unity.com/t/879261

[Invector]

How to get Hub 3.1.2 to work on Ubuntu 22.04 LTS
(solution by @tobagind )

Add this repository using the terminal:

echo “deb Index of /ubuntu impish-security main” | sudo tee /etc/apt/sources.list.d/impish-security.list

and install

sudo apt update
sudo apt-get install libssl1.1

Now uninstall the hub if you have installed and install it again by following this guide:
https://docs.unity3d.com/hub/manual/InstallHub.html#install-hub-linux

[MX-Pain]

After doing apt update.
I get from the terminal the following:
https://hub.unity3d.com/linux/repos/deb/dists/stable/InRelease: Key is stored in legacy t
rusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for det
ails.
Also Unity Hub is not opening. Testing on Kubuntu 22.04 Lts.

Edit: The above coment from Invector helped to open the hub.
Edit 2: Worst decision ever to turn down the app.image. More companies should use app.image as a default.

[KevinWelton]

@MX-Pain

After doing apt update.
I get from the terminal the following:
https://hub.unity3d.com/linux/repos/deb/dists/stable/InRelease: Key is stored in legacy t
rusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for det
ails.
Also Unity Hub is not opening. Testing on Kubuntu 22.04 Lts.

We do not currently support Ubuntu 22.04 or KDE. Our supported platforms are Ubuntu 18.04, 20.04 and CentOS 7 running the X11 window server and GNOME window manager.

We’re aware of issues with both the Hub and Editor on Ubuntu 22.04 and are working to address them before we announce full support. The biggest issue faced is the OpenSSL 1.1 dependency. This is probably what you are seeing here.

[print_helloworld]

@MX-Pain

After doing apt update.
I get from the terminal the following:
https://hub.unity3d.com/linux/repos/deb/dists/stable/InRelease: Key is stored in legacy t
rusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for det
ails.
Also Unity Hub is not opening. Testing on Kubuntu 22.04 Lts.

Edit: The above coment from Invector helped to open the hub.
Edit 2: Worst decision ever to turn down the app.image. More companies should use app.image as a default.

after the first two commands from their guide (at the moment), you have to migrate it out:

• list all apt keys: sudo apt-key list
• copy the last 4 characters of the pub code, so rn its 34E8243F
• then export the deprecated key into a gpg file: sudo apt-key export 34E8243F | sudo gpg --dearmour -o /usr/share/keyrings/unity.gpg
• edit the source file with your editor (nano is my example): sudo nano /etc/apt/sources.list.d/unityhub.list
• just after deb, you insert this new tag surrounded by : deb [arch=amd64 signed-by=/usr/share/keyrings/unity.gpg] ...
• now you can finally install unity hub: sudo apt update && sudo apt-get install unityhub

these steps work with a clean install of ubuntu 22.04

[xAzurian]

@tobagind

On my fedora 36 install I had the same issue and I managed to get it working after installing these two packages:

sudo dnf install openssl1.1-1:1.1.1n-1.fc36.x86_64
sudo dnf install openssl-libs-1:3.0.2-3.fc36.x86_64

Thanks, this info helped.
As of May,2022 this helped me fixed the “chrome-sandbox” error.

In Browser:
Sign In to Unity Account

#In Terminal:
sudo yum check-update
yum install openssl
sudo yum install openssl-libs
sudo yum check-update
sudo yum install unityhub

#Run UnityHub in Terminal
sudo unityhub (only sudo the first time)

[sakunix]

@Invector

How to get Hub 3.1.2 to work on Ubuntu 22.04 LTS
(solution by @tobagind )

Add this repository using the terminal:

and install

Now uninstall the hub if you have installed and install it again by following this guide:
https://docs.unity3d.com/hub/manual/InstallHub.html#install-hub-linux

it works

[MX-Pain]

@print_helloworld

after the first two commands from their guide (at the moment), you have to migrate it out:

• list all apt keys: sudo apt-key list
• copy the last 4 characters of the pub code, so rn its 34E8243F
• then export the deprecated key into a gpg file: sudo apt-key export 34E8243F | sudo gpg --dearmour -o /usr/share/keyrings/unity.gpg
• edit the source file with your editor (nano is my example): sudo nano /etc/apt/sources.list.d/unityhub.list
• just after deb, you insert this new tag surrounded by : deb [arch=amd64 signed-by=/usr/share/keyrings/unity.gpg] ...
• now you can finally install unity hub: sudo apt update && sudo apt-get install unityhub

these steps work with a clean install of ubuntu 22.04

wget -qO - https://hub.unity3d.com/linux/keys/public | sudo apt-key add -
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
gpg: no valid OpenPGP data found.

This is what I get after doing the 2nd comand from the guide.
And Update is doing a mess with the certificate validation because of tje key-desprecated.

sudo apt-key list
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
------------------------------------------------------
pub   rsa4096 2012-05-11 [SC]
      8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
uid           [ unknown] Ubuntu CD Image Automatic Signing Key (2012) <cdimage@ubuntu.com>

/etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
------------------------------------------------------
pub   rsa4096 2018-09-17 [SC]
      F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
uid           [ unknown] Ubuntu Archive Automatic Signing Key (2018) <ftpmaster@ubuntu.com>

And this is the output from sudo apt-key list

[ChanceNCounter]

@KevinWelton

We do not currently support Ubuntu 22.04 or KDE. Our supported platforms are Ubuntu 18.04, 20.04 and CentOS 7 running the X11 window server and GNOME window manager.

Having gtk deps is normal. You’ve gotta pick something.

Explicitly supporting exactly one window manager indicates that someone making decisions for your team is barely a Linux user. If you guys understood desktop Linux in the slightest, you’d regard “GNOME only” as a fireably incompetent declaration. Unfortunately, there is no suitable analogy, but I’ll do my best:

This is the difference between requiring me to have fonts that support Chinese characters (gtk dependencies) and requiring me to have my OS set to Standard Chinese (GNOME only.)

[MadWatch]

@ChanceNCounter

Explicitly supporting exactly one window manager indicates that someone making decisions for your team is barely a Linux user. If you guys understood desktop Linux in the slightest, you’d regard “GNOME only” as a fireably incompetent declaration.

Unity does not depend on GNOME. It’s just that it is only tested (officially) with GNOME. I’m using Unity on KDE and it works perfectly. I also successfully tested it or Cinnamon and I know some people use it on XFCE. I don’t mind that Unity is only tested on the GNOME desktop. It it works there it will also work elsewhere.

@KevinWelton

The biggest issue faced is the OpenSSL 1.1 dependency. This is probably what you are seeing here.

It’s been nearly 3 months since Ubuntu 22.04 was released and this issue isn’t solved yet (at least to the best of my knowledge). The worst thing is you’re going to have the exact same issue next time Ubuntu releases a LTS and next time the Cent OS devs decide to upgrade their system libraries. This is the nature of Linux, it is constantly changing.

@KevinWelton I am grateful for all the work you and your colleagues are doing on the Linux version, but please reconsider the distribution method. Flatpak, Snap and AppImage have been designed to solve this kind of library dependency problem you’re having. If you continue distributing Unity as a DEB/RPM you’re going to have library dependency problems again and again and again.

[ChanceNCounter]

@MadWatch

Unity does not depend on GNOME. It’s just that it is only tested (officially) with GNOME.

It’s only supported with GNOME, and it’s impractical to move your day job to a system where your vendors won’t provide tech support.

[sfjohansson]

Perhaps there should be a separate thread to discuss unsupported Linux distros and running unity on those

[hecker_de]

@SnowKaya

But as i said, they were refusing to offer support to those who were using non-supported distros, but still they were distributing the UnityHub to that same non-supported distros, which could backfire one time or another. We already had countless posts here on the forum of someone using Elementary on Linux Mint with some problem, but not receiving any official support since their distro wasn’t supported.

Not really related to UnityHub, but they shunned a bug-report of mine because I’m using Kubuntu on the desktop for using a different Desktop UI than they do…

[Duathphoenix]

Hey all,

I’ve followed the unity’s official instructions on installing unity hub on RHEL distros. But upon installing unityhub it kept showing a black screen, I installed openssl but that gets me to the signin page where the sign in button doesnt work. This is the error i get when i run sudo unityhub in terminal.

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Checking for update
Error: Error: ENOENT: no such file or directory, open ‘/opt/unityhub/resources/app-update.yml’
(electron) Security Warning: A WebContents was just created with both webviewTag and contextIsolation enabled. This combination is fundamentally less secure and effectively bypasses the protections of contextIsolation. We strongly recommend you move away from webviews to OOPIF or BrowserView in order for your app to be more secure

Does anyone have any idea on how to tackle this ?

[wilman_d]

Hi, I cannot find any article that solving my issue here, so i need help. I have installed Unity 2021 LTS version from Unity Hub in both of my Arch Linux and OpenSUSE. in Arch it’s work fine. but in OpenSUSE not, opening sample project (or any project with empty template) were stuck at “Importing”. I wait it for hours but nothing. at first it maybe my slow HDD. but i tried using SSD too and the result was same, it stuck. is there any workaround to make it work on another distro like my case?

[DrMeatball]

$ echo “deb Index of /ubuntu impish-security main” | sudo tee /etc/apt/sources.list.d/impish-security.list
deb Index of /ubuntu impish-security main

$ sudo apt-get install libssl1.1
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
E: Unable to locate package libssl1.1
E: Couldn’t find any package by glob ‘libssl1.1’
E: Couldn’t find any package by regex ‘libssl1.1’

22.04.1

Any ideas?

[hecker_de]

@DrMeatball

$ echo “deb http://security.ubuntu.com/ubuntu impish-security main” | sudo tee /etc/apt/sources.list.d/impish-security.list
deb http://security.ubuntu.com/ubuntu impish-security main

$ sudo apt-get install libssl1.1
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
E: Unable to locate package libssl1.1
E: Couldn’t find any package by glob ‘libssl1.1’
E: Couldn’t find any package by regex ‘libssl1.1’

22.04.1

Any ideas?

If you’re running 22.04, that’s Jammy Jellyfish. Impish Indri was 21.10.
So change the apt source to match with the rest of your system.

[markmozza]

@MadWatch

Exactly. But it’s not just that. It is much much worse than just that. Please allow me to explain.

Issue #1: Reliability
Unity is now forcing us to add a package repository to our system in order to install UnityHub. The problem is a package repository has the power to replace ANY package on the system! If Unity’s repository is badly configured (either by mistake or malice) then it has the power to destroy the entire system. Now, any time I will update my system, I will have to blindly trust that Unity didn’t made any mistake and didn’t get hacked. This is the same reason why Ubuntu’s PPA suck and why Canonical developed Snap to replace them.

When UnityHub was distributed as an AppImage there was no such problem. Installing it couldn’t harm the system.

Issue #2: Easiness
When UnityHub was distributed as an AppImage, all you had to do to install it was downloading it, right click on it and install it. That’s it, no extra step required. And yes, that takes care of the integration with the rest of the system (ie put it in the app menu and such). This is how I installed Unity on Ubuntu, Mint, Manjaro, Kubuntu and Neon. It always worked right out of the box.

Now that UnityHub is distributed as a package I have to open a terminal, become root, edit a system config file (which is different depending on the distribution I’m using), add a new line (which is different depending on the distribution I’m using), and type a bunch of commands (which are different depending on the distribution I’m using). If I make a mistake while doing it, I can screw up my whole system! How is this quality of life?

Issue #3: Other distributions and future versions of supported distributions
I know that Unity only officially support Ubuntu and CentOS and I approve of that decision. But if I want to install it on a non supported distribution that’s my problem. AppImage is a distribution agnostic method to distribute applications, it works the same everywhere. I managed to install and use Unity on a whole bunch on distributions without issue.

Now that UnityHub is distributed via a package repository there is no way to install it on a non officially supported distribution. There is also no telling if this is going to work on future versions of Ubuntu and CentOS. Package are tied to one specific version of one distribution. If Ubuntu or CentOS decided to rename some package or to change the version numbers and UnityHub depends on those package, then it won’t install anymore. Unity devs will have to constantly keep their packages up to date with the changes in their supported distribution. This is extra work for no benefit.

Packages are yesterday!
I know that packages used to be the way to distribute applications for Linux, but this is not true any more. Packages never were a good way to distribute applications to begin with. Linux developers know this. This is why they came up with new and better ways to distribute applications for Linux, namely AppImage, Flatpak and Snap. Unity devs don’t have to support them all, they only have to choose the one that fit their needs best.

AppImage was a fine choice. If, for any reason, Unity devs were not satisfied with it, they could just have picked Flatpak on Snap instead (I know that many people dislike Snap for various reasons but it works and that’s all that matter here). Distributing UnityHub via a package repository is a HUGE step back. This is not quality of life, it’s trouble for everybody, including Unity.

Please Unity, reconsider your decision.

Completely Disagree. Most of us who develop use a LTS version of Linux and a well supported version. Outside of that no one cares. Ubuntu and CentOS are the most used platforms to Develop on so choose one of them. You cant expect support for every distro, thats insane.

Using AppImage is a horrible not native experience, its a work around. Packages are yesterday? Composer? Npm? HomeBrew? They are all package managers. Also most LONG term Linux users do NOT like AppImage, Flatpak and especially Snap (First thing i removed on Ubuntu 22.04).

[ChiwTheNeko]

@markmozza

Most of us who develop use a LTS version of Linux and a well supported version. Outside of that no one cares. Ubuntu and CentOS are the most used platforms to Develop on so choose one of them.

And yet Unity still doesn’t support the latest Ubuntu LTS that was released 8 months ago because of one library change. It also still doesn’t support Cent OS 8 and 9 (I assume for the same reason). The problem isn’t that Unity don’t support every distro under the sun. The problem is Unity can’t even support the LTS distros it says it’s going to support.

And that stupid compatibility problem with LibSSL under Ubuntu 22.04 would not have happened if Unity was packaged with Flatpack or Snap or Appimage. These packaging systems are designed to avoid this kind of issues. Why not just use them?

[markmozza]

@ChiwTheNeko

And yet Unity still doesn’t support the latest Ubuntu LTS that was released 8 months ago because of one library change. It also still doesn’t support Cent OS 8 and 9 (I assume for the same reason). The problem isn’t that Unity don’t support every distro under the sun. The problem is Unity can’t even support the LTS distros it says it’s going to support.

And that stupid compatibility problem with LibSSL under Ubuntu 22.04 would not have happened if Unity was packaged with Flatpack or Snap or Appimage. These packaging systems are designed to avoid this kind of issues. Why not just use them?

Linux is way faster at releasing distro versions, you should be happy this exists, you get cutting edge constantly, yet people complain, Windows 10 was released in 2015, it 7 years old, Windows 11 is out yet only 23% of windows user use it, 75% is still Windows 10. Ubuntu 15.04 was release in 2015… 16.04 LTS in 2016, you get my point right. This is one Distro of Linux with several major versions released in the single life span of Windows 10, how do you expect developers to keep up. LibSSL issue lies within Ubuntu not Unity, you were not forced to the newer version. Just because its an LTS doesnt mean that its going to be backwards compatible, it just means it will be supported going forward.

Use a well supported version and you will be fine.