freetype: crash in TT_Load_Simple_Glyph

[nortcele]

With a MacBook pro, OS X Mavericks, Xcode 5.02, MacPorts 2.2.1. All ports uninstalled.

Installation of port urw-fonts fails the first time, then succeed.

Here are MacPort messages during installations of failed installation.

--->  Fetching archive for urw-fonts
--->  Attempting to fetch urw-fonts-1.0.7pre44_0.darwin_13.noarch.tbz2 from http://lil.fr.packages.macports.org/urw-fonts
--->  Attempting to fetch urw-fonts-1.0.7pre44_0.darwin_13.noarch.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/urw-fonts
--->  Attempting to fetch urw-fonts-1.0.7pre44_0.darwin_13.noarch.tbz2 from http://packages.macports.org/urw-fonts
--->  Fetching distfiles for urw-fonts
--->  Verifying checksums for urw-fonts
--->  Extracting urw-fonts
--->  Configuring urw-fonts
--->  Building urw-fonts
--->  Staging urw-fonts into destroot
--->  Installing urw-fonts @1.0.7pre44_0
--->  Activating urw-fonts @1.0.7pre44_0
Error: org.macports.activate for port urw-fonts returned: 
Please see the log file for port urw-fonts for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_urw-fonts/urw-fonts/main.log

I attached the corresponding log.

[ci42]

In the future please use WikiFormatting. Note that the Cc field requires a full email address.

[nortcele]

Perhaps the error is not in the urn-font port installation. I have a similar error with the installation of dejavu-fonts @2.34_0 that fails with:

--->  Fetching archive for dejavu-fonts
--->  Attempting to fetch dejavu-fonts-2.34_0.darwin_13.noarch.tbz2 from http://lil.fr.packages.macports.org/dejavu-fonts
--->  Attempting to fetch dejavu-fonts-2.34_0.darwin_13.noarch.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/dejavu-fonts
--->  Attempting to fetch dejavu-fonts-2.34_0.darwin_13.noarch.tbz2 from http://packages.macports.org/dejavu-fonts
--->  Fetching distfiles for dejavu-fonts
--->  Verifying checksums for dejavu-fonts
--->  Extracting dejavu-fonts
--->  Configuring dejavu-fonts
--->  Building dejavu-fonts
--->  Staging dejavu-fonts into destroot
--->  Installing dejavu-fonts @2.34_0
--->  Activating dejavu-fonts @2.34_0
Error: org.macports.activate for port dejavu-fonts returned: 
Error: Failed to install dejavu-fonts
Please see the log file for port dejavu-fonts for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_dejavu-fonts/dejavu-fonts/main.log

(log attached)

Fonts appear to be installed but the activation fails. If after the failure, I "sudo install dejavu-fonts", then the installation ends correctly.

Perhaps is it due to the way Mavericks manage SSD disk. I don't have any idea to find what is the true source of the failure.

[nortcele]

I installed these ports without problem on the following configuration: Mac mini server (late 2012), Intel Core i7 2.6 GHz, 2 classical 1 Tb Hard disks, OS X 10.8.5 - Xcode 5.02, MacPorts 2.2.1. All ports uninstalled.

[nortcele]

I made another successful installation of these ports on the following configuration: iMac 21.5" (late 2009), Intel Core 2 duo 3.06 GHz, classical 500 Mb Hard disk, 0S X 10.9 Mavericks - Xcode 5.02, MacPorts 2.2.1. All ports uninstalled.

So the problem seems to be related to the MacBook Pro where the installation fails.

[nortcele]

After more tests I think that the problem is with fc-cache from the fontconfig port. After an installation with

sudo port -d install urw-fonts > Desktop/port_install_urw-font_debug.log 2>&1

I have 3 fc-cache crash reports. 3 crashes are visible in the macports log:

sh: line 1: 90529 Segmentation fault: 11  /opt/local/bin/fc-cache -frsv
sh: line 1: 90532 Segmentation fault: 11  /opt/local/bin/fc-cache -frv

The third one is not catched by macports.

The port_install_urw-font_debug.zip archive contains the output of the installation and the 3 crash reports.

[takanori@…]

Which version of freetype are you using?

freetype was updated from @2.5.0_1 to @2.5.1_0 recently. Maybe it makes fc-cache unstable, I guess.

[takanori@…]

Anyway, I suppose that this is fontconfig's issue.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #41655.

freetype was recently updated; perhaps fontconfig needs to be rebuilt against the new freetype. Please try rebuilding fontconfig and let me know if that fixes the crash:

sudo port clean fontconfig
sudo port -ns upgrade --force fontconfig

If it does not, please report the problem to the developers. Since the crashing programs are fontconfig programs, I'd start by reporting it to them.

[nortcele]

Replying to takanori@…:

Which version of freetype are you using?

freetype was updated from @2.5.0_1 to @2.5.1_0 recently. Maybe it makes fc-cache unstable, I guess.

Before the tests I remove all installed ports so I use the last version available. @2.5.1 this morning.

[nortcele]

Replying to ryandesign@…:

Has duplicate #41655.

freetype was recently updated; perhaps fontconfig needs to be rebuilt against the new freetype. Please try rebuilding fontconfig and let me know if that fixes the crash:

sudo port clean fontconfig
sudo port -ns upgrade --force fontconfig

If it does not, please report the problem to the developers. Since the crashing programs are fontconfig programs, I'd start by reporting it to them.

Sadly, that doesn't fixe the crashes.

[ryandesign (Ryan Carsten Schmidt)]

Other tickets mentioning similar fontconfig and freetype symbols: #41651 (emacs), #41599 (inkscape).

[ryandesign (Ryan Carsten Schmidt)]

Same crash in #41671 (gftp-gtk, wine and other gtk-based programs).

[ryandesign (Ryan Carsten Schmidt)]

Submitted bug report to freetype: ​https://savannah.nongnu.org/bugs/index.php?40797

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #41674 (with graphviz' dot while building gnuradio)

[ryandesign (Ryan Carsten Schmidt)]

I was able to reproduce the issue using fc-list. Upstream fixed this a couple days ago; I applied their fix to our port in r114266. Now fc-list works fine so I think this fixes the problem.

[atlantide84@…]

Replying to ryandesign@…:

I was able to reproduce the issue using fc-list. Upstream fixed this a couple days ago; I applied their fix to our port in r114266. Now fc-list works fine so I think this fixes the problem.

I just updated and now all works, no more crashes..so #41671 is fixed now. Thank you!

[nortcele]

No more crashes here too. Thank you a lot.

[chuiyewleong@…]

The gnuradio-companion works like a charm now. Thanks.