Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 30573 - gv/gs broken by installed RH 7.0
gv/gs broken by installed RH 7.0
Product: Red Hat Linux
Classification: Retired
Component: ghostscript (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Crutcher Dunnavant
Aaron Brown
Depends On:
  Show dependency treegraph
Reported: 2001-03-04 17:16 EST by Darrell Long
Modified: 2007-04-18 12:31 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-04 17:16:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Darrell Long 2001-03-04 17:16:23 EST
I upgraded from 6.2 to 7.0 (which, while I'm at it, did not create
/etc/X11/xdm/Xsession like it should) it broke gv 3.5.8 for all PDF files.
gs 6.50 runs beneath it. It previously worked with no difficulty under RH

Here is an example:

[darrell@sequoia ~]$ gv special.pdf 
Error: /invalidfileaccess in (w)
Operand stack:
   DSCfile   (/home/darrell/gv_3aa2be80_1_special.pdf.tmp)
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--  
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--  
--nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1  
3   %oparray_pop   1   3   %oparray_pop   .runexec2   --nostringval--  
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--  
3   3   %oparray_pop   --nostringval--   --nostringval--
Dictionary stack:
   --dict:985/1476(ro)(G)--   --dict:0/20(G)--   --dict:67/200(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 2290
AFPL Ghostscript 6.50: Unrecoverable error, exit code 1
Comment 1 Crutcher Dunnavant 2001-04-04 17:08:46 EDT
gs 6.5 is not supported

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