evince crashed with SIGSEGV in g_list_length()

[Anders Kaseorg]

evince crashed with SIGSEGV in g_list_length()

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: evince 3.10.3-0ubuntu13
ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
Uname: Linux 3.16.0-3-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Jul 13 05:22:49 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2010-12-05 (1315 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic root=/dev/mapper/fdisk-ubuntu ro init=/lib/systemd/systemd quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f9812d315f0 <g_list_length+16>: mov 0x8(%rdi),%rdi
 PC (0x7f9812d315f0) ok
 source "0x8(%rdi)" (0x00000059) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 g_list_length (list=0x51) at /build/buildd/glib2.0-2.41.1/./glib/glist.c:963
 ?? ()
 ?? ()
 g_closure_invoke (closure=0x7f9815dd4b30, return_value=0x0, n_param_values=3, param_values=0x7fff8dc1ac80, invocation_hint=0x7fff8dc1ac20) at /build/buildd/glib2.0-2.41.1/./gobject/gclosure.c:768
 signal_emit_unlocked_R (node=node@entry=0x7f9815b14400, detail=detail@entry=0, instance=instance@entry=0x7f9815c3bf00, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff8dc1ac80) at /build/buildd/glib2.0-2.41.1/./gobject/gsignal.c:3555
Title: evince crashed with SIGSEGV in g_list_length()
UpgradeStatus: Upgraded to utopic on 2013-10-31 (254 days ago)
UserGroups: adm admin bumblebee cdrom dialout fuse kvm libvirtd lpadmin plugdev sambashare sudo wireshark

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