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

Bug#860591: marked as done (cups-daemon: Job enters queue, then stops and can't be removed)

Your message dated Thu, 14 Dec 2017 20:30:56 +0000
with message-id <13122017204653.55493660cebe@desktop.copernicus.org.uk>
and subject line Re: Bug#860591: cups-daemon: Job enters queue, then stops and can't be removed
has caused the Debian Bug report #860591,
regarding cups-daemon: Job enters queue, then stops and can't be removed
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.)


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

When attempting to print via CUPS, the job will successfully enter the
queue (the status “Processing” is shown). Then, the job is shown as
“Stopped”; the queue does not progress.

When I then attempt to remove that job – or any job – it simply fails.
The print queue is currently unusable, and its jobs remain there,
stopped.

I am using GNOME 3's printer management.


-- System Information:
Debian Release: 9.0
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups-daemon depends on:
ii  adduser              3.115
ii  bc                   1.06.95-9+b3
ii  dpkg                 1.18.23
ii  init-system-helpers  1.47
ii  libavahi-client3     0.6.32-2
ii  libavahi-common3     0.6.32-2
ii  libc6                2.24-9
ii  libcups2             2.2.2-2
ii  libcupsmime1         2.2.2-2
ii  libdbus-1-3          1.10.18-1
ii  libgssapi-krb5-2     1.15-1
ii  libpam0g             1.1.8-3.5
ii  libpaper1            1.1.24+nmu5
ii  libsystemd0          232-22
ii  lsb-base             9.20161125
ii  procps               2:3.3.12-3
ii  ssl-cert             1.0.38

Versions of packages cups-daemon recommends:
ii  avahi-daemon  0.6.32-2
ii  colord        1.3.3-2
ii  cups-browsed  1.13.4-1

Versions of packages cups-daemon suggests:
ii  cups                                       2.2.2-2
ii  cups-bsd                                   2.2.2-2
ii  cups-client                                2.2.2-2
ii  cups-common                                2.2.2-2
ii  cups-filters [foomatic-filters]            1.13.4-1
ii  cups-ppdc                                  2.2.1-8
ii  cups-server-common                         2.2.2-2
ii  foomatic-db-compressed-ppds [foomatic-db]  20161201-1
ii  ghostscript                                9.20~dfsg-3
ii  hplip                                      3.16.11+repack0-2
ii  poppler-utils                              0.48.0-2
ii  printer-driver-cups-pdf [cups-pdf]         2.6.1-22
ii  printer-driver-gutenprint                  5.2.11-1+b2
ii  printer-driver-hpcups                      3.16.11+repack0-2
pn  smbclient                                  <none>
ii  udev                                       232-22

-- no debconf information

-- 
 \        “We have to go forth and crush every world view that doesn't |
  `\                believe in tolerance and free speech.” —David Brin |
_o__)                                                                  |
Ben Finney <bignose@debian.org>

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On Sat 29 Apr 2017 at 13:09:05 +0100, Brian Potkin wrote:

> On Fri 21 Apr 2017 at 22:15:08 +1000, Ben Finney wrote:
> 
> > That leaves the problem of failing to print to the HP printer
> > connected via 802.11, which would not be affected by the USB hub. I
> > will try again later to diagnose that one.
> 
> Any news on this?

I think it not unreasonable to see the subject of the initial report
as having been dealt with satisfactorily. The USB issue has been solved
and. after this length of time, one might expect the wireless isuue to
have had a resolution. If not, a new report, could be submitted.

Regards,

Brian.

--- End Message ---
Reply to: