evince crashed with SIGSEGV in __strchr_sse2()

[GaaL]

opening the pdf file at http://www.plusbus.info/sites/default/files/pdfs/St%20Albans.pdf and then crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.2.1-0ubuntu2
ProcVersionSignature: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/proc/version_signature'
Uname: Linux 3.0.3-030003-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Nov 29 17:16:24 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: evince /tmp/St\ Albans.pdf
ProcCwd: /home/melankh
ProcEnviron:
 LANGUAGE=fr:en
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 LC_MESSAGES=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb9559e7c2a <__strchr_sse2+26>: movdqa (%rdi),%xmm0
 PC (0x7fb9559e7c2a) ok
 source "(%rdi)" (0x000001c0) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 __strchr_sse2 () at ../sysdeps/x86_64/multiarch/../strchr.S:33
 g_param_spec_pool_lookup () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_set_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_set () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
Title: evince crashed with SIGSEGV in __strchr_sse2()
UpgradeStatus: Upgraded to oneiric on 2011-10-13 (47 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare tape vboxusers video

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