Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#50353 - [fontconfig] Incorrect font substitution

Attached to Project: Arch Linux
Opened by Konstantin Gizdov (kgizdov) - Thursday, 11 August 2016, 11:42 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 19 March 2017, 09:34 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Font config incorrectly substitutes ZapfDingbats and Symbol with Bitstream Vera, even though correct alternatives are present and configured (e.g. DejaVu). A thorough discussion of the issue can be found here -

Additional info:
* package version(s)
fontconfig 2.12.1-3

* config and/or log files etc.

* Actual Result
$ fc-match -s sans
Vera.ttf: "Bitstream Vera Sans" "Roman"

* Expected Result
$ fc-match -s sans
DejaVuSans.ttf: "DejaVu Sans" "Book"

Steps to reproduce:
1. create a PDF including symbols (e.g Greek Letters)
2. Install Bitstream Vera or BistreamVera-based Unicode font (e.g. EmojiOne Color Font)
2. view PDF in viewer (e.g. Evince)
3. symbols are substituted by empty boxes
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 19 March 2017, 09:34 GMT
Reason for closing:  Upstream
Comment by Jan Alexander Steffens (heftig) - Sunday, 21 August 2016, 21:08 GMT
Isn't this an upstream problem? We're shipping the configuration unmodified.
Comment by Andreas Radke (AndyRTR) - Wednesday, 24 August 2016, 20:46 GMT
Jan, I guess we should apply the patches from and

But I guess this won't solve the above font substitution issue.
Comment by Andreas Radke (AndyRTR) - Friday, 16 December 2016, 07:08 GMT
There's more discussion on the ML:

I guess we can close our bug as "upstream"?