[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after "hp" CUPS backend failed
Is this related in any way to bug 1521134?
1521134 is marked fixed in 3.17.4 so I will test and see.
--
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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after "hp" CUPS backend failed
Still present in ubuntu 16.04. Workaround above is not possible in
ubuntu. Please fix the issue.
--
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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after "hp" CUPS backend failed
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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after hp CUPS backend failed
This is still a problem on Mint 17 and Ubuntu 14.04 with version 3.15.4 of hplip on the M225dn printer. -- 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after hp CUPS backend failed
akbar, what did you exactly do in System-Administration-Printing? Which blog do you mean? -- 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after hp CUPS backend failed
I have gone through System-Administration-Printing, and solved it. and rely appreciate and adore for your help in this blog. tonertree.com -- 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after hp CUPS backend failed
This bug is still around as of today :( -- 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after hp CUPS backend failed
** Changed in: hplip Assignee: (unassigned) = Sarbeswar Meher (sarbeswar-meher) -- 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after hp CUPS backend failed
Hi Till and Milan, Around Lucid time, the hp backend would indeed respond to a paper or toner outage, or trying to print to a powered-off printer, by pausing the queue. I applied beh to my queues as a workaround. Those cases have been fixed at least since Precise, but I think the behaviour is still different from other backends in certain situations. For example, if the network connection to the printer is interrupted while printing with the hp backend under Trusty, I see this in syslog: Apr 29 21:24:32 ubuntu hp[4085]: io/hpmud/jd.c 582: timeout write_channel hp:/net/HP_LaserJet_P2055dn?ip=10.0.254.34 Apr 29 21:24:37 ubuntu hp[4085]: io/hpmud/jd.c 94: unable to read device-id Apr 29 21:24:37 ubuntu hp[4085]: prnt/backend/hp.c 625: ERROR: 5012 device communication error! and this in cups' error_log: D [29/Apr/2014:21:24:37 +] [Job 1] prnt/backend/hp.c 625: ERROR: 5012 device communication error! D [29/Apr/2014:21:24:38 +] [Job 1] PID 4085 (/usr/lib/cups/backend/hp) stopped with status 4. D [29/Apr/2014:21:24:38 +] [Job 1] Wrote 1 pages... D [29/Apr/2014:21:24:38 +] [Job 1] PID 4087 (pstops) exited with no errors. D [29/Apr/2014:21:24:38 +] [Job 1] PID 4084 (/usr/lib/cups/filter/pdftops) exited with no errors. I [29/Apr/2014:21:24:38 +] [Job 1] Backend returned status 4 (stop printer) I [29/Apr/2014:21:24:38 +] [Job 1] Printer stopped due to backend errors; please consult the error_log file for details. Under the same conditions with the socket backend, the job fails but the backend is not paused: D [29/Apr/2014:21:29:40 +] [Job 2] Error reading back-channel data: Connection reset by peer E [29/Apr/2014:21:29:40 +] [Job 2] Unable to write print data: Broken pipe D [29/Apr/2014:21:29:40 +] [Job 2] Set job-printer-state-message to Unable to write print data: Broken pipe, current level=ERROR I [29/Apr/2014:21:29:40 +] [Job 2] Waiting for printer to finish. D [29/Apr/2014:21:29:40 +] [Job 2] ATTR: marker-levels=94 D [29/Apr/2014:21:29:40 +] [Job 2] new_supply_state=0, change_state=0 D [29/Apr/2014:21:29:40 +] [Job 2] new_state=0, change_state=0 D [29/Apr/2014:21:29:40 +] [Job 2] PID 4145 (/usr/lib/cups/backend/socket) exited with no errors. D [29/Apr/2014:21:29:40 +] [Job 2] Wrote 1 pages... D [29/Apr/2014:21:29:40 +] [Job 2] PID 4147 (pstops) exited with no errors. D [29/Apr/2014:21:29:40 +] [Job 2] PID 4146 (gs) exited with no errors. D [29/Apr/2014:21:29:40 +] [Job 2] PID 4144 (/usr/lib/cups/filter/pdftops) exited with no errors. D [29/Apr/2014:21:29:40 +] [Job 2] time-at-completed=1398806980 I [29/Apr/2014:21:29:40 +] [Job 2] Job completed. An example where this happened recently was a particular print job that triggered a firmware error (49 error), causing the printer to lock up and stop responding until power cycled. I don't know whether to consider this a bug in the hp backend or a difference of opinion. For my users I've kept beh on the queues because it's best if they can reset the printer and carry on, and not have to contact an lpadmin to resume the queue. -- 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: Incomplete 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after hp CUPS backend failed
Can someone of the HPLIP developers at HP have a look into the issue described by Ryan Tandy in comment #12? Thanks. -- 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: Incomplete 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692568] Re: Printer shouldn't be paused after hp CUPS backend failed
** Changed in: hplip Status: Incomplete = Confirmed -- 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
