-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesnt load fonts #31
Comments
Try the solution in #30 : |
|
Same. Ubuntu 22.04 |
No help with this? |
The solution is in one of the other threads, can't recall which. I went back to Mac after all, so can't help. |
@Skyyy777 you might want to look into this other similar project #14 (comment) |
Unfortunately I don't have any great ideas. I would try deleting all the files and services associated with the previous installation. I believe (on my machine) these are the locations to delete
Then try installing fresh:
|
💯️ It tottally works man !!!Figma should support this project. I just "uninstall" and install fresh as described avobe, added my When i hit |
Thanks, It works. |
A few notes on how to make it work: Avoid directory paths containing {
"port": "18412",
"directories": [
"/usr/share/fonts",
"/home/<USERNAME>/.local/share/fonts"
]
}
The install script fetches the latest release, which is at the time of writing over 2 years old. But you can easily build the project by your self locally. Rust + toolchain required. Just clone the repo, build the release version with git clone [email protected]:Figma-Linux/figma-linux-font-helper.git
cd figma-linux-font-helper
cargo build -r
mv target/release/font_helper /opt/FontHelper/fonthelper
systemctl restart fonthelper.service To make the install script work out-of-the-box, a new release needs to made. |
Had the same issue, the steps above fxed it. |
sudo nano /home//.config/systemd/user/figma-fonthelper.service |
and
made things work, thanks! ❤️ |
Hey, I get a 500 Internal Server Error when Figma tries to load fonts. Am I doing something wrong?
The text was updated successfully, but these errors were encountered: