gnome-font-viewer crashed with SIGSEGV after clicking on "install"

[lrbabe]

I tried to install a first font and the installation failed (no idea why, the "install" button just turned into "failed to install", or somethin').
Then I tried to install to install a variation of that font and the font viewer crashed.

I'm on Quantal 64 but I guess that's automatically reported.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-font-viewer 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Mon Oct 8 18:05:18 2012
ExecutablePath: /usr/bin/gnome-font-viewer
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
ProcCmdline: gnome-font-viewer /home/username/Downloads/Josefin_Sans/JosefinSans-Bold.ttf
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7faf90ccae2d: mov (%r8,%rdx,1),%edx
 PC (0x7faf90ccae2d) ok
 source "(%r8,%rdx,1)" (0x0e8e4ff0) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-font-viewer
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
 ?? ()
Title: gnome-font-viewer crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1051484, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.