evince crashed with SIGSEGV in g_atomic_int_exchange_and_add()

[Roland Dreier]

Binary package hint: evince

evince crashed a couple of times while I was just scrolling through http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2100.pdf

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evince 2.32.0-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.38-2.29-generic 2.6.38-rc3
Uname: Linux 2.6.38-2-generic x86_64
Architecture: amd64
Date: Mon Feb 7 09:43:39 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101206)
KernLog:

ProcCmdline: evince /tmp/n2100.pdf
ProcCmdline_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-generic root=UUID=ab1e5491-e40c-4113-bf20-22ecb604999a ro quiet splash vt.handoff=7
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature_: Ubuntu 2.6.38-2.29-generic 2.6.38-rc3
SegvAnalysis:
 Segfault happened at: 0x7f75f25420b2 <g_atomic_int_exchange_and_add+2>: lock xadd %eax,(%rdi)
 PC (0x7f75f25420b2) ok
 source "%eax" ok
 destination "(%rdi)" (0x00000024) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 g_atomic_int_exchange_and_add () from /lib/libglib-2.0.so.0
 g_variant_unref () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
Title: evince crashed with SIGSEGV in g_atomic_int_exchange_and_add()
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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