gnome-shell crashed with SIGSEGV in FT_Load_Glyph()

[bhatta]

Since the bugs with same description was marked 'Expired' I am putting this as new bug.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-shell 3.8.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-11.4-lowlatency 3.11.3
Uname: Linux 3.11.0-11-lowlatency x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Sat Oct 5 13:14:15 2013
DisplayManager: lightdm
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2013-08-24 (41 days ago)
InstallationMedia: Ubuntu-Studio 13.10 "Saucy Salamander" - Alpha amd64 (20130811)
MarkForUpload: True
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f2d8ee1fa10: mov %rdx,0x10(%rax)
 PC (0x7f2d8ee1fa10) ok
 source "%rdx" ok
 destination "0x10(%rax)" (0x00000010) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
Title: gnome-shell crashed with SIGSEGV in FT_Load_Glyph()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
XsessionLog:
 Script for cjkv started at run_im.
 Script for default started at run_im.

[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 #1208379, 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.