evince crashed when it reloads a file with less pages than before and try to go to a now unexisting page

[Paul Ecoffet]

I use evince as a viewer when editing my Libreoffice files and exporting them to pdf. I removed a descent amount of text and my document was now 1 page instead of 2. Yet, on evince, I was looking at the 2nd page. When the file was updated, evince crashed.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: evince 3.18.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Mar 31 19:39:28 2016
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2016-03-30 (1 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160329)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=10357116-e027-4866-a377-96f6cd72a31a ro noprompt quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f059f209f2f <atk_object_notify_state_change+31>: cmp (%rdx),%rax
 PC (0x7f059f209f2f) ok
 source "(%rdx)" (0x00000110) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 atk_object_notify_state_change () from /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0
 ev_view_accessible_set_page_range () from /usr/lib/x86_64-linux-gnu/libevview3.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libevview3.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libevview3.so.3
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: evince crashed with SIGSEGV in atk_object_notify_state_change()
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 #1436555, 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.