-
Notifications
You must be signed in to change notification settings - Fork 299
panic: Cannot create a label with a nil font #13
Comments
argh. So I added some code to look for fonts in the directories specified by FontPaths, I'm guessing Arial.ttf isn't in any of those places? Maybe it is, but has the wrong case? |
Evidently I have no Arial.ttf. Run as root: I'm running Xubuntu 14.04. I do have a bunch of fonts in
|
You should consider installing the ttf-mscorefonts package. |
@StefanSchroeder: I'd rather not if I can avoid it, because it requires accepting a Microsoft EULA. I'll leave it up to @ben-clayton -- if you want me to leave my machine in its current state to test a potential fix, I'll leave it alone. If you want me to install the Microsoft package so no further work is needed, I'll do that to save the effort, since it's not my effort. |
I'm not sure what the best option is in this case.
I can start investigating what our options are with a bundled font. In the meantime, to run the samples you should be able to take any font you like, rename it to Arial.ttf and set |
Thanks for that info, @ben-clayton. I'm sure I can make it work by installing the font, using the workaround you suggested, or forking and adding a font I have as an option. Feel free to close this issue if you think it's a narrow part of the bigger |
I am attempting to run on Mac 10.10.2 and getting the same error. I definitely have Arial on my machine. |
@ryanseys Please report the full path to |
I copied |
I'll keep this issue open as a 'we need bundle a font' issue. It's good to keep the context why. |
This should now be fixed as we bundle a font. Please let us know if you have more issues. |
Confirmed: The progress_bar sample runs on my Xbuntu 14.04 machine, without the MS font package. Thanks! |
That's great news - thank you for confirming! |
I was able to succesfully build the
progress_bar
binary from the samples folder using the Dockerfile described in #7. However, when I run the binary on my machine I receive the following panic:The text was updated successfully, but these errors were encountered: