That’s what automated CI/CD build piplines are supposed to be for…
What irks me more is how Unity-Hub 3.x is relying on doing some OAuth2 stuff through the web-browser in order to login to Unity. On my desktop machine (at a time I accidentally got the 3.x-beta installed) this never worke (so I reverted to the 2.4.x version of the hub)
On my laptop the 3.x release acutally did work (but popping up a new tab in Firefox is rather quirky), but for some reason I haven’t solved yet, after some updates and rebooting it is combletely borked now!
The application starts, but most of the time doesn’t show its window, or I get an empty one. If I run the old AppImage 2.4.x hub (which is also still on my machine), it may decide to open, but lost all of the configurations, and when I select login I get an empty window and cannot login.
I already tried dpkg-reconfigure as well as apt reinstall unityhub, but no success.
The fun continues, but somewhat differently…
I have the Hub running.
I am logged in.
I open a project from the list in the Hub.
Unity opens (2020.3.28f1, I just installed the update and bumped the version for this project).
Unity Editor shows as not logged in and when I click on the login option I get prompted to install the Hub.
I’m going to join the plea for Unity, please reconsider using a distribution agnostic packaging format, Flatpak, AppImage or Snap. Every one of those, especially Flatpak and Snap would be miles more user friendly to install for Ubuntu users, than the PPA-deb approach, with the added benefit of not restricting possible users to those supported distributions. You can still keep officially supporting only those distros.
Will you try using flatpak? Or even Snaps? Use one of these and you’ll only have to maintain one package for ALL distros, you get the best quality, and best compatibility.
It works OK in EndeavourOS (Arch based) because there’s someone voluntarily maintaining it in the Arch User Repository. You just install it with “yay unityhub”.
But I personally saw nothing wrong with the AppImage, it always worked. I wonder why they decided to do that? It shouldn’t be hard to provide a small explanation with the announcement…
I am currently using Mageia linux 8. Even though it is not an officially supported linux distro, the AppImage installer worked without issue, and Unity ran with no issue.
While I have been able to add the UnityHub repository to Mageia, the .rpm will not install because it is built for specifically for another distro.
sudo dnf install unityhub gives the following:
Error:
Problem: conflicting requests
nothing provides gtk3 needed by unityhub-3.0.1-1.x86_64
nothing provides libXtst needed by unityhub-3.0.1-1.x86_64
nothing provides libuuid needed by unityhub-3.0.1-1.x86_64
nothing provides gtk3 needed by unityhub-3.1.0-1.x86_64
nothing provides libXtst needed by unityhub-3.1.0-1.x86_64
nothing provides libuuid needed by unityhub-3.1.0-1.x86_64
nothing provides gtk3 needed by unityhub-3.0.0-1.x86_64
nothing provides libXtst needed by unityhub-3.0.0-1.x86_64
nothing provides libuuid needed by unityhub-3.0.0-1.x86_64
nothing provides gtk3 needed by unityhub-3.1.1-1.x86_64
nothing provides libXtst needed by unityhub-3.1.1-1.x86_64
nothing provides libuuid needed by unityhub-3.1.1-1.x86_64
(try to add ‘–skip-broken’ to skip uninstallable packages)
Idly wondering since the hub is an actual .deb/.rpm package now, if it would work better under FreeBSD using the linux compatibility layer which is based on CentOS.
Although i understand the frustration for not having how to install Unity on other distros (except the unityhub-beta aur for Arch/Manjaro) and also being affected by this (i really wanted to try Fedora, but it won’t be this time), i understand why Unity made this change.
Even when the Hub was distributed by .appimage, they only stated that they were only supporting Ubuntu LTS, which is wrong both technically and legally. Since UnityHub is distributed in a universal format, technically they are also obliged to support whoever was with problems.
And “supporting” doesn’t only mean making the application be in a functional state, it also means troubleshooting/helping someone when they are facing a error in the app.
And because the vast majority of differences some distros can have because of countless factors, it’s easier for them to only support one or another of the most used distros, which happens to be the base of other equally famous distros.
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.
Again, i ain’t happy with this either, but technically Unity isn’t wrong, but i also would like to see that flatpak version of UnityHub being the official one.
Hello.
I have an issue installing the Unity Hub on the latest 22.04.
When I try to open the Hub, nothing happen.
When I run it via the terminal, nothing happen.
I do have an issue if I wait for a long time:
Bug report does nothing.
When I installed the hub, I had this issue, idk if it’s relevant or not.
Got a problem with the Hub. I manually downloaded a unity editor tarball from the archive, uncompressed it and tried to add it to UnityHub using the Locate button but it doesn’t add it properly, it just imports it with the name of the parent folder of the editor, so if the directory structure is like:
MyUnityEditor
Editor
Files…
unity (as such, no extension) file
And I try to load that “unity” file, a dummy install is added to my list of editors as “MyUnityEditor”, no version number, so I can’t use it. Please help!
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!
