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

Bug#661866: marked as done (cups: CUPS states job successful. Only an error page prints, if anything.)



Your message dated Wed, 15 Mar 2017 15:37:49 +0000
with message-id <15032017153309.2bb00c69fde1@desktop.copernicus.org.uk>
and subject line Re: Bug#661866: cups: CUPS states job successful.  Only an error page prints, if anything.
has caused the Debian Bug report #661866,
regarding cups: CUPS states job successful.  Only an error page prints, if anything.
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.)


-- 
661866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661866
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cups
Version: 1.5.0-13
Severity: important

Dear Maintainer,

I first noticed this after a CUPS update, but have been too busy to deal with
it.  Basically, when I print now, only an error page is created (if I'm lucky)
with the following information on it:

ERROR:
invalidaccess (yes, no space here)
OFFENDING COMMAND:
length
STACK:

I can print to this printer (Brother HL-5250DN) from my other computer just
fine, so not a hardware issue.  It does not matter what application I'm
printing from:  any PDF program (okular, Adobe, whatever), LibreOffice, plain
text files in Kate or gedit.  Everything causes the error page listed above.  I
also get this for an output file when I print to the built-in PDF queue, so the
output location does not seem to matter which makes me think it is not a PPD
issue.

Most of the time, I don't even get the error page when I send it to my printer.
Usually, when I print, the printer wakes up, the activity light flashes once
and then stays on.  It will sit there like that until the cows come home.  If I
restart the CUPS service, sometimes that will jolt things and the error page
will print (though that is not the only way to get the error page, it will
print on its own at times).  Other times, I have to hit the cancel job button
on the printer to reset the activity light.

I have tried recreating the print queue, rebooting and reinstalling CUPS.
Nothing fixed it.  I've had issues in the past where the last page to print in
a job will hold in my printer for a long time and then finally print.  That is
not what is going on here.  It simply does not print.

Thank you for looking into this.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (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+b1
ii  cups-client            1.5.0-13
ii  cups-common            1.5.0-13
ii  cups-ppdc              1.5.0-13
ii  debconf [debconf-2.0]  1.5.41
ii  ghostscript            9.05~dfsg-2
ii  libavahi-client3       0.6.30-6
ii  libavahi-common3       0.6.30-6
ii  libc6                  2.13-26
ii  libcups2               1.5.0-13
ii  libcupscgi1            1.5.0-13
ii  libcupsdriver1         1.5.0-13
ii  libcupsimage2          1.5.0-13
ii  libcupsmime1           1.5.0-13
ii  libcupsppdc1           1.5.0-13
ii  libdbus-1-3            1.4.18-1
ii  libgcc1                1:4.6.2-12
ii  libgnutls26            2.12.16-1
ii  libgssapi-krb5-2       1.10+dfsg~beta1-2
ii  libijs-0.35            0.35-8
ii  libkrb5-3              1.10+dfsg~beta1-2
ii  liblcms1               1.19.dfsg-1+b1
ii  libldap-2.4-2          2.4.28-1.1
ii  libpam0g               1.1.3-7
ii  libpaper1              1.1.24+nmu1
ii  libpoppler13           0.16.7-3
ii  libslp1                1.2.1-9
ii  libstdc++6             4.6.2-12
ii  libusb-0.1-4           2:0.1.12-20
ii  lsb-base               3.2-28.1
ii  poppler-utils          0.16.7-3
ii  procps                 1:3.2.8-11
ii  ssl-cert               1.0.28
ii  ttf-freefont           20100919-1
ii  zlib1g                 1:1.2.6.dfsg-1

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.0-13
ii  cups-pdf     2.6.1-5
ii  foomatic-db  20120212-1
ii  hplip        <none>
ii  smbclient    2:3.6.3-1
ii  udev         175-3.1

-- debconf information:
  cupsys/raw-print: true
  cupsys/backend: ipp, lpd, parallel, serial, socket, usb, snmp, dnssd



--- End Message ---
--- Begin Message ---
On Thu 01 Mar 2012 at 20:18:07 -0700, Brett Ussher wrote:

> Package: cups
> Version: 1.5.0-13
> Severity: important
> 
> Dear Maintainer,
> 
> I first noticed this after a CUPS update, but have been too busy to deal with
> it.  Basically, when I print now, only an error page is created (if I'm lucky)
> with the following information on it:
> 
> ERROR:
> invalidaccess (yes, no space here)
> OFFENDING COMMAND:
> length
> STACK:
> 
> I can print to this printer (Brother HL-5250DN) from my other computer just
> fine, so not a hardware issue.  It does not matter what application I'm
> printing from:  any PDF program (okular, Adobe, whatever), LibreOffice, plain
> text files in Kate or gedit.  Everything causes the error page listed above.  I
> also get this for an output file when I print to the built-in PDF queue, so the
> output location does not seem to matter which makes me think it is not a PPD
> issue.
> 
> Most of the time, I don't even get the error page when I send it to my printer.
> Usually, when I print, the printer wakes up, the activity light flashes once
> and then stays on.  It will sit there like that until the cows come home.  If I
> restart the CUPS service, sometimes that will jolt things and the error page
> will print (though that is not the only way to get the error page, it will
> print on its own at times).  Other times, I have to hit the cancel job button
> on the printer to reset the activity light.
> 
> I have tried recreating the print queue, rebooting and reinstalling CUPS.
> Nothing fixed it.  I've had issues in the past where the last page to print in
> a job will hold in my printer for a long time and then finally print.  That is
> not what is going on here.  It simply does not print.
> 
> Thank you for looking into this.

This report was submitted against what is now an unsuppoerted version of
cups-filters. There did seem to be an amelioration of the issue at the
time and it is very probably not present in testing/unstable. Should
that not be the case, please submit a new report.

Thanks,

Brian.

--- End Message ---

Reply to: