On Wed, 8 Jul 2015, Peter Bjuhr wrote:
On 2015-07-08 10:17, Andrew Bernard wrote:
I reported this some time ago for Fedora 22. The issue has been dealt
with and fixed and is now working in 2.19.22. Previous versions
fail with the error you show, but 2.19.22 is now good. It’s not a
Frescobaldi error.
Thanks! Good to know that it has been fixed!
After a long search for the cause of the problem, it was fixed thanks to the
updated fontconfig package in Fedora. I don't think it was anything in LilyPond
2.19.22 that made the bug disappear:
https://bugzilla.redhat.com/show_bug.cgi?id=1216312
--
MT_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
