Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

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!
Tasklist

FS#51707 - [lilypond] Font displayed much too large

Attached to Project: Community Packages
Opened by J. M. Reckel (ArchChem) - Saturday, 05 November 2016, 13:21 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 21 June 2017, 11:13 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

This package raises a font error, the font is displayed in a too large size (see picture http://i.imgur.com/kPGcKEjl.png) as mentioned here: https://bbs.archlinux.org/viewtopic.php?pid=1665573
So, the lilypond compiling results are ugly and not usable.

User trschell suggested a patch solving the problem: https://bbs.archlinux.org/viewtopic.php?pid=1665573#p1665573
It should be implemented.

Additional info:
* The problem occurs scince fontconfig 2.11.94-1

Steps to reproduce:
Compile a lilypond document with text.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Wednesday, 21 June 2017, 11:13 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Saturday, 05 November 2016, 14:15 GMT
Has this been reported/fixed upstream? If not, you really need to take it there.
Comment by J. M. Reckel (ArchChem) - Friday, 11 November 2016, 16:42 GMT
I think this is not useful for other distros like Ubuntu don't have this problem. It seems to be a bug with the current ArchLinux package or with pango or fontconfig. Till this is solved, this patch can be a useful solution.
Comment by Doug Newgard (Scimmia) - Friday, 11 November 2016, 16:48 GMT
A change in fontconfig does not mean a bug, it could simply mean a change.

How many distros are using a fontconfig this new?
Comment by J. M. Reckel (ArchChem) - Monday, 02 January 2017, 13:26 GMT
As user pbrenna points out in this post (https://bbs.archlinux.org/viewtopic.php?pid=1679864#p1679864), the problem seems to be a conflict with the LXQT font configuration. Removing the file ~/.config/fontconfig/fonts.conf fixes it. Users not using LXQT seem to be not affected.

Loading...