Package Details: unityhub 3.15.2-1

Git Clone URL: https://aur.archlinux.org/unityhub.git (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: https://unity.com/
Keywords: game unity3d
Licenses: custom
Conflicts: unityhub-beta
Submitter: spacepluk
Maintainer: nobbele (sinasio)
Last Packager: sinasio
Votes: 95
Popularity: 1.80
First Submitted: 2018-08-31 12:14 (UTC)
Last Updated: 2025-11-08 16:41 (UTC)

Latest Comments

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

WeanWind commented on 2025-11-24 17:49 (UTC)

Version 3.15.2-1 does not recognize installed plaforms. It will be fixed in 3.16.0+

Details: https://discussions.unity.com/t/unity-editor-does-not-recognize-installed-plaforms/1692184/10

totemfallico commented on 2025-11-22 15:14 (UTC)

I managed to get it running on hyprland by installing gconf from AUR. I tried to launch a specific project from cli and it says that it was missing lib-gconf.so.4 or something like that. After installation everything seems to be working properly!

3D_Daxter commented on 2025-11-15 16:55 (UTC) (edited on 2025-11-15 16:55 (UTC) by 3D_Daxter)

Okay for me its the editor/engine version 6000.2.12f1 that is having this issue. The lts version and the newer BETA version works fine.

3D_Daxter commented on 2025-11-15 13:31 (UTC) (edited on 2025-11-15 14:02 (UTC) by 3D_Daxter)

Maybe the information helps that only works on gnome for me not on i3 or hyprland. According to the segfault there seems to be a problem with libgobject2.0.so (provided by glib2).

My guess is some new glib2 or unityhub/Editor update broke compatibility with unityhub/the editor outside of gnome. Even though that would be wired since when the problem stated to occur I could actually open an older project.

lufog commented on 2025-11-14 15:01 (UTC) (edited on 2025-11-14 15:04 (UTC) by lufog)

I think it would be nice to add a couple of extra files to the Unity Hub package. The first one is the Unity Editor icon, and the second one is a Unity Editor desktop entry:

Unity.desktop

[Desktop Entry]
Type=Application
Version=1.0
Name=Unity
NoDisplay=true
Comment=Unity editor
Icon=unity-editor
Terminal=false
Categories=Development;
StartupWMClass=Unity

This desktop entry doesn't appear in the apps grid/menu. Its sole purpose is to bind an icon to the editor in a Wayland session. This ensures that the Unity Editor icon appears in the taskbar/dock instead of the standard gear icon.

kenshiwara commented on 2025-11-13 01:54 (UTC)

@silver456 — Unfortunately, I haven't been able to solve the issue despite trying almost everything. I even consulted the top three leading paid LLMs for assistance, but they all failed to provide a useful solution after long hours of suggestions.

The core problem is a segmentation fault. I am currently running Manjaro Linux KDE.

silver456 commented on 2025-11-12 18:19 (UTC)

@kenshiwara I get the same error, and my project folder is empty.

sinasio commented on 2025-11-09 15:29 (UTC)

@kenshiwara I confirm that I can create and open any new or old project.

kenshiwara commented on 2025-11-09 11:51 (UTC)

@sinasio — The Unity Editor fails to create a new project on my machine (segmentation fault), which is why it refuses to open it, showing an error message that it’s already open. I also couldn’t find any UnityLockFile (under any name variation) anywhere on my system.

Could you please confirm whether you’re able to create and open new projects? Any confirmation from any user, in fact, would indicate that the problem is specific to my machine and not related to the package.

Thanks in advance for checking!

sinasio commented on 2025-11-09 10:45 (UTC)

@kenshiwara From the project's root dir, try to delete the file "Temp/UnityLockfile" and then open the project again

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