evince crashed with SIGSEGV in XPending()

[Bulat Nigmatullin]

1) lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

2) apt-cache policy evince
evince:
  Installed: 3.3.5-0ubuntu1
  Candidate: 3.3.5-0ubuntu1
  Version table:
 *** 3.3.5-0ubuntu1 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

3)

4) Just crash report alert appeared. I don't know how and why.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: evince 3.3.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Wed Feb 15 08:33:08 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evince
ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.2.0-16-generic root=UUID=dd9deb42-96cb-4aa4-a666-097f4284c390 ro rootflags=subvol=@ quiet splash vt.handoff=7
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f65c53083ce <XPending+14>: mov 0x968(%rdi),%rax
 PC (0x7f65c53083ce) ok
 source "0x968(%rdi)" (0x00000968) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libutouch-geis.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libutouch-geis.so.1
 geis_event_dispatch () from /usr/lib/x86_64-linux-gnu/libutouch-geis.so.1
 ?? () from /usr/lib/libgrip.so.0
Title: evince crashed with SIGSEGV in XPending()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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