Comment 4 for bug 342717

Related to the security issue, I don't know if the attached font is segfaulting for the same reason, but I had a session ending segfault when running fc-cache -fv. I went through the ~3000 custom fonts I have, and this is the only one I could find that segfaults. Though oddly, the segfault only killed my gnome-session the first time.

I don't know if it's a fontconfig issue or a gnome issue, but with the font in a font load path other gnome issues occur as well: If gnome is locked, the unlock dialog won't appear. If no session exists and you try to login, the login seems to succeed, but the desktop never loads. Removing the font resolves these issues.

Running fontconfig version 2.11.0 on Trusty.