--- Begin Message ---
- To: Debian Bug Reporting <submit@bugs.debian.org>
- Subject: gs cannot view /usr/share/gs/6.53/gs_init.ps
- From: Dan Hatton <dan.hatton@btinternet.com>
- Date: Sat, 17 May 2003 00:58:25 +0100 (BST)
- Message-id: <Pine.LNX.4.33.0305170024160.3029-100000@localhost.localdomain>
Package:gs
Version:6.53-3
gs gs_init.ps, run directly from the command line, dies with the error
message:
GNU Ghostscript 6.53 (2002-02-13)
Copyright (C) 2002 artofcode LLC, Benicia, CA. All rights reserved.
This software comes with NO WARRANTY: see the file COPYING for
details.
Error: /invalidaccess in def
Operand stack:
--nostringval--
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-- --nostringval-- --nostringval--
Dictionary stack:
--dict:1034/1476(ro)(G)-- --dict:0/20(G)-- --dict:67/200(L)--
--dict:1034/1476(ro)(G)--
Current allocation mode is global
Current file position is 2820
GNU Ghostscript 6.53: Unrecoverable error, exit code 1
When gs is run on gs_init.ps, through the gv front-end, it fails to
show me anything, with a very similar error message.
When gs is run on gs_init.ps, through the lpr front-end, the text of
the postscript file appears to get sent through a2ps before printing
(this also happens with align.ps.)
I have made sure that the gs_init.ps I'm trying to display/print is
that distributed with Debian, not one of my edited versions, first by
checking out the original version from my own RCS repository, then by
down-loading the source code for gs 6.53-3, and taking the gs_init.ps
from there.
None of these anomalies happen for postscript files in general. For
example, my own LaTeX/dvips outputs display/print normally, apart from
the effects of bug #122415.
I found all this out because I had some idea in my head that following
the instructions in gs_init.ps would be a good way to work around bug
#122415. The fact that I had this much of an idea what gs_init.ps
said suggests that the bug I'm reporting may result from something
that's happened in a security update since the original release of
Woody.
Versions of related software:
Linux kernel 2.2.20
libc6 2.2.5-11.5
libgimpprint1 4.2.0-4
libpaperg 1.1.8
libpng2 1.0.12-3.woody.3
xlibs 4.1.0-16
zlib1g 1:1.1.4-1
gs-common 0.3.3.0woody1
gsfonts 6.0-2
psfontmgr 0.11.0
a2ps 4.13b-16
--
Ta
Dan Hatton
<http://www.bib.hatton.btinternet.co.uk/dan/>
--- End Message ---
--- Begin Message ---
- To: 364936-done@bugs.debian.org, 459930-done@bugs.debian.org, 169678-done@bugs.debian.org, 587272-done@bugs.debian.org, 193775-done@bugs.debian.org, 115122-done@bugs.debian.org, 175267-done@bugs.debian.org, 177763-done@bugs.debian.org, 193609-done@bugs.debian.org, 194147-done@bugs.debian.org, 208941-done@bugs.debian.org, 213695-done@bugs.debian.org, 280473-done@bugs.debian.org, 103301-done@bugs.debian.org, 128890-done@bugs.debian.org, 144256-done@bugs.debian.org, 116266-done@bugs.debian.org, 16285-done@bugs.debian.org, 56968-done@bugs.debian.org, 71897-done@bugs.debian.org
- Subject: Closing orphan/obsolete bugs (gs and gs-aladdin)
- From: "Manuel A. Fernandez Montecelo" <manuel.montezelo@gmail.com>
- Date: Thu, 5 Jul 2012 15:26:04 +0100
- Message-id: <CAPQ4b8kkvW2C65NtVY71GFdiwf5O1D7AsHZUFK7mRdR5KstUFA@mail.gmail.com>
Hello,
Thanks for your interest in Debian, and sorry that the bugs were not
attended in due time.
gs and gs-aladdin were removed from Debian unstable long ago [1], 8+
years, at least with that package name.
Many of these reports don't have new information for years, or never
were really followed up by the people involved at the time; some even
without any activity for 10 to 15 years. Two or three of the reports
were indeed confirmed and cloned as bugs to the more recent
"ghostscript" package.
[1] http://packages.qa.debian.org/g/gs.html
[2] http://packages.qa.debian.org/g/gs-aladdin.html
The bugs are now orphan (no maintainer assigned), so they are not
going to be noticed by anybody and dealt with, and indeed many of them
were already marked as unreproducible or contain references to files
never provided, and needed to reproduce the bug.
For all of the reasons stated, I am thus closing the bug reports now.
If somebody wants to keep them open, please reconfirm that they are
still happening and assign them to a current package, so they are not
orphan and can really be tracked.
Regards.
--- End Message ---