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 Sat 21 Sep 2019 at 17:45:06 +0200, Francesco Poli wrote:
> On Sat, 21 Sep 2019 14:07:18 +0200 Didier 'OdyX' Raboud wrote:
>
> > Le samedi, 21 septembre 2019, 10.53:04 h CEST Francesco Poli a écrit :
> > > Should we suppose that printer-driver-hpcups reads /etc/os-release
> > > (or /etc/issue* or /etc/debian_version) and decides whether it will
> > > crash, based on this?!?
> >
> > Well. Parts of hplip are in python; and hplip then uses:
> >
> > import platform
> > dist = platform.dist()
> >
> > platform.dist() will try to guess the Linux distro from /etc/lsb-release
> > (should not exist), then /etc/*-{release,version}, hence /etc/os-release.
>
> Ah. This looks really surprising to me...
>
> >
> > hplip uses its own internal list of supported distros, in
> > /usr/share/hplip/installer/distros.dat
> > … shipped from hplip-data.
> [...]
> > I'm not sure it will work, as printer-driver-hpcups doesn't depend on hplip-
> > data anyway; *sigh*.
>
> And indeed, I do not have hplip-data installed:
This is of no consequence; you do not need it to print.
[...]
> Well, I retested the setup with the driver that was crashing on my box.
> I am no longer able to reproduce the bug (without even having to
> downgrade base-files!).
Mine is an up-to-date unstable installation. Using the hpijs driver no
longer produces the stack smashing error. That was not the case when the
report was first filed (I tested at the time we received it). Oh, my
testing today was without hplip-data on the box.
[...]
> 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.
> 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.
Regards,
Brian.
Reply to: