desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #107608
[Bug 692568] Re: Printer shouldn't be paused after "hp" CUPS backend failed
We're still experiencing the same bug on multiple computers running 10.04 with HPLIP versions from 3.13.10 up to 3.14.10. Affected printers have been: M1536dnf, HP M125nw and the M1212nf.
The only workaround I've found so far that's susceptible for our end users who don't have admin rights is to run "cupsenable $PRINTERNAME" every few minutes via crontab. A real solution would be very useful.
(beh does not help us as we need the scanning capability of the hplip drivers).
I can provide more information if required.
--
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 HP Linux Imaging and Printing:
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