evince crashed with signal 7

[csanchezmonte]

Binary package hint: evince

Package: evince
ubuntu 9.10
I try to load a pdf archive of a external partition

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Oct 27 08:56:03 2009
Disassembly: 0x58b422: No se puede acceder a la memoria en la dirección 0x58b422
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evince
KernLog:
 Oct 27 07:20:07 ubuntu kernel: [ 0.004028] Security Framework initialized
 Oct 27 07:20:07 ubuntu kernel: [ 0.004048] AppArmor: AppArmor initialized
 Oct 27 07:20:07 ubuntu kernel: [ 0.261510] AppArmor: AppArmor Filesystem Enabled
 Oct 27 07:20:07 ubuntu kernel: [ 1.759158] type=2000 audit(1256627865.756:1): initialized
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
Package: evince 2.28.1-0ubuntu1
ProcCmdline: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=es console-setup/layoutcode?=es
ProcEnviron:

ProcMaps:
 08048000-0809b000 r-xp 00000000 00:11 19195 /usr/bin/evince
 0809b000-0809e000 rw-p 00052000 00:11 19195 /usr/bin/evince
 bff92000-bffa7000 rw-p 00000000 00:00 0 [stack]
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 apparmor 2.3.1+1403-0ubuntu27
 libapparmor1 2.3.1+1403-0ubuntu27
 libapparmor-perl 2.3.1+1403-0ubuntu27
 apparmor-utils 2.3.1+1403-0ubuntu27
Signal: 7
SourcePackage: evince
Stacktrace:
 #0 0x0058b422 in ?? ()
 No symbol table info available.
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (Thread 5057):
 #0 0x0058b422 in ?? ()
 No symbol table info available.
Title: evince crashed with signal 7
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:_start () from /lib/ld-linux.so.2

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.