evince crashed with SIGSEGV in g_param_spec_pool_lookup()

[Vadim Peretokin]

Keeps crashing when I try to open a particular document. I can't attach it here though, but I tried multiple times with no success.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.2.1-0ubuntu2
ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature'
Uname: Linux 3.1.0-030100rc10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Wed Nov 9 13:35:29 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.1.0-030100rc10-generic root=UUID=5a261133-b5a0-46a2-81ff-c1af4edb821e ro quiet splash nomodeset video=uvesafb:mode_option=1440x900-24,mtrr=3,scroll=ywrap vt.handoff=7
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f55d72c4c2a: movdqa (%rdi),%xmm0
 PC (0x7f55d72c4c2a) ok
 source "(%rdi)" (0x00000110) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 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 g_param_spec_pool_lookup()
UpgradeStatus: Upgraded to oneiric on 2011-10-19 (20 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare vboxusers

[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.