Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 156200 - ghostscript explodes when fed some kinds of Acrobat Reader output
Summary: ghostscript explodes when fed some kinds of Acrobat Reader output
Alias: None
Product: Fedora
Classification: Fedora
Component: ghostscript
Version: 3
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-28 12:43 UTC by Barry K. Nathan
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: 8.15-0.rc3.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-06-07 11:29:34 UTC
Type: ---

Attachments (Terms of Use)
output of GhostScript when processing the test case PostScript file (2.83 KB, text/plain)
2005-04-28 12:46 UTC, Barry K. Nathan
no flags Details
test case PostScript file (277.57 KB, application/postscript)
2005-04-28 12:48 UTC, Barry K. Nathan
no flags Details

Description Barry K. Nathan 2005-04-28 12:43:20 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Description of problem:
I've noticed lately that more and more documents are failing to fully print properly on the printer connected to my Fedora Core 3 print server. Examining /var/log/cups/error.log shows that ghostscript is blowing up.

Recently, I have (accidentally) found situations where this can be reproduced 100% of the time. The easiest way to hit the problem is to try printing from Adobe Reader 7.0.1 on a Mac running Mac OS 10.3.8, although I hit the problem earlier this month using Acrobat Reader 5.0.5 on Linux.

I didn't report this bug before, because all of my previous test cases involved private information (e.g. tax forms). However, I've managed to construct a test case using one of Red Hat's own web pages ;) so I can now report this bug.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Download the PostScript file which I will attach after I file this bug. Save it with some filename (e.g. "d00394-001").
2. Run "gs d00394-001".
3. See whether gs can run without crashing. This particular test case seems to always cause crashes on the second page or so (after the first page in any case).

Actual Results:  I was going to cut-and-paste this, but it's longer than I expected (and it may be wide enough to mess up this Bugzilla anyway). I'll attach it instead.

Expected Results:  The "Error: /undefined in |-" should not happen, and ghostscript should not crash. Oh, and it should print all pages, not just the first page.

Additional info:

Workaround for Adobe Reader 7.0.1:
In the Print dialog box, click "Advanced". Then change "Font and Resource Policy" from the default of "Send by Range" to "Send at Start". (Maybe "Send for Each Page" will also work -- but I didn't try that. In any case, GhostScript works with "Send at Start" and blows up with "Send by Range".)

Unfortunately I have not managed to find a similar workaround for the Acrobat Reader 5.0.5 case.

Comment 1 Barry K. Nathan 2005-04-28 12:46:15 UTC
Created attachment 113769 [details]
output of GhostScript when processing the test case PostScript file

This is basically the "Actual Results" section of the Bugzilla. (No, I haven't
attached the test case yet. That will be the next attachment.)

Comment 2 Barry K. Nathan 2005-04-28 12:48:52 UTC
Created attachment 113771 [details]
test case PostScript file

This is the PS file that I'm using to reproduce all my troubles... (I captured
it by copying it out of /var/spool/cups when printing the source PDF from
Acrobat Reader on the family iMac.)

Comment 3 Barry K. Nathan 2005-04-28 21:41:53 UTC
GPL Ghostscript 8.15 running on Windows XP does not exhibit this bug.

(At this precise moment in time, it's easier for me to try Ghostscript 8.xx
under Windows than Linux. Hopefully I will have a chance to change that this
evening, but in the meantime I figure that knowing how GS 8.15 reacts on Windows
is better than *nothing*.)

Comment 4 Tim Waugh 2005-06-07 11:29:34 UTC
8.15-0.rc3.1 processes this file correctly for me, so this will be fixed in FC5.

Note You need to log in before you can comment on or make changes to this bug.