evince crashed with SIGSEGV

[LAZA]

https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1404972

I should open up a new bug report like the page here
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
says.
This should be fixed asap for the LTS releases.

Original report:

Opened directly a processable document i downloaded, edited some things and closed *without* saving!

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: evince 3.10.3-0ubuntu10.1
ProcVersionSignature: Ubuntu 3.16.0-29.39~14.04.1-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Dec 22 20:17:00 2014
Disassembly: => 0x7fc880ade803: Cannot access memory at address 0x7fc880ade803
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2014-03-16 (281 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140225)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=325b49b2-158d-45a6-81b1-2d4351757330 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fc880ade803: Cannot access memory at address 0x7fc880ade803
 PC (0x7fc880ade803) ok
 SP (0x7fffe7a932f8) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: evince
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
Title: evince crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare sudo tape video

[LAZA (laza74)]

Stacktrace.txt

#0 0x00007fc880ade803 in ?? ()
No symbol table info available.
#1 0x00007fffe7a92460 in ?? ()
No symbol table info available.
#2 0x0000000000000000 in ?? ()
No symbol table info available.

[LAZA (laza74)]

ThreadStacktrace.txt

.
Thread 6 (LWP 10210):
#0 0x00007fc87e871cbd in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
.
Thread 5 (LWP 10209):
#0 0x00007fc87e871cbd in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
.
Thread 4 (LWP 10212):
#0 0x00007fc87e871cbd in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
.
Thread 3 (LWP 10221):
#0 0x00007fc87eb56414 in ?? ()
No symbol table info available.
#1 0x0000000600000000 in ?? ()
No symbol table info available.
#2 0x00007fc882c0ef90 in ?? ()
No symbol table info available.
#3 0x00007fc882cce560 in ?? ()
No symbol table info available.
#4 0x0000000000000006 in ?? ()
No symbol table info available.
#5 0x00007fc8811210c0 in ?? ()
No symbol table info available.
#6 0x00007fc87f0f8bf7 in ?? ()
No symbol table info available.
#7 0x00007fc8811210c0 in ?? ()
No symbol table info available.
#8 0x00007fc8811210c0 in ?? ()
No symbol table info available.
#9 0x0000000000000000 in ?? ()
No symbol table info available.
.
Thread 2 (LWP 10305):
#0 0x00007fc87eb567ce in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
.
Thread 1 (LWP 10207):
#0 0x00007fc880ade803 in ?? ()
No symbol table info available.
#1 0x00007fffe7a92460 in ?? ()
No symbol table info available.
#2 0x0000000000000000 in ?? ()
No symbol table info available.

[Sebastien Bacher (seb128)]

The bug is years old without activity or new report, assuming it has been deprecated and closing, best to report a new bug if you still have issues