compiz crashed with SIGSEGV in FT_Load_Glyph()

[Marc PETER]

may be related to #959323 (FT_Load_Glyph() is in the description) but I am under 13.10.
got by searching the backup app in the app search tool (i don't know the name in english). It throwed when I typed 'Sauve' in the search line.
Note the app search tool didn't crash.
My appologies for the very bad english I use...

Regards
Marc

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Sat Feb 8 11:59:39 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2012-11-07 (458 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f928cbe5a10: mov %rdx,0x10(%rax)
 PC (0x7f928cbe5a10) 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: unity
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: compiz crashed with SIGSEGV in FT_Load_Glyph()
UpgradeStatus: Upgraded to saucy on 2013-10-20 (110 days ago)
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 #1199571, 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.