Arch Linux User Repository

I'm on Arch + yay too, not sure what your setup might be but the problem seems to be related to the fakeroot: AppImage tries to use root-owned directories and buses and obviously can't, while with my fix it will try to use the regular user-owned ones and therefore succeeds. Maybe you have something configured that makes AppImage play nice with fakeroot.

Hi there! Thanks for tracking this down. We're in the middle of releasing a game and I'm a bit overwhelmed atm.

Are you both using Manjaro? It seems to work fine on Arch + yay.

Thanks!

I found the problem!!

The AppImage --appimage-extract operation fails because it's done inside of the package() function, which is run in the fakeroot. Instead, the extract step should be run during build(), which is run by the local user.

The following is the diff I get from git when updating the PKGBUILD to work this way:

diff --git a/PKGBUILD b/PKGBUILD
index [`b657e5e`](https://aur.archlinux.org/cgit/aur.git/commit/?h=unityhub&id=b657e5e)..552d036 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -11,7 +11,7 @@ source=("${pkgname}-${pkgver}.AppImage::<https://public-cdn.cloud.unity3d.com/hub>
 md5sums=('7cbff634d574a4e6da02fd1ce15bf2cb')
 PKGEXT='.pkg.tar'

-package() {
+build () {
   # Extract AppImage
   chmod +x "${pkgname}-${pkgver}.AppImage"
   "./${pkgname}-${pkgver}.AppImage" --appimage-extract
@@ -21,8 +21,11 @@ package() {
   sed -i "/^Exec=/cExec=unityhub" "${_df}"
   sed -i "s/^X-AppImage-Version=/Version=/" "${_df}"
   sed -i "/^X-AppImage/d" "${_df}"
+}

+package() {
   # Install
+  _df="${srcdir}/squashfs-root/unityhub.desktop"
   install -d "${pkgdir}/usr/share"
   install -D ${_df} "${pkgdir}/usr/share/applications/unityhub.desktop"
   install -D "${srcdir}/squashfs-root/usr/share/icons/hicolor/48x48/apps/unityhub.png" \

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

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.

Hey, md5sum is incorrect

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

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

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!