Comment 27 for bug 898385

It still happens. It really rare with Splix. Using Splix does not solve the problem, but makes it less frequent.

I did small test. I've created my own backend (bash script), which redirects stdin to some file, and when it is finished sends file to /dev/usb/lp0. It is working well even with Samsung driver. When my script redirects directly to stdout, it produces problem.

So: the same content, but sent in single not interrupted stream makes difference. It may suggest that it is some timing issue, which should be addressed in usbbackend and not in Splix or Samsung driver.

I think that interrupt in input stream is interpreted by Samsung printer as end of job. If uploaded data is not complete, printer tries to print as plain text, and does not wait for rest of job.

I'd like to try cups' filter ability in order to implement buffering, but it is out of my knowledge. If you may suggest something I'm open to try your suggestions.