fc-match does not return the correct font
Bug #1814342 reported by
Ron Koerner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| fontconfig (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
On Ubuntu 18.10 the command `fc-match monospace:bold` returns
DejaVuSansM
instead of
DejaVuSansM
This works correctly on Ubuntu 18.04.1 which is using fontconfig 2.12.6, whereas 18.10 uses 2.13.0.
I compiled 2.13.1 from source and just installed libfontconfig.
This solves the problem.
While it does not sound much, this bug also causes Java 8 AWT/Swing font rendering to be uglier than it has to be. Instead of "DejaVu Sans Mono Bold" and emboldened version of "DejaVu Sans Mono" is used which has a different size, which goes counter to the notion of a "monospace" font.
Revision history for this message
| Sebastien Bacher (seb128) wrote | #1 |
| Changed in fontconfig (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Fix Released |
To post a comment you must log in.
The issue seems to have been fixed by that commit
https:/
Closing since it's resolved with 1.13.1 in the current Ubuntu serie, maybe it should be SRU to 18.10 but that's a non LTS serie and the issue doesn't seem to get much user traction...