Evince crashed while viewing a pdf that was modified at the same time (overwritten by pdflatex).
I may have been navigating the pdf in evince (opposed to just looking at it).
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: evince 3.6.1-1ubuntu3
ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature'
Uname: Linux 3.11.0-031100rc7-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Wed Sep 11 23:33:25 2013
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2013-02-26 (197 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-031100rc7-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7
SegvAnalysis:
Segfault happened at: 0x7f4b21681840 <ev_job_get_run_mode>: mov 0x20(%rdi),%eax
PC (0x7f4b21681840) ok
source "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
ev_job_get_run_mode () from /usr/lib/libevview3.so.3
ev_job_scheduler_update_job () from /usr/lib/libevview3.so.3
?? () from /usr/lib/libevview3.so.3
g_closure_invoke (closure=0x7f4b23cf81d0, return_value=0x7fff8e308710, n_param_values=2, param_values=0x7f4b23ee6170, invocation_hint=0x7fff8e3085e0) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:777
signal_emit_unlocked_R (node=node@entry=0x7f4b239acf90, detail=detail@entry=0, instance=instance@entry=0x7f4b23adc010, emission_return=emission_return@entry=0x7fff8e308710, instance_and_params=instance_and_params@entry=0x7f4b23ee6170) at /build/buildd/glib2.0-2.36.0/./gobject/gsignal.c:3622
Title: evince crashed with SIGSEGV in ev_job_get_run_mode()
UpgradeStatus: Upgraded to raring on 2013-04-19 (145 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
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 #971404, 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.