desktop-packages team mailing list archive

[Nick G <692568@xxxxxxxxxxxxxxxxxx>]

This issue occurred on a Debian Jessie system today with the following
series of errors in the CUPS log while attempting to send print jobs:

E [20/Nov/2015:10:22:41 -0800] [Job 1828] Unable to send data to printer.
E [20/Nov/2015:10:27:46 -0800] [Job 1828] Stopping unresponsive job.
E [20/Nov/2015:10:47:07 -0800] Missing printer-uri, job-uri, or ppd-name attribute
E [20/Nov/2015:10:47:07 -0800] [Client 17] Returning IPP client-error-bad-request for windows-ext (no URI) from 10.0.1.15
E [20/Nov/2015:10:50:07 -0800] Unable to communicate with avahi-daemon: An unexpected D-Bus error occured
W [20/Nov/2015:11:16:25 -0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP_LaserJet_1200-Gray..' already exists

To Till Kamppeter above: for me the error was resolved by going to
Administration -> Manage Printers -> HP_LaserJet_1200 -> In the dropdown
that has "Maintenance" selected by default, select "Resume Printer".

A UI problem is that "Resume Printer" should be a button, not an entry
in a menu that otherwise changes screens.  Bigger UI problem of course
is lack of any indication that a printer is paused outside the "Resume"
option appearing hidden in a drop-down menu.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/692568

Title:
  Printer shouldn't be paused after "hp" CUPS backend failed

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  When printing fails for some reason ("backend failed" message),
  printer is paused, and won't resume automatically, even after a
  reboot. This is silly because there's no notice about that in the
  print dialog nor in the print queue: you have to go to
  System->Administration->Printing, and be very clever to understand how
  to re-enable the printer.

  In most cases, the fact that something failed doesn't mean other
  documents won't print, and generally users will figure the error
  better by themselves than with a paused printer.

  This is in Lucid, cups 1.4.3-1ubuntu1.3 (not sure it's the same
  behavior in Maverick).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/692568/+subscriptions