Package Details: unityhub 2.1.2-1

Git Clone URL: https://aur.archlinux.org/unityhub.git (read-only)
Package Base: unityhub
Description: The Unity Hub is a standalone application that streamlines the way you find, download, and manage your Unity Projects and installations.
Upstream URL: None
Licenses: custom
Submitter: spacepluk
Maintainer: spacepluk
Last Packager: spacepluk
Votes: 13
Popularity: 0.809119
First Submitted: 2018-08-31 12:14
Last Updated: 2019-09-18 08:57

Latest Comments

1 2 3 4 Next › Last »

SorcererSupreme commented on 2019-10-11 21:54

Similar issue as @Darkhogg

Using manjaro with yay.

QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
Failed to connect to bus: Operation not permitted
Failed to connect to bus: Operation not permitted
Failed to create /root/.cache for shader cache (Permission denied)---disabling.
==> ERROR: A failure occurred in package().
    Aborting...
Error making: unityhub

Darkhogg commented on 2019-10-11 13:03

I'm having the same problem @thunderingMarmot described, with the following logs:

==> Starting package()...
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0

(AppImageLauncher:53713): dbind-WARNING **: 14:59:27.931: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to connect to bus: Operation not permitted
Failed to connect to bus: Operation not permitted
Failed to create /root/.cache for shader cache (Permission denied)---disabling.
==> ERROR: A failure occurred in package().
    Aborting...

and the "Failed to register AppImage in AppImageLauncherFS: error while trying to start appimagelauncherfs.service" popup dialog.

This is all happening with the --appimage-extract command, which is weird because I have other AppImage packages installed (I maintain one myself, even) that give me no such problems.

HunabKu commented on 2019-09-18 07:45

Hey, md5sum is incorrect

HunabKu commented on 2019-09-15 07:24

https://public-cdn.cloud.unity3d.com/hub/prod/UnityHub.AppImage 012c855e84965e5fb3d52a36677ccfdf

codeandgin commented on 2019-09-07 23:32

The UnityHub source location has changed, and the validity check isnt working for me.

Aargonian commented on 2019-09-05 05:02

Hello, I would just like to first say thanks for providing the package!

I do have an issue, though. unityhub appears to be able to install the 2019.1 editor just fine, and create a new project, but it failed when I attempted the same with the 2019.2 editor. The failure appeared to be silent, as the hub interface would simply disappear, as though it was about to start the editor on the new project, but the editor never opened. The folder for the project was never created, but unityhub itself was still running in the background and I had to use the kill command to kill it. Is this a known issue or a fixable issue?

If there is an upstream repository for the hub, I'd be happy to report this there, but my google-fu must be badly lacking as I couldn't find it. Either way, at least it seems to work for 2019.1!

RavianXReaver commented on 2019-08-07 20:29

Any solution ?

==> Making package: unityhub 2.0.4-1 (Thu Aug 8 01:58:58 2019) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found unityhub-2.0.4.AppImage ==> Validating source files with md5sums... unityhub-2.0.4.AppImage ... FAILED ==> ERROR: One or more files did not pass the validity check!

haekel commented on 2019-07-20 07:05

Hello, first of all, thank you spacepluk for packaging all the Unity things! <3

This might be a problem in unityhub itself, but for some reason, I keep having the problem that the Unity versions I install using unityhub (2018.4.4, but others are affected as well) are missing the Mac build support, regardless of whether I install the "Mac Build Support (Mono)" component or not. The corresponding folder under PlaybackEngines does not get created and trying to build a Mac version fails. Exporting to Windows and Linux work fine. Installing Unity using the unity-editor-* packages and not unityhub works fine for Mac/Win/Linux as well.

I'm grateful for any insight or workaround. Thank you in advance!

thunderingMarmot commented on 2019-07-11 15:25

I don't know if it's me but I tried installing others AppImages and everything works fine... So, the problem is:

==> Starting package()...
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
Failed to connect to bus: Operation not permitted
Failed to connect to bus: Operation not permitted
==> ERROR: A failure occurred in package().
    Aborting...
:: failed to build unityhub package(s)
It also had a popup message that said: "Failed to register AppImage in AppImageLauncherFS: error while trying to start appimagelauncherfs.service"

I'm using Manjaro Linux 18 with KDE, Octopi (as GUI for Pacman) and Yaourt for AUR.

I'm really sorry if the cause of this problem is me and not the package but I'm still learning Arch Linux and I just discovered this whole AUR thing.

ahub commented on 2019-07-11 14:46

For some reason it won't launch after installation (no errors during makepkg process)

unityhub
fish: “unityhub” terminated by signal SIGSEGV (Address boundary error)
sudo unityhub
No protocol specified

Analysing the core dump it has to do with XDG_CONFIG_DIRS. Unsetting the environment variable seems to fix the issue.