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

Bug#817246: marked as done (gziptoany fails with signal 13 since upgrade to jessie)

Your message dated Thu, 10 Mar 2016 20:16:07 +0100
with message-id <20160310191607.GB12774@fishbowl.rw.madduck.net>
and subject line Re: Bug#817246: gziptoany fails with signal 13 since upgrade to jessie
has caused the Debian Bug report #817246,
regarding gziptoany fails with signal 13 since upgrade to jessie
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.)


-- 
817246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817246
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cups-core-drivers
Version: 2.1.3-3
Severity: normal
File: /usr/lib/cups/filter/gziptoany

Since the upgrade to jessie, we cannot print any longer. Here is the
relevant debug log:

  Started filter /usr/lib/cups/filter/gziptoany (PID 7212)
  Started filter /usr/lib/cups/filter/hpcups (PID 7213)
  Started backend /usr/lib/cups/backend/hp (PID 7214)
  prnt/hpcups/HPCupsFilter.cpp 530: cupsRasterOpen failed, fd = 0
  PID 7212 (/usr/lib/cups/filter/gziptoany) did not catch or ignore signal 13.
  PID 7213 (/usr/lib/cups/filter/hpcups) stopped with status 1.
  Hint: Try setting the LogLevel to "debug" to find out more.
  prnt/backend/hp.c 902: ERROR: null print job total=0
  PID 7214 (/usr/lib/cups/backend/hp) exited with no errors.
  End of messages
  printer-state=3(idle)
  printer-state-message="Filter failed"
  printer-state-reasons=none

as you can see, gziptoany failed without any additional information
that could be useful (the LogLevel hint does not help when debug
level is already selected).

This is reproducible with various different PDF files and only
occurs when printing happens via the network (using ipps://…). The
printer is advertised using the (old) cups broadcast, using
cups-browsed on both server and client. Printing locally on the
print server works fine.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups-core-drivers depends on:
ii  cups-daemon                2.1.3-3
ii  cups-filters-core-drivers  1.8.2-3
ii  libc6                      2.21-9
ii  libcups2                   2.1.3-3

Versions of packages cups-core-drivers recommends:
pn  avahi-daemon  <none>

cups-core-drivers suggests no packages.

-- no debconf information


-- 
 .''`.   martin f. krafft <madduck@d.o> @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)


--- End Message ---
--- Begin Message --- 
also sprach Brian Potkin <claremont102@gmail.com> [2016-03-09 23:19 +0100]:
> >   PID 7212 (/usr/lib/cups/filter/gziptoany) did not catch or ignore signal 13.
> 
> Signal 13 (please see signal(7)) is SIGPIPE. It looks like gziptoany
> tried to write some output to hpcups and it wasn't having anything to do
> with it. This line could be a reaction to the previous one.

Oh of course. For some reason I thought I saw sig11…

> > This is reproducible with various different PDF files and only
> > occurs when printing happens via the network (using ipps://…). The
> > printer is advertised using the (old) cups broadcast, using
> > cups-browsed on both server and client. Printing locally on the
> > print server works fine.
> 
> This sounds as though the problem should be reproducible here. Please
> post full debug logs for client and server for a failed job. The printer
> and PPD would also be useful to know.

I found the problem, thanks to your help. The PPD in use was
*hopelessly* outdated. With the current one in place, it all works
again.

I am sorry for filing this bug report. Had I interpreted the signal
correctly, then I might have looked in the right place right away…

-- 
 .''`.   martin f. krafft <madduck@d.o> @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
"wenn elephanten tanzen leidet das gras."
                                                 -- die vogelpredigt

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)


--- End Message ---
Reply to: