Bug#932246: printer-driver-hpcups: no more printing to a HP LaserJet 1320: stack smashing detected and hpcups crashed on signal 6
Package: printer-driver-hpcups Version: 3.20.5+dfsg0-2 Followup-For: Bug #932246 Dear Maintainer, The bug is still present in 3.20.5+dfsg0-2. Printer: Laserjet 1200 /usr/lib/os-release Pretty Name: Debian GNU/Linux bullseye/sid Changing the /usr/lib/os-release Pretty Name to "Debian GNU/Linux bullseye" eliminates the segfault. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.19.0-5-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages printer-driver-hpcups depends on: ii cups 2.3.3-1 ii cups-filters [ghostscript-cups] 1.27.4-1+b1 ii libc62.30-4 ii libcups2 2.3.3-1 ii libdbus-1-3 1.12.16-2 ii libgcc-s110-20200502-1 ii libhpmud03.20.5+dfsg0-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libstdc++6 10-20200502-1 ii zlib1g 1:1.2.11.dfsg-2 printer-driver-hpcups recommends no packages. Versions of packages printer-driver-hpcups suggests: ii hplip 3.20.5+dfsg0-2 pn hplip-doc -- debconf-show failed
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
>> FWIW, I have 3.19.8+dfsg0-7 installed and am still seeing this problem. > Knowing the printer model is always useful. HP-Deskjet-5150 > The file /usr/lib/os-release has bullseye/sid in PRETTY_NAME. Edit > bullseye/sid to reduce the number of characters to less than 12. > Does this have any effect? Yes, I removed the "/sid" and that worked around the problem (that's how I confirmed that it was still the same problem, before sending my previous message ;-) Stefan
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 Wed 09 Oct 2019 at 17:26:02 -0400, Stefan Monnier wrote: > > That'll be 3.19.8+dfsg0-4, uploaded later tonight. It will also ship > > autopkgtests, to also test hplip printing on fake printers. > > FWIW, I have 3.19.8+dfsg0-7 installed and am still seeing this problem. Knowing the printer model is always useful. The file /usr/lib/os-release has bullseye/sid in PRETTY_NAME. Edit bullseye/sid to reduce the number of characters to less than 12. Does this have any effect? Cheers, Brian.
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
> That'll be 3.19.8+dfsg0-4, uploaded later tonight. It will also ship > autopkgtests, to also test hplip printing on fake printers. FWIW, I have 3.19.8+dfsg0-7 installed and am still seeing this problem. Stefan
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 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.
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 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 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. > 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. Cheers, Brian.
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 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?!? > > > 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. 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. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpb_aMIk1HPD.pgp Description: PGP signature
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.
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
Le samedi, 21 septembre 2019, 14.07:18 h CEST Didier 'OdyX' Raboud a écrit : > (It seems this whole "detect the distro and try being smart" should be > removed completely from Debian's hplip). With this in mind, I've prepared an hplip version which totally skips the guessing parts: def validate_distro_version(self): -if self.validate_disto(): -for vers in self.distros[self.distro_name]['versions']: -if self.distro_version == vers: -return True - -return False +# It's shipped in Debian. It's supported. +return True def is_auto_installer_support(self, distro_version=DISTRO_VER_UNKNOWN): -if not self.distro_name: -self.get_distro() - (… etc etc …) +# No auto install ever. +return False It will also forbid the hp-* tools to try to install supposedly missing dependencies themselves. Debian has package dependencies for a reason. That'll be 3.19.8+dfsg0-4, uploaded later tonight. It will also ship autopkgtests, to also test hplip printing on fake printers. Hopefully, that'll help for a better hplip on the long-term! Cheers, OdyX signature.asc Description: This is a digitally signed message part.
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 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:
$ apt policy hplip-data
hplip-data:
Installed: (none)
Candidate: 3.19.8+dfsg0-1
Version table:
3.19.8+dfsg0-3 500
500 http://deb.debian.org/debian unstable/main i386 Packages
3.19.8+dfsg0-1 800
800 http://deb.debian.org/debian testing/main i386 Packages
$ apt policy printer-driver-hpcups
printer-driver-hpcups:
Installed: 3.19.8+dfsg0-1
Candidate: 3.19.8+dfsg0-1
Version table:
3.19.8+dfsg0-3 500
500 http://deb.debian.org/debian unstable/main i386 Packages
*** 3.19.8+dfsg0-1 800
800 http://deb.debian.org/debian testing/main i386 Packages
100 /var/lib/dpkg/status
>
> (It seems this whole "detect the distro and try being smart" should be
> removed
> completely from Debian's hplip).
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!).
# 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
$ apt policy base-files
base-files:
Installed: 11
Candidate: 11
Version table:
*** 11 800
800 http://deb.debian.org/debian testing/main i386 Packages
500 http://deb.debian.org/debian unstable/main i386 Packages
100 /var/lib/dpkg/status
$ python
Python 2.7.16+ (default, Sep 4 2019, 08:19:57)
[GCC 9.2.1 20190827] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import platform
>>> dist = platform.dist()
>>> dist
('debian', 'bullseye/sid', '')
>>>
$ python3
Python 3.7.4+ (default, Sep 4 2019, 08:03:05)
[GCC 9.2.1 20190827] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import platform
>>> dist = platform.dist()
__main__:1: DeprecationWarning: dist() and linux_distribution() functions are
deprecated in Python 3.5
>>> dist
('debian', 'bullseye/sid', '')
>>>
$ echo hello | lpr
$ lpq
lj is ready and printing
RankOwner Job File(s) Total Size
active USER368 (stdin) 1024 bytes
$ lpq
lj is ready
no entries
It works with no issues: I got a wonderful (well, sort of wonderful...)
page with the "hello" string printed on one of its sides...
Unless I am misinterpreting something, this bug seems to have vanished
or have been fixed in printer-driver-hpcups/3.19.8+dfsg0-1
I do not understand why other users seem to get different experiences...
--
http://www.inventati.org/frx/
There's not a second to spare! To the laboratory!
. Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgppizHpEBwk3.pgp
Description: PGP signature
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 10:53:04 +0200, Francesco Poli wrote: > On Sat, 21 Sep 2019 09:33:25 +0200 nicolas.patr...@gmail.com wrote: > > > Le 21/09/2019 00:02:42, Brian Potkin a écrit : > > > > > No idea. I haven't even begun to think about it because I was awaiting > > > confirmation or otherwise. > > > > I checked it again this morning after the morning upgrade. > > Version 11 crashes printing. > > Downgrading to version 10.3+deb10u1 makes it work back again. > > What's this? Magic?!?:-o Must be! It has exerted its influence across the English Channel and affected my machine! A little test, using either the technique I gave earlier or by printing: The first line of /usr/lib/os-release has "bullseye/sid" in it. There are eight characters in "bullseye". Remove any one of them and print. Also - leave the eight characters there and remove the forward slash. Now, who is to deal with this? Upstream HPLIP, upstream systemd or the base-files maintainer? > I compared the two source packages of base-files (10.3+deb10u1 vs. 11), > see the attached diff output. > I really cannot see any relevant difference. > 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?!? I do not understand code but, for some reason, /etc/os-release is opened in common/utils.c. Regards, Brian.
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
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.
hplip uses its own internal list of supported distros, in
/usr/share/hplip/installer/distros.dat
… shipped from hplip-data.
It only gained "Buster" support in 3.19.8; so could any of you try to install
distros.dat from
https://salsa.debian.org/printing-team/hplip/raw/debian/3.19.8+dfsg0-3/
installer/distros.dat
into /usr/share/hplip/installer/distros.dat, and try printing again?
(That is:
wget -q 'https://salsa.debian.org/printing-team/hplip/raw/debian/
3.19.8+dfsg0-3/installer/distros.dat' -O - | sudo tee /usr/share/hplip/
installer/distros.dat
)
I'm not sure it will work, as printer-driver-hpcups doesn't depend on hplip-
data anyway; *sigh*.
(It seems this whole "detect the distro and try being smart" should be removed
completely from Debian's hplip).
Cheers,
OdyX
signature.asc
Description: This is a digitally signed message part.
Bug#932246: Re : 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
Le 21/09/2019 10:53:04, Francesco Poli a écrit : > What's this? Magic?!?:-o I don’t know. My machine begins to be old and crashed yesterday. Nothing changed after the reboot. Regards, nicolas patrois : pts noir asocial -- RÉALISME M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ? P : Non... Une carte bleue suffirait...
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 09:33:25 +0200 nicolas.patr...@gmail.com wrote: > Le 21/09/2019 00:02:42, Brian Potkin a écrit : > > > No idea. I haven't even begun to think about it because I was awaiting > > confirmation or otherwise. > > I checked it again this morning after the morning upgrade. > Version 11 crashes printing. > Downgrading to version 10.3+deb10u1 makes it work back again. What's this? Magic?!?:-o I compared the two source packages of base-files (10.3+deb10u1 vs. 11), see the attached diff output. I really cannot see any relevant difference. 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?!? -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE diff -ruN base-files-10.3+deb10u1/debian/changelog base-files-11/debian/changelog --- base-files-10.3+deb10u1/debian/changelog 2019-08-30 14:31:26.0 +0200 +++ base-files-11/debian/changelog 2019-07-09 12:05:50.0 +0200 @@ -1,8 +1,11 @@ -base-files (10.3+deb10u1) buster; urgency=medium +base-files (11) unstable; urgency=medium - * Change /etc/debian_version to 10.1, for Debian 10.1 point release. + * Change issue, issue.net, debian_version and os-release to read +"bullseye/sid". + * Drop VERSION, VERSION_ID and CODENAME from os-release. + * Make "mesg n" silent in default /root/.profile. Closes: #930654. - -- Santiago Vila Fri, 30 Aug 2019 14:31:26 +0200 + -- Santiago Vila Tue, 09 Jul 2019 12:05:50 +0200 base-files (10.3) unstable; urgency=medium diff -ruN base-files-10.3+deb10u1/etc/debian_version base-files-11/etc/debian_version --- base-files-10.3+deb10u1/etc/debian_version 2019-08-30 09:00:00.0 +0200 +++ base-files-11/etc/debian_version 2019-07-09 12:00:00.0 +0200 @@ -1 +1 @@ -10.1 +bullseye/sid diff -ruN base-files-10.3+deb10u1/etc/issue base-files-11/etc/issue --- base-files-10.3+deb10u1/etc/issue 2019-04-19 13:00:00.0 +0200 +++ base-files-11/etc/issue 2019-07-09 12:00:00.0 +0200 @@ -1,2 +1,2 @@ -Debian #OSNAME# 10 \n \l +Debian #OSNAME# bullseye/sid \n \l diff -ruN base-files-10.3+deb10u1/etc/issue.net base-files-11/etc/issue.net --- base-files-10.3+deb10u1/etc/issue.net 2019-04-19 13:00:00.0 +0200 +++ base-files-11/etc/issue.net 2019-07-09 12:00:00.0 +0200 @@ -1 +1 @@ -Debian #OSNAME# 10 +Debian #OSNAME# bullseye/sid diff -ruN base-files-10.3+deb10u1/etc/os-release base-files-11/etc/os-release --- base-files-10.3+deb10u1/etc/os-release 2019-04-19 13:00:00.0 +0200 +++ base-files-11/etc/os-release 2019-07-09 12:00:00.0 +0200 @@ -1,8 +1,5 @@ -PRETTY_NAME="Debian #OSNAME# 10 (buster)" +PRETTY_NAME="Debian #OSNAME# bullseye/sid" NAME="Debian #OSNAME#" -VERSION_ID="10" -VERSION="10 (buster)" -VERSION_CODENAME=buster ID=debian HOME_URL="https://www.debian.org/; SUPPORT_URL="https://www.debian.org/support; diff -ruN base-files-10.3+deb10u1/share/dot.profile base-files-11/share/dot.profile --- base-files-10.3+deb10u1/share/dot.profile 2015-08-17 17:30:33.0 +0200 +++ base-files-11/share/dot.profile 2019-07-09 12:05:50.0 +0200 @@ -6,4 +6,4 @@ fi fi -mesg n || true +mesg n 2> /dev/null || true pgp4Kbx7WvWJq.pgp Description: PGP signature
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
Le 21/09/2019 00:02:42, Brian Potkin a écrit : > No idea. I haven't even begun to think about it because I was awaiting > confirmation or otherwise. I checked it again this morning after the morning upgrade. Version 11 crashes printing. Downgrading to version 10.3+deb10u1 makes it work back again. Regards, nicolas patrois : pts noir asocial -- RÉALISME M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ? P : Non... Une carte bleue suffirait...
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 Fri 20 Sep 2019 at 23:23:48 +0200, Francesco Poli wrote: > On Fri, 20 Sep 2019 18:59:29 +0200 nicolas.patr...@gmail.com wrote: > > > Le 20/09/2019 15:08:37, Brian Potkin a écrit : [...] > > > Would you and Nicolas download buster's base-files package from > > > > > > > > http://snapshot.debian.org/package/base-files/10.3%2Bdeb10u1/#base-files_10.3:2b:deb10u1 > > > > > and install it with 'dpkg -i ...'? How's that for printing? > > > > It works for me. > > Yay. > > I haven't tried yet. And, since I managed to work around the bug by > changing driver, I am not sure I will find the time to perform the test > real soon now... > > But anyway, this looks like the weirdest test I have ever been > requested to perform: how can a downgrade of base-files affect my > ability to print via printer-driver-hpcups?!? No idea. I haven't even begun to think about it because I was awaiting confirmation or otherwise. > Could you please clarify why you think that downgrading base-files > might help? And, above all, why it has worked for Nicolas? An evening, morning and part of an afternoon of installing and testing contributed to advancing the suggestion I made. > I am really curious! But not that curious. :) Cheers, Brian.
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 Fri, 20 Sep 2019 18:59:29 +0200 nicolas.patr...@gmail.com wrote: > Le 20/09/2019 15:08:37, Brian Potkin a écrit : > > > We all would, Francesco. Thanks for your clear, detailed report. Hello Brian, you are welcome. > > > As far as can tell, this affects queues set up with printer-driver-ijs > > and printer-driver-hpcups, and all the raster printer models I tested > > are affected. For testing I used > > > cupsfilter -p -m printer/foo -e > > /etc/nsswitch.conf > out.dat As far as my own printer (HP LaserJet 1320) is concerned, I've been able to work around the bug by changing driver: # lpadmin -x lj # lpadmin -p lj -E \ -v 'usb://HP/LaserJet%201320%20series?serial=00CNFW522KS9' \ -m foomatic:HP-LaserJet_1320-pxlmono.ppd \ -o pdftops-renderer-default=pdftops \ -L local -D "HP LaserJet 1320" # lpoptions -p lj -o media=A4 -o sides=two-sided-long-edge # lpadmin -d lj I guess this other driver has nothing to do with printer-driver-ijs or printer-driver-hpcups... > > > Would you and Nicolas download buster's base-files package from > > > > > http://snapshot.debian.org/package/base-files/10.3%2Bdeb10u1/#base-files_10.3:2b:deb10u1 > > > and install it with 'dpkg -i ...'? How's that for printing? > > It works for me. > Yay. I haven't tried yet. And, since I managed to work around the bug by changing driver, I am not sure I will find the time to perform the test real soon now... But anyway, this looks like the weirdest test I have ever been requested to perform: how can a downgrade of base-files affect my ability to print via printer-driver-hpcups?!? Could you please clarify why you think that downgrading base-files might help? And, above all, why it has worked for Nicolas? I am really curious! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpIxqk1JKels.pgp Description: PGP signature
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
Le 20/09/2019 15:08:37, Brian Potkin a écrit : > We all would, Francesco. Thanks for your clear, detailed report. > As far as can tell, this affects queues set up with printer-driver-ijs > and printer-driver-hpcups, and all the raster printer models I tested > are affected. For testing I used > cupsfilter -p -m printer/foo -e > /etc/nsswitch.conf > out.dat > Would you and Nicolas download buster's base-files package from > > http://snapshot.debian.org/package/base-files/10.3%2Bdeb10u1/#base-files_10.3:2b:deb10u1 > and install it with 'dpkg -i ...'? How's that for printing? It works for me. Yay. Regards, nicolas patrois : pts noir asocial -- RÉALISME M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ? P : Non... Une carte bleue suffirait...
Bug#932246: printer-driver-hpcups: no more printing to a HP LaserJet 1320: stack smashing detected and hpcups crashed on signal 6
On Tue 16 Jul 2019 at 23:50:42 +0200, Francesco Poli (wintermute) wrote: [...] > Since hpcups seems to crash on signal 6 after a "stack smashing" > was detected, I tried to upgrade to printer-driver-hpcups from > experimental: > > > [UPGRADE] printer-driver-hpcups:i386 3.18.12+dfsg0-2 -> 3.19.6+dfsg0-1 > > > But this didn't help. > I tried to downgrade many packages (all the way back to last Saturday), > but to no avail. > I cannot even understand which package upgrade broke my setup... > > Please help me to investigate: I cannot print anymore, and I > would love to solve this issue. We all would, Francesco. Thanks for your clear, detailed report. As far as can tell, this affects queues set up with printer-driver-ijs and printer-driver-hpcups, and all the raster printer models I tested are affected. For testing I used cupsfilter -p -m printer/foo -e /etc/nsswitch.conf > out.dat Would you and Nicolas download buster's base-files package from http://snapshot.debian.org/package/base-files/10.3%2Bdeb10u1/#base-files_10.3:2b:deb10u1 and install it with 'dpkg -i ...'? How's that for printing? Regards, Brian.
Bug#932246: printer-driver-hpcups: no more printing to a HP LaserJet 1320: stack smashing detected and hpcups crashed on signal 6
Package: printer-driver-hpcups Version: 3.18.12+dfsg0-2 Severity: important Dear Debian Printing Team, I have a small i386 box (Soekris net5501) running testing (buster before July the 6th, 2019, now bullseye) and connected to a HP LaserJet 1320 printer via USB cable. The printer is configured via the following command lines: # 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" # lpoptions -p lj -o media=A4 -o sides=two-sided-long-edge # lpadmin -d lj The setup has worked fine until July the 9th (that is to say, even after the first bullseye package upgrades): during that day, I printed a PDF file without issues. After that, I went on upgrading the box for about a week: [UPGRADE] tzdata:i386 2019a-1 -> 2019b-1 [UPGRADE] chrony:i386 3.4-4 -> 3.5-2 [UPGRADE] dirmngr:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gnupg:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gnupg-l10n:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gnupg-utils:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gnupg2:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gpg:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gpg-agent:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gpg-wks-client:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gpg-wks-server:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gpgconf:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gpgsm:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] gpgv:i386 2.2.12-1 -> 2.2.13-2 [UPGRADE] libnewt0.52:i386 0.52.20-8 -> 0.52.21-1 [UPGRADE] libsystemd0:i386 241-5 -> 241-6 [UPGRADE] libudev1:i386 241-5 -> 241-6 [UPGRADE] nano:i386 3.2-3 -> 4.3-1 [UPGRADE] openssh-client:i386 1:7.9p1-10 -> 1:8.0p1-3 [UPGRADE] openssh-server:i386 1:7.9p1-10 -> 1:8.0p1-3 [UPGRADE] openssh-sftp-server:i386 1:7.9p1-10 -> 1:8.0p1-3 [UPGRADE] udev:i386 241-5 -> 241-6 [UPGRADE] whiptail:i386 0.52.20-8 -> 0.52.21-1 [UPGRADE] libassuan0:i386 2.5.2-1 -> 2.5.3-2 [UPGRADE] libedit2:i386 3.1-20181209-1 -> 3.1-20190324-1 [UPGRADE] libgpg-error0:i386 1.35-1 -> 1.36-2 [UPGRADE] libpci3:i386 1:3.5.2-1 -> 1:3.6.2-2 [UPGRADE] pciutils:i386 1:3.5.2-1 -> 1:3.6.2-2 [UPGRADE] usbutils:i386 1:010-3 -> 1:012-1 [REMOVE, NOT USED] libip4tc0:i386 1.8.2-4 [REMOVE, NOT USED] libip6tc0:i386 1.8.2-4 [INSTALL, DEPENDENCIES] libip4tc2:i386 1.8.3-2 [INSTALL, DEPENDENCIES] libip6tc2:i386 1.8.3-2 [UPGRADE] base-files:i386 10.3 -> 11 [UPGRADE] iptables:i386 1.8.2-4 -> 1.8.3-2 [UPGRADE] libiptc0:i386 1.8.2-4 -> 1.8.3-2 [UPGRADE] libnftnl11:i386 1.1.2-2 -> 1.1.3-2 [UPGRADE] libsystemd0:i386 241-6 -> 241-6+b1 [UPGRADE] libudev1:i386 241-6 -> 241-6+b1 [UPGRADE] libxtables12:i386 1.8.2-4 -> 1.8.3-2 [UPGRADE] login:i386 1:4.5-1.1 -> 1:4.7-1 [UPGRADE] passwd:i386 1:4.5-1.1 -> 1:4.7-1 [UPGRADE] startpar:i386 0.61-1 -> 0.63-1 [UPGRADE] udev:i386 241-6 -> 241-6+b1 [UPGRADE] bzip2:i386 1.0.6-9.1 -> 1.0.6-9.2 [UPGRADE] exim4:i386 4.92-8 -> 4.92-9 [UPGRADE] exim4-base:i386 4.92-8 -> 4.92-9 [UPGRADE] exim4-config:i386 4.92-8 -> 4.92-9 [UPGRADE] exim4-daemon-light:i386 4.92-8 -> 4.92-9 [UPGRADE] info:i386 6.5.0.dfsg.1-4+b1 -> 6.6.0.dfsg.1-2 [UPGRADE] install-info:i386 6.5.0.dfsg.1-4+b1 -> 6.6.0.dfsg.1-2 [UPGRADE] iproute2:i386 4.20.0-2 -> 5.2.0-1 [UPGRADE] libbz2-1.0:i386 1.0.6-9.1 -> 1.0.6-9.2 [UPGRADE] libgnutls-dane0:i386 3.6.7-4 -> 3.6.8-2 [UPGRADE] libgnutls30:i386 3.6.7-4 -> 3.6.8-2 [UPGRADE] manpages:i386 4.16-2 -> 5.01-1 [UPGRADE] rsyslog:i386 8.1901.0-1 -> 8.1907.0-1 [UPGRADE] runit-helper:i386 2.8.6 -> 2.8.13.2 Yesterday, I tried to print a PDF file and I found out that the hpcups crashed and printing was no longer possible. Even a simple $ echo hello | lpr generates a print job that never vanishes: $ lpq lj is ready RankOwner Job File(s) Total Size 1st unknown 348 unknown 1024 bytes but the data seem to never reach the printer and /var/log/cups/error_log shows the following error messages: E [16/Jul/2019:23:08:14 +0200] [Job 348] Job stopped due to filter errors; please consult the /var/log/cups/error_log file for details. D [16/Jul/2019:23:08:14 +0200] [Job 348] The following messages were recorded from 11:08:01 PM to 11:08:14 PM D [16/Jul/2019:23:08:14 +0200] [Job 348] Applying default options... D [16/Jul/2019:23:08:14 +0200] [Job 348] Adding start banner page "none". D [16/Jul/2019:23:08:14 +0200] [Job 348] Queued on "lj" by "USER". D [16/Jul/2019:23:08:14 +0200] [Job 348] Auto-typing file... D [16/Jul/2019:23:08:14 +0200] [Job 348] Request file type is text/plain. D [16/Jul/2019:23:08:14 +0200] [Job 348] File of type text/plain queued by "USER". D [16/Jul/2019:23:08:14 +0200] [Job 348] Adding end banner page "none". D [16/Jul/2019:23:08:14 +0200] [Job 348]
