[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#339924: marked as done (advi: fails to display inlined Postscript with current gs)

Your message dated Fri, 17 Feb 2006 10:52:40 +0100
with message-id <20060217095240.GA28728@bryan.is-a-geek.org>
and subject line Bug#339924: advi: fails to display inlined Postscript with current gs
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: advi
Version: 1.6.0-6
Severity: normal


I just discovered that my old advi presentations no longer work. 
Since I have to give a talk next week, I tried to debug it -:)

What happens:
 zadvi /usr/share/doc/advi-examples/examples/test/demo.dvi.gz
  doesn't show inlined postscript but complains:
   Warning: Setting policy to -exec
   Warning: Error: /invalidfileaccess in --file--
   Warning: Error in Postscript
   Warning: Sys_error("Bad file descriptor")
   Warning: GS Terminated
   Warning: Sys_error("Bad file descriptor")
   Warning: GS Terminated
   ...
  
Reason: advi pipes the follwing to gs:
  ...
  (/usr/share/texmf/dvips/base/texc.pro) run
  (/usr/share/texmf/dvips/base/special.pro) run
  (/usr/share/texmf/dvips/pstricks/pstricks.pro) run
  ...
 
 It seems that this is no longer compatible with the "-dSAFER" option
 of gs, it crashes gs. 

Workaround for me: remove this option from gs.ml
This is perhaps not the best workaround for the package. Perhaps advi
should cat the contents of these files directly to gs?

Regards,  Meik


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages advi depends on:
ii  gs                       8.15-4          Transitional package
ii  gs-esp [gs]              8.15.1.dfsg.1-1 The Ghostscript PostScript interpr
ii  gs-gpl [gs]              8.15-4          The GPL Ghostscript PostScript int
ii  libc6                    2.3.5-8         GNU C Library: Shared libraries an
ii  libfreetype6             2.1.10-1        FreeType 2 font engine, shared lib
ii  libice6                  6.8.2.dfsg.1-10 Inter-Client Exchange library
ii  libjpeg62                6b-10           The Independent JPEG Group's JPEG 
ii  libpng12-0               1.2.8rel-5      PNG library - runtime
ii  libsm6                   6.8.2.dfsg.1-10 X Window System Session Management
ii  libtiff4                 3.7.4-1         Tag Image File Format (TIFF) libra
ii  libungif4g               4.1.4-1         shared library for GIF images (run
ii  libx11-6                 6.8.2.dfsg.1-10 X Window System protocol client li
ii  libxext6                 6.8.2.dfsg.1-10 X Window System miscellaneous exte
ii  libxpm4                  6.8.2.dfsg.1-10 X pixmap library
ii  tetex-bin                3.0-10.1        The teTeX binary files
ii  xlibs                    6.8.2.dfsg.1-10 X Window System client libraries m
ii  zlib1g                   1:1.2.3-6       compression library - runtime

advi recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1.6.0-9

On Fri, Feb 17, 2006 at 10:29:13 +0000, Meik Hellmund wrote:

> I just want to report that this bug is solved in current 
> advi packages. Looks like upstream did his homework:
>   from changelog.Debian:
>   * Update to CVS HEAD as of 20060103,...
> 
> Many thanks to the package maintainer. 
> 
Thank you for following up on this!
I'm now closing this bug.

Cheers,
Julien

--- End Message ---
Reply to: