[cups-devel] Seiko label printer missing part of text on left hand edge ACTUALLY last bit of print lost

[Helge Blischke]

> Am 30.05.2020 um 11:45 schrieb KKing <kicking177 at gmail.com>:
> 
> So I thought I had issue with the left hand edge of label (or as it comes out the final part) which I have now realised it is an issue I always had in that it is the last part of data sent to the printer that is missed/lost.
> 
> With LMDE2 CUPS v1.7.5 the labels printed with the left hand edge first and would lose the last part so I got round this by adding extra spaces and dots on one of the lines so it was that part of data that was lost and what I needed got printed.
> 
> But I do have a couple of issues with Debian 10 CUPS 2.2.10 for some reason being different to the LMDE2 v1.7.5.
> 
> The various PPD's I have for this printer that worked on LMDE2 (apart from final part data sent to printer) now have issues with Debian 10 CUPS 2.2.10.
> 1. The width and height dimensions appear to have been transposed, to get to work I have to swap the values in the PPD.
> 2. The last part of label data is printed first which means I lose the beginning of each line as it is the final print data sent to the printer.
> 3. LibreOffice Writer Print and Preview has issues with the orientation of label (I'm still fighting with that) but so far when I can get it to look right I encounter the issue that the left hand edge of label is the last bit sent to printer and I lose that 1-2mm worth of print.
> 
> Does that make sense?
> Any thoughts on why the orientation appears to have changed between the machines/versions of CUPS, is there a config setting outside of the PPD that affects this?
> And why the last part of print data appears to have been lost/missed?
> 

I think you should explain in more detail the CUPS configuration on both of your machines.
Moreover, you should turn debug lofting on (cupsctl —debug-logging), print a sample
label (on both machines) and (on both machines) extract the job specific log messages
from the /var/log/cus/error_log.

If you have difficults doing that, I can provide a Perl script which does just that
with the job ID as parameter.

Helge