-
Notifications
You must be signed in to change notification settings - Fork 12
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
Fontconfig error #68
Comments
I am on 19.10 beta and am getting a similar Fontconfig error:
After a short pause, PyLNP launches but the smallest font imaginable! |
At least it's readable for you. wheezing With the Disney font, I have to guess everything. |
Doesn't work on Ubuntu Mate either :( I had some serious DF plans for this weekend :( |
You could try running PyLNP from source, if you have Python installed: https://bitbucket.org/Pidgeot/python-lnp |
WORKS! File building.rst in directory /docs in the source explains how to run it.
|
This happens to me as well on Arch Linux. |
Hello, I am facing the same problem as @JamesJOliver, regarding fontconfig errors and font size of the gui. I am running the pack on Fedora 33. Any way to force the application to use a specific font with a given size, through the ".Xresources" file maybe? I am using a 42" screen with a 4k resolution, so imagine the pain to my eyes when trying to read texts in the interface. |
Hello, With version 0.47-04, the fontconfig errors does not show up anymore. However, I have still the tiniest font ever. I have also noticed that |
Just an issue I notice since I updated to ubuntu 19.04. I haven't played dwarf fortress in a while and I decided to load it up using the lazy newb pack. I load it up in the terminal, and I get this error:
It takes a while to load, but eventually PyLNP does load up, but in the worse font imaginable. Wheezing. The font used in Disney logos. I can deal with it just fine, but perhaps the newb pack needs an update for newer distros? It seems like ubuntu 19.04 does something different with fontconfig.
The text was updated successfully, but these errors were encountered: