Re: [Bug-AUCTeX] 11.86; pngs not being generated by preview-latex

[Clark Taylor]

My error log follows (from the middle mouse button).  Thank you for your help!

"GSWIN32C.EXE" "-dOutputFile=(_region_.prv/tmp3712kvc/pr1-1.png)" "-q"
"-dSAFER" "-dNOPAUSE" "-DNOPLATFONTS" "-dPrinted" "-dTextAlphaBits=4"
"-dGraphicsAlphaBits=4" "-sDEVICE=png16m" "-r70.4906x70.6156"
GS>{DELAYSAFER{.setsafe}if}stopped pop/.preview-BP
currentpagedevice/BeginPage get dup null eq{pop{pop}bind}if
def<</BeginPage{currentpagedevice/PageSize get dup 0 get 1 ne exch 1
get 1 ne or{.preview-BP }{pop}ifelse}bind/PageSize[1
1]>>setpagedevice/preview-do{[count 3 roll save]3 1 roll dup length 0
eq{pop}{setpagedevice}{ifelse .runandhide}stopped{handleerror quit}if
aload pop restore}bind def
[(_region_.prv/tmp3712kvc/preview.dsc)(r)file]aload exch dup 0
setfileposition 520()/SubFileDecode filter cvx .runandhide aload pop
dup dup 623 setfileposition 50()/SubFileDecode filter
cvx<<>>preview-do
Error: /invalidfileaccess in --file--
Operand stack:
   --nostringval--   (_region_.prv/tmp3712kvc/preview.dsc)   (r)
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--
--nostringval--   2   %stopped_push   --nostringval--
--nostringval--   %loop_continue   --nostringval--   --nostringval--
false   1   %stopped_push   .runexec2   --nostringval--
--nostringval--   --nostringval--   2   %stopped_push
--nostringval--
Dictionary stack:
   --dict:1163/1684(ro)(G)--   --dict:0/20(G)--   --dict:79/200(L)--
Current allocation mode is local
Last OS error: No such file or directory
Current file position is 442
GS<3>


On Mon, Oct 11, 2010 at 9:10 AM, Ralf Angeli <address@hidden> wrote:
>
> * Clark Taylor (2010-10-11) writes:
>
> > On Sun, Oct 10, 2010 at 3:20 PM, Ralf Angeli <address@hidden> wrote:
> >>
> >> All the output you included in the mail is not done with TeX PDF mode
> >> active.  It would be interesting to see the output when the mode is
> >> active and the route via the .dsc file is actually chosen.  It would
> >> also be interesting to know if TeX PDF mode being active or not makes a
> >> difference.
> >>
> > I turned off pdf mode and have the same result.  On other computers, I
> > have always done this in the past with pdf mode on and it has worked
> > fine.
>
> Hm, recently there have been some reports where problems were confined
> to PDF output only.  The fact that you get the "no entry" signs with DVI
> output as well seems to suggest that this is a different one.
>
> If you click with mouse-2 on one of those signs, what's the output you
> get?
>
> > The two things that are different this time (that I can think of) from
> > my normal installs are that (1) this is the first time I have been
> > using Vista and (2) Ghostscript seems to be a new version (9.0.0).
>
> Yes, Ghostscript is also on my shortlist of culprits.  The Debian
> maintainer is in course of packaging the new version, so hopefully I'll
> be able to test with it in the near future without having to install it
> manually.
>
> >> By the way, please don't send HTML mails to the AUCTeX mailing lists.
> >> Plain text can convey the information satisfactorily and does not waste
> >> so much space and bandwidth.
> >>
> > Sorry about that.  I got lazy and forgot to check.  Fixed for this
> > e-mail (I hope!)
>
> Thanks!
>
> --
> Ralf