Bug 691919

Summary:	Problems rendering embedded eps images in dvi files
Product:	Ghostscript	Reporter:	Leonid Isaev <lisaev>
Component:	PS Interpreter	Assignee:	Alex Cherepanov <alex>
Status:	RESOLVED INVALID
Severity:	normal	CC:	andyrtr, christinedelight.top85
Priority:	P4
Version:	9.00
Hardware:	PC
OS:	Linux
Customer:		Word Size:	---
Attachments:	testcase: 1 tex file and 1 eps figure

Description Leonid Isaev 2011-01-30 22:51:43 UTC

Created attachment 7171 [details]
testcase: 1 tex file and 1 eps figure

When trying to display a .dvi file with an embedded eps image both in xdvi and evince, the following errors are displayed:

[xdvi]
xdvik: read_from_gs: Connection reset by peer
xdvi-xaw: Warning: Read_from_gs returned 0 bytes
[evince]
GPL Ghostscript  9.00: Initialization file gs_init.ps does not begin with an integer.
fatal internal error -100
[3]+  Illegal instruction     evince ~/current_science/notes/ti/ti_ss_notes.dvi

Both are accompanied by segfaults:
Jan 30 17:39:15 svibor kernel: gs[5831]: segfault at 4c4 ip 0839df34 sp bfcf75f0 error 4 in gs[8048000+572000]
Jan 30 17:39:27 svibor kernel: gs[5839]: segfault at 4c4 ip 0839df34 sp bfcf4b10 error 4 in gs[8048000+572000]
Jan 30 17:39:29 svibor kernel: gs[5840]: segfault at 4c4 ip 0839df34 sp bff23cb0 error 4 in gs[8048000+572000]

The error with xdvi can be worked around, if one sets PS ANTIALISING. There is an existing ticket (22026) at https://bugs.archlinux.org (https://bugs.archlinux.org/task/22026#comment71558) 
System and program versions:
Arch Linux
ghostscript 9.00
xdvik 22.84.16
evince 2.32.0

I am attaching the testcase (ti.tar.bz2)

Thanks.

Comment 1 Alex Cherepanov 2011-02-20 17:20:58 UTC

My attempts to process the sample file with TeX failed with some error messages. I have to admit that I have zero experience with TeX, but that's what happens when a native application file is submitted.

Please generate PS of PDF file that has problems on your system and attach it to the bug report if you choose to reopen this bug report.
The original bug report claims that this problem is fixed in v. 9.01.