Arch Linux User Repository

I don't recall having this with older Unity versions, but with 2021.3 UI elements with TextMeshPro text tend to not render their text at all. This seems to happen because the default font is "Arial", which is supposedly a "Built-in resource" in Unity. If you set the font explicitly to a font in your project or on your system, it works fine.

I also found that actually installing Arial separately (e.g. AUR package ttf-ms-fonts) fixes the issue without making changes to your project, in case this helps someone. Maybe it's worth adding this package as optional dependency?

This still smells like a Unity issue though - they should provide a font so it's always available, or use or fallback to one that is.

Hi @sinasio, I was having an issue with unity on Arch. Using the Online Unity Asset Store (https://assetstore.unity.com/) appears to not work. After the Open in Unity button is clicked, the following message is printed to the browser logs: ""kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/com.unity3d.kharma" not found".

@BujuArena I see, thank you for your insights.

Without switching away from Manjaro to a distro which uses Arch repositories, the more viable alternative to Manjaro stable is Manjaro unstable. Like I said though, even Manjaro unstable could have any number of unexpected differences, since it is not Arch stable.

@BujuArena I know about this discrepancy but so far I have only encountered a few issues which were usually fixed by simply downgrading the AUR package. If you say don't try to use it, are there any alternatives? I mean anything more safe or stable than just manually retaining updates from the AUR if necessary? The AUR is amazing and one of the big reasons I chose Manjaro to begin with so I'll want to keep using it.

Please don't try to use Manjaro stable with the AUR. The AUR is for Arch stable, which is ahead of Manjaro unstable (without even mentioning that it's a completely different repository, so it could have any number of unexpected differences). Manjaro stable is so far behind that it's guaranteed to break on changing dependencies often.

@sinasio Thanks! I'm sure it will solve it for Manjaro eventually but currently the package is only available on the unstable branch of Manjaros updates meaning it will probably take a week or two until it hits stable. Fortunately the issue that prompted the addition of the dependency in the first place seemingly has not yet hit stable either so in the end it'll probably all work out and until then I can just stay on unityhub 3.3.0-1.
Ps. Thanks for the addition of the dependency, I'm sure it's a good change. It should not be your responsibility to deal with issue coming from Manjaros update retention.

@Joelius300 I can see the openssl-1.1 packages here: https://packages.manjaro.org/?query=openssl

Looks like it was added recently :D Does it resolve your issue?

FWIW the addition of openssl-1.1 as a dependency makes it impossible to install on my Manjaro system (impossible is a hard word; pacman, pamac and yay cannot handle the situation at least not without some flag I don't know about).

It seems that none of the packages openssl, openssl-1.0, lib32-openssl and lib32-openssl-1.0 provide openssl-1.1 (and openssl and lib32-openssl are both on version 1.1.1.q-1). I had to manually install unityhub 3.3.0-1 and didn't face any issues or crashes whatsoever.

@attishno1 @Lexito thanks for the update. I'll add openssl-1.1 to the dependencies, as the package fixes the problem.

The issue is known by Unity devs: https://forum.unity.com/threads/workaround-for-libssl-issue-on-ubuntu-22-04.1271405/#post-8098841 Hopefully they'll fix the issue one day :D