Can not create new project in Unity Hub - Linux

I just downloaded a editor in the Unity Hub interface (2019.2.19f1) but the created project does not exists in the path.

The folder is just empty. Just tried to use different paths but stills not creating. If I close the Hub and open again the list of projects shows empty.

I’m on Linux Mint 19.1 (Ubuntu 18.09) and using latest version of Unity Hub (2.2.2?) downloaded as AppImage.

Is this Hub uncompatible with my Linux or is this a known bug? Didn’t found some solutions until now.

Thanks in advance!

I am running into the same issue, but on Pop_OS! (19.10).

I was running into the same problem but I finally found it to be nothing but an issue of my own impatience! Try letting go of your computer as soon as you hit “Create” and check after 10 mins or so - it seemed to not have created anything for me and then finally after 10 minutes or so, Unity began opening!

The solution can’t possibly be “wait 10 minutes”. Has anyone found a proper solution? Or at least an explanation?

Same here XUbuntu 20.04
It looks like this is a fix:

  • Open unity
  • Select “Installs” on the left panel
  • remove whatever was there before
  • “Add” a new one - whichever you like
  • NOW create a new project.
  • After creation the unity window closes and it looks like it crashed. But after a few seconds another unity window will open

I guess this is the problem:

  • You did not setup any (proper) “Installs”

I had a similar issue running on Arch. It appears that older versions of Unity (at least up to 2019) require gconf to work. After installing the gconf package, I could make projects just fine.
(Very late reply I know)

This feels like the meme where there are 4 panels and the last one is you guys got it to work at all? I’m on Arch, a while ago I took a break…fast forward a few months fired up Unity and nothing worked. Last while I’ve tried Win7 and XUbuntu (22.04) and I can’t get anything to work. Hub3 opens to either blank window or just crashes. I can get Hub2 (appImage) to open and kinda work but installing editors constantly fail. If it finally works I get two blank errors on new projects or old and a dead end to an unfixable safemode.

** @souluquinha ** to stay on topic I notice you are also using Hub V2 but I’d say you’re having an issue with your project name. Notice how you have “New Unity Project?” Unity can’t handle POSIX filesystems still so I bet if you either rename it “new unity project” or make a symlink to the lower cased name in the same root folder it will work. I constantly have to rename or fix crap like that.

I will say just installing gconf is just more than a bad idea. For example of xfce4 you will see there is already a dconf which works just like gconf. Conflicts are expected. Newer versions of unity can use dconf and gconf as well.
Ultimately if you really need unity 2019 or older, use the gnome desktop environment for your project.

I just solved this.

So first try to run your Unity command in the terminal.
It should be located in ~/Unity/Hub/Editor/{version}/Editor/Unity

Run this and see if any errors pop up for me it was,
╰λ /home/drew/Unity/Hub/Editor/6000.0.48f1/Editor/Unity
/home/drew/Unity/Hub/Editor/6000.0.48f1/Editor/Unity: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory

So for me the issue isn’t that I didn’t have libxml2 installed I just had the wrong version.

╰λ ls /usr/lib/libxml2.so*
/usr/lib/libxml2.so /usr/lib/libxml2.so.16 /usr/lib/libxml2.so.16.0.2

Since nothing else uses libxml2.so.2 I just linked the library to the .16 version using this command.

sudo ln -s /usr/lib/libxml2.so.16 /usr/lib/libxml2.so.2

And voila! You may now create projects.
Honestly the AUR should probably be updated to install the correct version.

That worked for me too, thanks man!

Even in 2025 with Unity 6 and 6.2…

In my case I was able to download libgconf-2.so* from the Arch Linux archives, you can extract the contents of /usr/lib to your /usr/local/lib folder and force Unity Hub to load it by adding LD_LIBRARY_PATH=/usr/local/lib to the launch env vars.

In case anyone else struggles with this on SUSE systems, the solution is to create a link for libxml2 in /usr/lib64/ (not /usr/lib/) like this:

well ya man that worked, i was first confused why im do creating project but they not showing in files , creating symbolic link fixed it thanks alot