Sorry, I don't have these printers offhand, and anyway the bug is not easy to reproduce. I think it would be simpler to look at the code and see what error codes lead to suspending the printer. IMHO, there are almost no reasons to stop the printer: if an error occurs, kill the current job, or maybe all jobs waiting in the queue, but don't prevent new tasks from being printed unless you're absolutely sure that will result in serious damage/waste.
There's also an issue that in corporate environments, it's probably OK to suspend printers to avoid people sending jobs that won't work and will waste paper, while in home desktops, people would prefer to be allowed to print, and check the result. This could probably be fixed in the GUI by showing a "Printer is suspended due to failure" notification, with a simple way to resume it if the user has admin rights. -- 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 "hp" CUPS backend failed To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/692568/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
