Package Details: unityhub 2.3.2-1

Git Clone URL: (read-only, click to copy)
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:
Keywords: game unity3d
Licenses: custom
Submitter: spacepluk
Maintainer: mglo
Last Packager: mglo
Votes: 28
Popularity: 2.19
First Submitted: 2018-08-31 12:14
Last Updated: 2020-05-31 12:54

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Qwertystop commented on 2020-07-25 15:25

Having an issue with the hub — attempting to use it install versions other than the ones provided directly in the hub, through Unity's download archive, isn't working. Specifically, the Unity Hub links on result in Unity Hub opening, gaining focus, and not actually downloading anything. The log file it keeps is not changed by this attempt and it doesn't seem to make any network requests as a result. Any idea? My web browser is Firefox and my desktop environment is Xfce, if that's relevant. The versions the hub can install work fine, as did downloading the older version manually by grabbing the tarball link out of the relevant PKGBUILD from [unity-editor]( and then pointing Unity Hub at the extracted files as a version installed separately.

m0cha commented on 2020-05-26 13:35

You have to change "${pkgdir}/opt/${pkgname}/unityhub-bin" into "${pkgdir}/opt/${pkgname}/unityhub" at line 53 in the PKGBUILD, otherwise you will get the error like "'unityhub/unityhub-bin': No such file or directory"

ShayBox commented on 2020-05-10 05:21

To solve the problem of the pinned comment, you have to skip verification, if the source isn't static you shouldn't be be verifying it per the pkgbuild guidelines.

Qjammer commented on 2020-04-17 08:21

The executable doesn't launch from the launcher because the launcher script (which can be found by running $which unityhub) is borked. In particular, the shebang is borked. It has a space between # and !, making it not run. Removing this space fixes it. This is why it launches properly from the console but it doesn't from a .desktop, running it on the console implicitly runs it in bash.

feuerpanda commented on 2020-04-04 00:36

For some reason, you can't execute unityhub out of an .desktop file.

HunabKu commented on 2020-03-14 13:01

Waiting spacepluk upgrade the package, i do it :!iZ5UnCxY!OdlJQg-rsBpgyyiD8O_wFqZAa2J-j4Z82OMT8XA8GZ0

The fixes :


  • correct the md5sum or SKIP it

  • touch the src/squashfs-root/eula.txt file


  • replace SCRIPT_DIR line in /usr/bin/unityhub by SCRIPT_DIR=/opt/unityhub

  • chmod /opt/unityhub/unityhub-bin

kaizen commented on 2020-03-09 11:27

New md5sum is d7cb21611e5f77fb6ebe03b01efd6ded Lines with eula needs to be removed in the pkgbuild

rosebeats commented on 2020-03-09 03:07

Following along with what Raymo said, I found that if I edit /usr/bin/unityhub and added SCRIPT_DIR=/opt/unityhub and cd $SCRIPT_DIR, unityhub opens like normal.

emmanuell2025 commented on 2020-03-09 02:28

After doing the steps shown below, I found that editing the desktop shortcut (I use KDE Plasma, so I used kmenuedit) from "unityhub" to "unityhub &" made the desktop shortcut work EDIT: Just discovered that the unityhub-bin process isn't being stopped when I close the unityhub window, not sure if it's a result of my change to the launch or a change with unitythub

Raymo111 commented on 2020-03-04 14:03

Lines containing eula.txt need to be removed, or package() will throw an error (eula.txt not found). Upon install, /usr/bin/unityhub must be edited. Change exec "/usr/bin/unityhub-bin" on line 8 to exec "/opt/unityhub/unityhub-bin". Then run sudo chmod +x /opt/unityhub/unityhub-bin. Even then, the .desktop file doesn't work, and you have to run unityhub in a terminal.