evince crashed with SIGILL in gs_interpret()

[Cesare Mastroianni]

Binary package hint: evince

Hi there.

I used Lynx to generate a DVI file including an EPS images imported from Xfig.

XDVI displays the DVI file well, with no problem. Evince crashes each time. See attached TXT report from GDB. I attached also the DVI generated file + its own EPS file.

I noticed there is also bug #653194 about a similar problem. But there at comment #8 MrWoo claims that his problem affects all DVI viewers. My problem seems to affect Evince, and not XDVI.

Please, note that evince prints a comment to the command line while crashing (2 lines message):
   fatal internal error -100
   Istruzione non consentita (core dump creato)

The second line is Italian (my local configuration), and it means more or less "Illegal instruction (core dumped)".

Ciao from Italy.
CM

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evince 2.32.0-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic-pae 2.6.35.10
Uname: Linux 2.6.35-25-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Mon Feb 7 22:09:05 2011
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic-pae root=UUID=f75d175a-4a7e-4fdf-804a-2c88e8b16fe6 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=it_IT.utf8
Signal: 4
SourcePackage: evince
StacktraceTop:
 ?? () from /usr/lib/libgs.so.8
 ?? () from /usr/lib/libgs.so.8
 gs_interpret () from /usr/lib/libgs.so.8
 gs_main_run_string_begin () from /usr/lib/libgs.so.8
 gs_main_run_string_with_length () from /usr/lib/libgs.so.8
Title: evince crashed with SIGILL in gs_interpret()
UserGroups: adm admin cdrom dialout lp 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 #653194, 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.