Some additional information: I'm using a Canon PIXMA MP610 printer, attached via USB.
So looking through the diff between -1 and -2.3 the patch debian/patches/usb-backend-further-enhancements.patch might indeed by the culprit here. Reading through the patch header - Added the command line option "usb-no-reattach". With the option set the usblp kernel module does not get reattached after a job has been printed. Some printers cut off the end of the job or even crash by re-attaching the module. This is a development/debug mode to test whether re-attaching was the culprit of a problem. Users should report such issues so that their printers can get added to the quirk list. - USB backend: Do a printer reset after each job, this makes the Prolific USB -> Parallel adapter finally work (LP: #987485) and makes it unnecessary to blacklist the usblp kernel module for some printers (LP: #997040). I've tried "lp -d Canon_MP610_series -o usb-no-reattach=off test.pdf", but that didn't seem to help. I'm not sure though, if I have passed the usb-no-reattach option the right way. In the kernel I still got an entry like Oct 20 00:39:39 pluto kernel: [ 2641.104790] usb 1-1.1.3: reset high-speed USB device number 9 using ehci_hcd On a different note: I don't quite understand, by you modprobe the usblp module on upgrades, but not in the init script . If the module is needed, shouldn't you also load it when you reboot? If it's not needed, why the modprobe? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature