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

Bug#932246: Re : Bug#932246: Re : Bug#932246: printer-driver-hpcups: no more printing to a HP LaserJet 1320: stack smashing detected and hpcups crashed on signal 6



On Sun 22 Sep 2019 at 00:17:15 +0100, Brian Potkin wrote:

> On Sat 21 Sep 2019 at 22:25:25 +0200, Francesco Poli wrote:
> 
> > On Sat, 21 Sep 2019 19:14:07 +0100 Brian Potkin wrote:
> > 
> > > On Sat 21 Sep 2019 at 17:45:06 +0200, Francesco Poli wrote:
> > [...]
> > > > Unless I am misinterpreting something, this bug seems to have vanished
> > > > or have been fixed in printer-driver-hpcups/3.19.8+dfsg0-1
> > > 
> > > You are not using printer-driver-hpcups.
> > 
> > Am I not?!?
> 
> Not according to the PPD you used to set up the queue.
> 
>  > -m drv:///hpijs.drv/hp-laserjet_1320-hpijs.ppd
> 
> An hpijs PPD doesn't use the hpcups filter.

I stand by that, but please see later on.

> > > > I do not understand why other users seem to get different experiences...
> > > 
> > > Perhaps you could set up a queue with printer-driver-hpcups to gain some
> > > understanding.
> > 
> > I thought that
> > 
> >   # lpadmin -x lj
> >   # lpadmin -p lj -E \
> >     -v 'usb://HP/LaserJet%201320%20series?serial=00CNFW522KS9' \
> >     -m drv:///hpijs.drv/hp-laserjet_1320-hpijs.ppd \
> >     -o pdftops-renderer-default=pdftops \
> >     -L local -D "HP LaserJet 1320"
> >   lpadmin: Printer drivers are deprecated and will stop working in a future version of CUPS.
> >   # lpoptions -p lj -o media=A4 -o sides=two-sided-long-edge
> >   # lpadmin -d lj
> > 
> > did set up a queue with printer-driver-hpcups.
> 
> The hp-laserjet_1320-hpijs.ppd is not in printer-driver-hpcups.

I stand by that too, but it turns out it is irrelevant.
 
> > At the very least, this was the queue where I originally experienced the
> > bug (please remember that I am the original bug report submitter!).
> > And the error log said that "/usr/lib/cups/filter/hpcups" had "crashed
> > on signal 6".
> > And
> > 
> >   $ dpkg -S /usr/lib/cups/filter/hpcups
> >   printer-driver-hpcups: /usr/lib/cups/filter/hpcups
> > 
> > This is what made me conclude that the bug was in package
> > printer-driver-hpcups.
> 
> It could be me who is confused.

My confusion arose because an hpijs queue was set up but an hpcups
filter was clearly being used. I have just recollected #686653:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686653

It is best to read the last four or five mails first to understand what
led to a resolution in that report and what happened to Francesco's
setup to change the PPD used.

At some stage new hplip packages became available and the update updated
the hpijs PPD files. We read in the hplip changelog:

  * debian/hplip-cups.postinst, debian/hpijs.postinst: Switch to hpcups as
    default driver (migrate HPIJS queues to hpcups). The problem of Ghostscript
    segfaulting when generating CUPS raster data is solved and the hpcups
    driver needs also more testing.

 -- Till Kamppeter <till.kamppeter@gmail.com>  Thu,  3 Jun 2010 15:36:18 +0200

The original hpijs PPD was silently migrated to an hpcups PPD and the
bug that is the subject of this report is then experienced.

Cheers,

Brian.


Reply to: