This bug is *not* about the backend failure I'm getting. It's merely
about the fact that a backend failure makes the printer go to pause
instead of just aborting the current task. So the precise error that
happens in my case doesn't matter, and it actually happened while I was
away (users hadn't understood why the printer had suddenly stopped
working).
** Changed in: cups (Ubuntu)
Status: Incomplete => New
** Description changed:
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 1.4.3-1ubuntu1.3 (not sure in Maverick).
+ This is in Lucid, cups 1.4.3-1ubuntu1.3 (not sure it's the same behavior
+ in Maverick).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692568
Title:
Printer shouldn't be paused after backend failed
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
