Bug#618530: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input

2011-03-20 Thread Jonathan Nieder
fixed 618530 ghostscript/8.71~dfsg2-6 found 618530 ghostscript/8.71~dfsg2-6.1 found 618530 ghostscript/9.01~dfsg-2 tags 618530 + confirmed # regression severity 618530 important retitle 618530 gs -dSAFER: /invalidfileaccess with run operator forcemerge 414002 618530 quit Hi again, Ralph Smith

Bug#618530: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input

2011-03-19 Thread Ralph Smith
Surprisingly, the invalid file access does not occur in any of the versions you suggested, but returns when I upgrade to the current version (8.71~dfsg2-9). For each case, I installed ghostscript, libgs8 and gs-common debs for the test. On Tue, Mar 15, 2011 at 9:36 PM, Jonathan Nieder

Bug#618530: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input

2011-03-15 Thread Ralph A. Smith
Package: ghostscript Version: 8.71~dfsg2-9 Severity: normal The behavior of the -dSAFER flag has changed between versions of Ghostscript in Lenny and Squeeze. It now prevents -sOutputFile from working if the input is taken interactively or from a pipe. For example: user@host:path$ gs -q

Bug#618530: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input

2011-03-15 Thread Jonathan Nieder
Hi Ralph, Ralph A. Smith wrote: user@host:path$ gs -q -dSAFER -dSAFINTERPOLATE -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -sDEVICE=ppmraw -r144 -sOutputFile=foo.ppm GS(foo.ps) run Error: /invalidfileaccess in --run-- Operand stack: (foo.ps) (r) ... Thanks for reporting. Could you try