Your message dated Sat, 11 Jul 2015 13:45:02 +0100
with message-id <[email protected]>
and subject line Re: Bug#661992: cups: Invoking of GS fails or printing fails
shortly after this
has caused the Debian Bug report #661992,
regarding cups: Invoking of GS fails or printing fails shortly after this
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 [email protected]
immediately.)
--
661992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661992
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cups
Version: 1.5.2-5
Severity: normal
Dear Maintainer,
the list of open bugs is quite bug, I tried to find my issue but
didn't see it in the end. I have a Samsung ML-1630 printer, i use
it with the splix packages of debian. When I am printing German
DHL labels (dhl.de) with their Java applet, sometimes I don't get
anything printed (and the label can only be printed once/asked to
be reset five times). When printing I see gs starting up but quitting
quite early, the log files don't include anything about it (my main
concern here).
Logs:
==> cups/access_log <==
localhost - - [03/Mar/2012:11:21:48 +0100] "POST /printers/ML-1630-Series
HTTP/1.1" 200 369 Create-Job successful-ok
localhost - - [03/Mar/2012:11:21:48 +0100] "POST /printers/ML-1630-Series
HTTP/1.1" 200 1302862 Send-Document successful-ok
==> cups/page_log <==
ML-1630-Series ich 608 [03/Mar/2012:11:21:53 +0100] 1 1 - localhost
DHL-Marke-1-HRM9KRRHYB - -
nothing is written to cups/error_log
Question:
How can I see the invocation of gs? Is somebody logging the exit status?
How can I figure out if the issue is with cups? the PS->PDF where gs is
used for? the Splix? backend?
holger
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cups depends on:
ii adduser 3.113+nmu1
ii bc 1.06.95-2
ii cups-client 1.5.2-5
ii cups-common 1.5.2-5
ii cups-filters 1.0.2-1
ii cups-ppdc 1.5.2-5
ii debconf [debconf-2.0] 1.5.41
ii dpkg 1.16.1.2
ii ghostscript 9.05~dfsg-2
ii libavahi-client3 0.6.30-6
ii libavahi-common3 0.6.30-6
ii libc6 2.13-27
ii libcups2 1.5.2-5
ii libcupscgi1 1.5.2-5
ii libcupsimage2 1.5.2-5
ii libcupsmime1 1.5.2-5
ii libcupsppdc1 1.5.2-5
ii libdbus-1-3 1.4.18-1
ii libgcc1 1:4.6.2-16
ii libgnutls26 2.12.16-1
ii libgssapi-krb5-2 1.10+dfsg~beta1-2
ii libkrb5-3 1.10+dfsg~beta1-2
ii libldap-2.4-2 2.4.28-1.1
ii libpam0g 1.1.3-7
ii libpaper1 1.1.24+nmu1
ii libslp1 1.2.1-9
ii libstdc++6 4.6.2-16
ii libusb-1.0-0 2:1.0.9~rc3-3
ii lsb-base 3.2-28.1
ii poppler-utils 0.16.7-3
ii procps 1:3.3.2-3
ii ssl-cert 1.0.28
Versions of packages cups recommends:
ii avahi-daemon 0.6.30-6
ii colord 0.1.16-2
ii cups-driver-gutenprint 5.2.7-5
ii foomatic-filters 4.0.12-1
ii ghostscript-cups 9.05~dfsg-2
ii printer-driver-gutenprint [cups-driver-gutenprint] 5.2.7-5
Versions of packages cups suggests:
ii cups-bsd 1.5.2-5
ii cups-pdf <none>
ii foomatic-db-compressed-ppds [foomatic-db] 20120212-1
ii hplip 3.12.2-1
ii smbclient 2:3.6.3-1
ii udev 175-3.1
-- debconf information:
cupsys/raw-print: true
cupsys/backend: ipp, lpd, socket, usb, snmp, dnssd
--- End Message ---
--- Begin Message ---
Dear Debian User,
Further information on your issue was requested some time ago but there
has been no response from you. Use of our limited, volunteer supported
resources is best served by not keeping open inactive bugs any longer
than desirable, especially when the package concerned is older than the
current stable Debian version. Consequently, the report is now being
closed.
You may, of course, wish to review the reported problem. It would be
appreciated if any future investigation could be conducted using the
testing or unstable distributions. If considered necessary, this report
could be re-opened or a new bug report, possibly referencing this one,
submitted.
Thank you for your report.
Regards,
Brian.
--- End Message ---
