-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Printing impossible after disconnect at wrong time #72
Comments
I set the IPP-USB logs to debug to get some more information here:
|
Hi @Xerxekyran! First of all, seems your If upgrade will not help, could you please play a bit with |
Hi @alexpevzner thank you for your quick answer. I am currently playing around with different settings for init-delay, init-reset, disable-fax and http-connection in the default.conf but could not yet find a setting where this problem is solved. |
I checked my build scripts and there it states that I use version 0.9.23 already. What made you think I am using an older version? |
Even when using relatively high values it seems not to recover from the "failure state of the printer":
I tried hard, soft and none init-reset, high and low values for the delay and with or without the fax feature. Is there anything else I can test? |
Absence of the |
Do you know the model name of this Brother? |
BTW, #66 looks similar. Does tweaking |
BTW, my colleague suggested a reasonable idea. Have you tried to replace an USB cable? |
Brother HL-L2370DW
This problem was reported to me from a person at a different location, so there was a different cable in use. Further testing showed me that even printing directly to the printer via USB does not work (shutting IPP-USB off) as long as it is in this failure state. I needed to restart the printer completely by powering it off to recover it. After that everything works fine again. |
Setting this to 2 or 1 does not "heal" the problematic state. I will check if it prevents getting to the state as soon as I can get my hands on the printer again in a couple of days. I appreciate your help, thank you. |
So I got access to a very similar printer that a mentioned above: Brother-HL-L2370DN-series When I do the same setup:
I see some kind of an endless loop in the IPP-USB printer log. Maybe in this scenario it is a CUPS issue? If I add another print job, this new one is not printed, as the first one where the cable was removed inbetween never finishes. As soon as I remove that "failed" print job, the next print job gets printed without any problem.
Restarting the printer had the same result as deleting the stuck printing job. The next print job in the queue gets properly printed. |
Hi @Xerxekyran,
'ipp-usb However, it may be hard for CUPS guys to deal with this problem at their side (and there are not too much guys, after all). I'll try to find one of devices you've mentioned locally and if I will succeed, it will be best of all. Otherwise, we will try to debug remotely, by e-mail :) |
I found this issue because I have a Brother HL-L2350DW and ipp-usb would show
I set
because of @alexpevzner 's suggestion and that worked and the connection now seems stable. I can browse port 60000 without every other request causing the zero-size read. |
Hi there,
I am facing an issue where printing is not possible anymore until I restart the printer. When I try to print something and disconnect the USB-connection during this process (when I see the "! USB[1]: zero-size read" log entries in the IPP-USB printer log) then sometimes the printer initialization of IPP-USB gets stuck in an endless initilization loop. Re-connecting the printer or even restarting IPP-USB does not help. Only shutting down the printer and starting it up again. I know that this is not just a problem of this one printer (HP OfficeJet 200 Mobile Series), but also for example a Brother printer acted like this.
Is there a way of getting more information about what the actual problem is? Here are my logs for this situation:
Thank you for any help on this topic.
Regards
Lars
The text was updated successfully, but these errors were encountered: