Can you do this testing again and as soon as you get a hanging job, check whether the usblp kernel module is attached to the printer or not.
To do so,when starting the (cancel jobs, power-cycle printer) run the command:
ls -l /dev/usb/lp*
This should give at least one line of output (make sure usblp is not blacklisted). You can see which line corresponds to your printer via
sudo usb_printerid /dev/usb/lp0 sudo usb_printerid /dev/usb/lp1 ...
Now print your jobs. You can observe that during data transfer of each job the line for your printer in
disappears and reappears after completion of the data transfer to the printer.
As soon as a job hangs, DO NOT cancel it and run the commands
ls -l /dev/usb/lp* ps auxwww | grep usb:
and post the output here. Does the line for your printer appear in the "ls -l /dev/usb/lp*" output?
Can you do this testing again and as soon as you get a hanging job, check whether the usblp kernel module is attached to the printer or not.
To do so,when starting the (cancel jobs, power-cycle printer) run the command:
ls -l /dev/usb/lp*
This should give at least one line of output (make sure usblp is not blacklisted). You can see which line corresponds to your printer via
sudo usb_printerid /dev/usb/lp0
sudo usb_printerid /dev/usb/lp1
...
Now print your jobs. You can observe that during data transfer of each job the line for your printer in
ls -l /dev/usb/lp*
disappears and reappears after completion of the data transfer to the printer.
As soon as a job hangs, DO NOT cancel it and run the commands
ls -l /dev/usb/lp*
ps auxwww | grep usb:
and post the output here. Does the line for your printer appear in the "ls -l /dev/usb/lp*" output?