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

Bug#177763: marked as done (gs prints core dump, bypassing lpd (and thus unstoppable))

Your message dated Thu, 5 Jul 2012 15:26:04 +0100
with message-id <CAPQ4b8kkvW2C65NtVY71GFdiwf5O1D7AsHZUFK7mRdR5KstUFA@mail.gmail.com>
and subject line Closing orphan/obsolete bugs (gs and gs-aladdin)
has caused the Debian Bug report #177763,
regarding gs prints core dump, bypassing lpd (and thus unstoppable)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
177763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=177763
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gs
Version: 6.53-3

I have been printing using lprng and my Epson Stylus Color 660 for some time
now.  Today I turned on the printer and it began printing the sort of
gibberish found when a job is interrupted mid-print.  After three lines it
segued into  a long apparent core dump. 

I quickly checked lpq, and found job 648 listed as aborted.  Using lprm on
that job did nothing.  In desperation I killed lpd AND THE CORE DUMP KEPT
PRINTING. 

25 pages later I remembered "lsof", which told me that gs was using
/dev/lp0.  Killing gs finally stopped the printing and let me print
normally.

Sorry, I don't want to type the entire core dump into this message.  It
was made up lines like:

0x936a534: 0x0d name --S----- 0x00a5 0x0826f578 = ioerror

but many hundreds of 'em, before I managed to stop the printing.

First, gs shouldn't core dump to the printer.  Second, it shouldn't bypass
lpd, preventing me from cancelling the job.
-- 
Carl Fink		carlf@dm.net
Manager, Dueling Modems Computer Forum
<http://dm.net>

--- End Message ---
--- Begin Message --- 
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 ---
Reply to: