FS#63903 - [fontconfig] "/etc/fonts/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"

Attached to Project: Arch Linux
Opened by Daniel M. Capella (polyzen) - Tuesday, 24 September 2019, 13:20 GMT
Last edited by Jan Alexander Steffens (heftig) - Monday, 14 October 2019, 13:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 22
Private No

Details

Description:

After upgrading noto-fonts-emoji to 20190810-1, fontconfig.hook returns:
Fontconfig warning: "/etc/fonts/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"

Additional info:
- fontconfig 2:2.13.91+23+g65087ac-1
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Monday, 14 October 2019, 13:44 GMT
Reason for closing:  Fixed
Additional comments about closing:  lib32-fontconfig 2.13.91+24
Comment by Olivier DOSSMANN (blankoworld) - Tuesday, 24 September 2019, 14:55 GMT
Same problem here. I can display the same error with:

`fc-cache-32`.

I found the problem while attempting to launch gitter desktop client (which display more problems, but that's another story).

I don't know how to resolve this problem.
Comment by Chris Billington (chrisjbillington) - Tuesday, 24 September 2019, 15:20 GMT
It looks like fontconfig, the package that owns /etc/fonts/conf.avail/05-reset-dirs-sample.conf, was updated recently, but that lib32-fontconfig, which appears to share configuration, was not. Seems like fontconfig and lib32-fontconfig ought to be released in lockstep. I imagine a new Arch package for lib32-fontconfig would solve the issue.
Comment by Nick Stefanov (mozo) - Tuesday, 24 September 2019, 19:14 GMT
I don't have noto-fonts-emoji installed but I receive this error too.
Comment by Chris Billington (chrisjbillington) - Tuesday, 24 September 2019, 21:28 GMT
Though the issue right now is just that lib32-fontconfig is out of date, normally not warranting a bug report, the root cause of the issue is that the fontconfig and lib32-fontconfig package releases aren't synchronised.
Comment by Samega 7Cattac (Samega 7Cattac) - Sunday, 06 October 2019, 17:02 GMT
Same issue

fontconfig-2:2.13.91+23+g65087ac-1
lib32-fontconfig-2:2.13.1+12+g5f5ec56-1
Comment by Mel (Mel) - Sunday, 06 October 2019, 22:07 GMT
"This element removes all of fonts directories where added by
dir elements. it is useful to override fonts dirs from system
to their own dirs only."
^ this was added to cater to flatpaks and other self-contained app technology

Even manually building the updated version fails, it doesn't pass all the tests.

One possible solution is not shipping it, until upstream fixes it.
Comment by Daniel Mehrmann (Akusari) - Monday, 07 October 2019, 23:18 GMT
I can confirm this bug too
Comment by Simone (tigerjack) - Sunday, 13 October 2019, 10:20 GMT
Confirming the bug.

Loading...