Skip to content
This repository has been archived by the owner on Dec 30, 2024. It is now read-only.

Fonts don't load in Arch/Manjaro #11

Open
kenballus opened this issue Aug 4, 2020 · 12 comments
Open

Fonts don't load in Arch/Manjaro #11

kenballus opened this issue Aug 4, 2020 · 12 comments

Comments

@kenballus
Copy link

This is a great tool; thanks for making it.

Running the latest binary on a fresh Manjaro install gives the following errors:
Fontconfig warning: "/etc/fonts/fonts.conf", line 5: unknown element "its:rules" Fontconfig warning: "/etc/fonts/fonts.conf", line 6: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/fonts.conf", line 6: invalid attribute 'translate' Fontconfig error: "/etc/fonts/fonts.conf", line 6: invalid attribute 'selector' Fontconfig error: "/etc/fonts/fonts.conf", line 7: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/fonts.conf", line 7: invalid attribute 'version' Fontconfig warning: "/etc/fonts/fonts.conf", line 9: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/45-generic.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/49-sansserif.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/51-local.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/60-generic.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/65-nonlatin.conf", line 4: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/70-no-bitmaps.conf", line 8: unknown element "description" Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf

A screenshot:
image

Using the script does not have this problem.

@noirscape
Copy link

Your fontconfig file isn't properly set up. This isn't a fusee bug.

Please reference the Arch wiki for more on how to fix it or try to fix this issue on the Manjaro forums.

@oreo639
Copy link

oreo639 commented Aug 12, 2020

I'm confused. Was this an issue with your fontconfig? It seems like the version of fontconfig bundled with v1.0.1 (2.12.6) is too old to support 2.13.x font configs.

(Just a note, the v1.0.0 version was built with a newer fontconfig so it should work just fine for you)

@Traace
Copy link

Traace commented Aug 21, 2020

@oreo639 is right here. Newer versions of fontconfig shipped with arch (also manjaro) are not compatible with 2.12.6. I'm getting the same error. fusee-interfacee-tk version 1.0.0 works just fine 👍

@kenballus kenballus reopened this Aug 21, 2020
@kenballus kenballus changed the title Fonts don't load on Manjaro Fonts don't load in Arch/Manjaro Aug 21, 2020
@lucasmb
Copy link

lucasmb commented Aug 22, 2020

Had the same issue,

this fix makes the fonts rendering.
https://forum.snapcraft.io/t/snapped-app-not-loading-fonts-on-fedora-and-arch/12484/27

but the console errors and warning are still there

@kenballus
Copy link
Author

Had the same issue,

this fix makes the fonts rendering.
https://forum.snapcraft.io/t/snapped-app-not-loading-fonts-on-fedora-and-arch/12484/27

but the console errors and warning are still there

This fixed for me too! It took a few minutes to take effect, though.

@sczther
Copy link

sczther commented Sep 26, 2020

Happens on latest Fedora too

@noirscape
Copy link

Again this is not a fusee bug.

This is a bug with how your distros are handling fontconfigs cache.

Don't report it here.

@ghost
Copy link

ghost commented Nov 20, 2020

Again this is not a fusee bug.

This is a bug with how your distros are handling fontconfigs cache.

Don't report it here.

If I'm looking at everything correctly, it's either an issue with ttk.style at line 32 in app.py, or it's an issue with tkinter.feildialogue, as these seem to be having issues parsing fonts correctly in Arch. You aren't wrong, it's not an issue with your app directly, but you're also not being helpful as you're not really looking into the issue and claiming it as an issue with fontconfig, when it isn't as the method fonts are called in Arch changed recently. A solution may simply be to use a different style method, but I haven't had a chance to properly go over how ttk.style or tkinter.feildialogue handles fonts as you may be able to simply change how you call it to solve the problem, but likely tkinter needs an update to conform to the new font configuration method.

Edit: after looking into it, tkinter is built into python, and likely the issue is with tkinter.ttk directly, so python itself would need updating to handle the new method for how Arch now handles fonts. Blaming the distro for keeping things up to date, when this can easily be pointed back to python just not having updated to handle the new method, which happens, I'm not saying python fucked up here, they should just need to update to handle the new use case.

@marianomacchi
Copy link

I was having the same issue on Fedora 32.

I couldn't solve it by removing fontconfig's cache, but I managed to by cloning the repository and directly running the app.py as a python script (after having installed pyusb).

@dixiedream
Copy link

In order to use (Python 3.8) i cloned the source code and run through command line:

Requirements

pip install pyusb

# pacman -S tk as it wasn't installed on my arch machine.

Usage

python app.py

@ThisNekoGuy
Copy link

ThisNekoGuy commented Mar 18, 2021

Can confirm that installing python-pyusb and tk via pacman and running app.py directly works just fine.
If I had to guess, the dependencies being bundled with the binary might be outdated; it evidently definitely isn't the distro's fault.

@ghost
Copy link

ghost commented Jul 20, 2021

Here's a PKBUILD that makes more sense.

https://github.com/Ammako/fusee-interfacee-tk/releases/tag/PKGBUILD

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants