pdftotext crashed with SIGSEGV in cmsDoTransform()

[eris23]

Binary package hint: tracker

pdftotext crashed with SIGSEGV in cmsDoTransform()

karmic
tracker 0.6.95-1ubuntu1

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Jul 20 19:27:17 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pdftotext
NonfreeKernelModules: nvidia
Package: poppler-utils 0.11.0-0ubuntu4
ProcCmdline: pdftotext -enc UTF-8 -q -nopgbrk /media/disk-3/etext/Computing\ &\ IT/A\ Dynamic\ Birthmark\ for\ Java.pdf -
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0x7fca687c0055 <cmsDoTransform+5>: mov %rdi,0x18(%rax)
 PC (0x7fca687c0055) ok
 source "%rdi" ok
 destination "0x18(%rax)" (0x00000018) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: poppler
StacktraceTop:
 cmsDoTransform () from /usr/lib/liblcms.so.1
 GfxICCBasedColorSpace::getRGB(GfxColor*, GfxRGB*) ()
 TextWord::TextWord(GfxState*, int, double, double, int, TextFontInfo*, double) () from /usr/lib/libpoppler.so.5
 TextPage::beginWord(GfxState*, double, double) ()
 TextPage::addChar(GfxState*, double, double, double, double, unsigned int, int, unsigned int*, int) ()
Title: pdftotext crashed with SIGSEGV in cmsDoTransform()
Uname: Linux 2.6.31-3-generic x86_64
UserGroups: audio cdrom dialout dip fax fuse kvm libvirtd lpadmin netdev plugdev sambashare tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:cmsDoTransform () from /usr/lib/liblcms.so.1
GfxICCBasedColorSpace::getRGB(GfxColor*, GfxRGB*) ()
TextWord::TextWord(GfxState*, int, double, double, int, TextFontInfo*, double) () from /usr/lib/libpoppler.so.5
TextPage::beginWord(GfxState*, double, double) ()
TextPage::addChar(GfxState*, double, double, double, double, unsigned int, int, unsigned int*, int) ()

[Jeremy Bícha (jbicha)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.