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

Bug#908871: marked as done (cups: completed jobs stay in queue)

Your message dated Sun, 16 Sep 2018 17:06:24 +0200
with message-id <2195442.mNPQFjG6mq@odyx.org>
and subject line Re: Bug#908871: cups: completed jobs stay in queue
has caused the Debian Bug report #908871,
regarding cups: completed jobs stay in queue
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.)


-- 
908871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908871
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cups
Version: 2.2.8-5
Severity: normal

Dear Maintainer,

Wondering why my printer didn't seem to want to print anymore, I
noticed that completed print jobs stay in the queue, preventing any
subsequent jobs from printing (unless I lprm the completed job).

Tried with lpr, lp and printing from chromium.  Same results.

Since I don't print very often, I don't know exactly when this change
occurred, but everything was working fine about a month ago AFAIK.

Printer: HP LaserJet p2015n Series, hpcups 3.17.1 (via JetDirect).

Happy to help debug this if you let me know what I can try.

Thanks.

- Felix

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

Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups depends on:
ii  cups-client            2.2.8-5
ii  cups-common            2.2.8-5
ii  cups-core-drivers      2.2.8-5
ii  cups-daemon            2.2.8-5
ii  cups-filters           1.21.2-1
ii  cups-ppdc              2.2.8-5
ii  cups-server-common     2.2.8-5
ii  debconf [debconf-2.0]  1.5.69
ii  ghostscript            9.22~dfsg-3
ii  libavahi-client3       0.7-4
ii  libavahi-common3       0.7-4
ii  libc-bin               2.27-6
ii  libc6                  2.27-6
ii  libcups2               2.2.8-5
ii  libcupscgi1            2.2.8-5
ii  libcupsimage2          2.2.8-5
ii  libcupsmime1           2.2.8-5
ii  libcupsppdc1           2.2.8-5
ii  libgcc1                1:8.2.0-6
ii  libstdc++6             8.2.0-6
ii  libusb-1.0-0           2:1.0.22-2
ii  poppler-utils          0.63.0-2
ii  procps                 2:3.3.15-2

Versions of packages cups recommends:
ii  avahi-daemon                     0.7-4
ii  colord                           1.4.3-3
ii  cups-filters [ghostscript-cups]  1.21.2-1
ii  printer-driver-gutenprint        5.2.13-2+b1

Versions of packages cups suggests:
ii  cups-bsd                                   2.2.8-5
pn  cups-pdf                                   <none>
ii  foomatic-db-compressed-ppds [foomatic-db]  20180604-1
ii  hplip                                      3.17.10+repack0-5
ii  printer-driver-hpcups                      3.17.10+repack0-5
ii  smbclient                                  2:4.8.5+dfsg-1
ii  udev                                       239-9

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
Le dimanche, 16 septembre 2018, 15.30:34 h CEST Felix C. Stegerman a écrit :
> * Brian Potkin <claremont102@gmail.com> [2018-09-16 13:50]:
> > My quick tests show gstoraster is failing. There is a new ghostscript
> > package now in unstable. Upgrade. How do you go on?
> 
> That does indeed seem to fix the problem.  Thanks!

Closing then, thanks!

-- 
    OdyX

--- End Message ---
Reply to: