evince crashed after opening dvi file

[thiago]

Binary package hint: evince

Evince (version 2.32.0) crashes when opening dvi file. Using ubuntu maverick 10.10 32bits.

GPL Ghostscript 8.71: Initialization file gs_init.ps does not begin with an integer.
fatal internal error

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evince 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
Architecture: i386
CrashCounter: 1
Date: Fri Oct 1 15:36:49 2010
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=84fcc034-397f-470f-9a43-c0b03b093bd1 ro quiet splash
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.utf8
 SHELL=/bin/bash
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 lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:1587): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:
 i_unregister_root (mem=0xffffff9c, rp=0xb6adcff4,
 interp (pi_ctx_p=<value optimized out>,
 gs_interpret (pi_ctx_p=0xb5a750bc, pref=0xb48849e8,
 gs_main_run_string_begin (minst=0xb5a75068, user_errors=0,
 gs_main_run_string_with_length (minst=0xb5a75068,

[Pedro Villavicencio (pedro)]

Thanks for the report, could you please attach that document to the report? thanks in advance.

[thiago (pereirats)]

Sure, which document do you need?

2010/10/4 Pedro Villavicencio <email address hidden>:
> Thanks for the report, could you please attach that document to the
> report? thanks in advance.
>
> ** Visibility changed to: Public
>
> ** Changed in: evince (Ubuntu)
>       Status: New => Incomplete
>
> --
> evince crashed after opening dvi file
> https://bugs.launchpad.net/bugs/653194
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “evince” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: evince
>
> Evince (version 2.32.0) crashes when opening dvi file. Using ubuntu maverick 10.10 32bits.
>
> GPL Ghostscript 8.71: Initialization file gs_init.ps does not begin with an integer.
> fatal internal error
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.10
> Package: evince 2.32.0-0ubuntu1
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
> Uname: Linux 2.6.35-22-generic-pae i686
> Architecture: i386
> CrashCounter: 1
> Date: Fri Oct  1 15:36:49 2010
> ExecutablePath: /usr/bin/evince
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
> ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=84fcc034-397f-470f-9a43-c0b03b093bd1 ro quiet splash
> ProcEnviron:
>  LANGUAGE=pt_BR:pt:en
>  LANG=pt_BR.utf8
>  SHELL=/bin/bash
> 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 lpadmin plugdev sambashare
> XsessionErrors: (polkit-gnome-authentication-agent-1:1587): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/evince/+bug/653194/+subscribe
>

[Anton Eliasson (eliasson)]

Any news on this? The bug still affects me. Do you need any more information perhaps?

[MrWoo (laxix-deactivatedaccount)]

Affects me, too. The dvi I was opening included stuff that was known to be a problem for dvi viewers: pstricks output.

http://tug.org/PSTricks/main.cgi/

"# PSTricks is PostScript Tricks, viewing your PS output with a PS viewer is appropriate. Nearly all DVI-viewers cannot show the correct output.
# You cannot run your files with pdftex or pdflatex, use the sequence latex->dvips->ps2pdf, or see topic pdfoutput"

[Cesare Mastroianni (cece)]

Please, notice my new bug report bug #714849 where I attached GDB detailed backtrace of the coredump. (bug #714849 has been marked as "duplicate" of this present one).

Ciao
CM

[Romano Giannetti (romano-giannetti)]

I have a similar crash, but not the same. Trying to open the rg004ash.dvi file (will attach), which is a simple fake sensor data sheet for my class exams, reliably crashes evince:

(0)pern:~/education/SisPer4/mysensors% evince rg004ash.dvi
fatal internal error -100[1] 27622 illegal hardware instruction evince rg004ash.dvi

If asked, I can send the source for the file. xdvi opens it perfectly.

[Romano Giannetti (romano-giannetti)]

Ok, it seems the problem is the EPS inclusion. Maybe ghostscript-related? The minimal file here (attached, all the file needed
 to test) triggers the bug:

(0)pern:~/software/bugs/evince% cat try.tex
\documentclass[12pt,a4paper]{article}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{graphicx}
\begin{document}

Just this
\includegraphics{little}

\end{document}
(0)pern:~/software/bugs/evince% latex try > /dev/null
(0)pern:~/software/bugs/evince% evince try.dvi
fatal internal error -100[1] 27939 illegal hardware instruction evince try.dvi
(132)pern:~/software/bugs/evince%

Hope this helps...

[Tomas Bacigal (tom67t)]

Indeed, it seems to be related to ghostscript

http://bugs.ghostscript.com/show_bug.cgi?id=689698

[Romano Giannetti (romano-giannetti)]

It is fixed in Natty.

[Cesare Mastroianni (cece)]

@Romano:
Thanks for this info. However, I'm still using Maverick at home and Lucid at office. Both releases suffer for this bug.

Ciao
CM

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest stable version of Ubuntu - Natty Narwhal.

If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad