Ubuntu
splix package

  1. Bug #898385
  2. Comment #12

Comment 12 for bug 898385

Revision history for this message
SPud (pudlis) wrote : Re: Chromium is not able to print on Samsung SCX-3200

Job 1515 was created by "fake" printer and send to backend http. Job 1516 was received over http and sent to usb backend (as far I understand). If job 1515 was send directly to usb it would produces garbage. Going through http fixes the problem.
In my opinion http causes only, that job is first created and later sent in single not interrupted, complete stream to usb backend. In direct case job may be sent in several chunks (and not single single step), because filter "stack" pstops/rastertospl does not produce steady stream. Or pstops/rastertospl stack finishes job (closes output, sends EOF or so) and when it is received by usb backend it interrupts uploading job to the printer (even there are still some data to upload).
It is only my guessing, so does it make any sense?