evince crashed with SIGSEGV in __strchr_sse2()

[iMac]

Noting the duplicate #879926 was created with Alpha, I am re-submitting

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Nov 8 14:17:35 2011
ExecutablePath: /usr/bin/evince
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=52543d1c-6080-4cdf-80e0-30b9af3748f7 ro crashkernel=384M-2G:64M,2G-:128M splash vt.handoff=7
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1b8caf4c2a <__strchr_sse2+26>: movdqa (%rdi),%xmm0
 PC (0x7f1b8caf4c2a) ok
 source "(%rdi)" (0x00000140) 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 (pool=0x7f1b907f1190, param_name=0x145 <Address 0x145 out of bounds>, owner_type=139756369071952, walk_ancestors=1) at /build/buildd/glib2.0-2.30.0/./gobject/gparam.c:1058
 g_object_set_valist (object=0x7f1b90bc4240, first_property_name=<optimized out>, var_args=0x7fffd5fb13c8) at /build/buildd/glib2.0-2.30.0/./gobject/gobject.c:1690
 g_object_set (_object=0x7f1b90bc4240, first_property_name=0x7f1b902d50ed "enable-gestures") at /build/buildd/glib2.0-2.30.0/./gobject/gobject.c:1833
 ?? ()
Title: evince crashed with SIGSEGV in __strchr_sse2()
UpgradeStatus: Upgraded to oneiric on 2011-10-28 (11 days ago)
UserGroups: adm admin cdrom dialout dip disk fax fuse libvirtd lpadmin mythtv netdev plugdev pulse pulse-access sambashare scanner tape vboxusers vde2-net video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu 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.