evince crashed with SIGSEGV in FcConfigSubstituteWithPat()

[komputes]

Binary package hint: evince

Opening a large document or searching a pdf document crashed evince in karmic.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 19ba8f45e3d3d7bf348103cee5a0eeaa
CheckboxSystem: 099634613a96bc3665b92c4a813055e8
Date: Sat Sep 26 12:32:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evince
Package: evince 2.28.0-0ubuntu1
ProcCmdline: BOOT_IMAGE=/vmlinuz-2.6.31-10-generic root=/dev/mapper/hostname-kk ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SegvAnalysis:
 Segfault happened at: 0x95c6a6 <FcConfigSubstituteWithPat+198>: mov 0x4(%ecx),%edi
 PC (0x0095c6a6) ok
 source "0x4(%ecx)" (0x00000050) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 FcConfigSubstituteWithPat ()
 FcConfigSubstitute () from /usr/lib/libfontconfig.so.1
 GlobalParams::getDisplayFont(GfxFont*) ()
 CairoFreeTypeFont::create(GfxFont*, XRef*, FT_LibraryRec_*, int) () from /usr/lib/libpoppler-glib.so.4
 CairoFontEngine::getFont(GfxFont*, XRef*, Catalog*, int) ()
Title: evince crashed with SIGSEGV in FcConfigSubstituteWithPat()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:IA__FcConfigSubstituteWithPat (config=0x9f01c28,
IA__FcConfigSubstitute (config=0x9f01c28, p=0xb3faa520,
GlobalParams::getDisplayFont (this=0x9f5b4e0,
CairoFreeTypeFont::create (gfxFont=0xb3fa7c80,
CairoFontEngine::getFont (this=0xb3fa50d8,

[Pedro Villavicencio (pedro)]

seems to be a fontconfig issue, reassigning.

[Pedro Villavicencio (pedro)]

any chance to attach the document to the report? thanks.

[komputes (komputes)]

Hi Pedro, unfortunately I no longer remember which PDF I was looking at when this happened. None of the attachments seem to give a hint to the exact document. Should I stumble upon this bug again, I will re-open it.