Nixpkgs version

• Stable (25.05)

Describe the bug

Many UI's in Unity load partially, or not at all due to the failure to load Liberation Sans. In cases such as the asset store, this prevents the loading of most the UI, rendering it unusable. This bug is reproducible with with assets that load game UI as well. Produces an error in the console with the text "Unable to find a font file with the specified Family Name [Liberation Sans] and Style [Regular]. UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /home/bokken/build/output/unity/unity/Modules?IMGUI/GUIUtility.cs:2003)", and double clicking this error produces a pop up with the error "/home/bokken/build/output/unity/unity/Modules/TextCoreTextEngine/Managed/FontAsset.cs does not exist.". The console error reoccurs every time an affected UI element is moused over.

Steps to reproduce

(KDE Plasma 6.3.5, Nvidia Proprietary Drivers, x86)

1. Download and install editor version 2022.3.22f1 through the "Installs" menu.
2. Use this editor version to create a new project.
3. Attempt to open the Asset Store through the Window drop down in the top toolbar. The Asset Store will appear similar to the attached image.

Expected behaviour

Asset Store and font-dependent UI should load and display all UI elements.

Screenshots

Console entry:

Popup created by double-clicking console entry:

The Asset Store appears as this while affected by this bug:

Relevant log output

Additional context

• This bug occurs even if the Liberation Sans font is installed on the system.
• There is indeed no folder named "bokken" under the main /home directory. To clarify, this is not my username.

System metadata

• system: "x86_64-linux"
• host os: Linux 6.12.30, NixOS, 25.05 (Warbler), 25.05.20250526.7848cd8
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.28.3
• channels(root): "nixos-25.05, nixpkgs-unstable"
• channels(moonclip): ""
• nixpkgs: /nix/store/2d4cws3k4ypb9kvln8qh8ikpd5j5r89l-source

Notify maintainers

@tesq0
@huantianad

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.