evince crashed with SIGSEGV in ev_pixbuf_cache_set_selection_list()

[Milan Bouchet-Valat]

Binary package hint: evince

Crashed while opening a document. But now opening this document works fine.

This looks similar to Bug 642736, but I'm opening it separately in the hope we'll get a better (and up-to-date) trace.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evince 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Wed Oct 13 17:03:29 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100913)
ProcCmdline: BOOT_IMAGE=/vmlinuz-2.6.35-22-generic root=/dev/sda3 ro quiet splash
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x71f964 <ev_pixbuf_cache_set_selection_list+436>: mov 0x58(%eax),%edx
 PC (0x0071f964) ok
 source "0x58(%eax)" (0x00000058) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 ev_pixbuf_cache_set_selection_list () from /usr/lib/libevview.so.3
 ?? () from /usr/lib/libevview.so.3
 ?? () from /usr/lib/libevview.so.3
 ?? () from /usr/lib/libevview.so.3
 _gtk_marshal_BOOLEAN__BOXED (closure=0x22aaa1c0, return_value=0x22be1000, n_param_values=2, param_values=0x22c2f1f0, invocation_hint=0xbf8a4b30, marshal_data=0x730db0) at /build/buildd/gtk+2.0-2.22.0/gtk/gtkmarshalers.c:86
Title: evince crashed with SIGSEGV in ev_pixbuf_cache_set_selection_list()
UserGroups: adm admin cdrom dialout 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 #651931, 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.