Found this weird behavior when testing printing multiple copies to thinlocal. When printing, say, more than 30 copies to thinlocal the client will not print that amount on the local printer. I tested with 4.12.1 client on Fedora 34 and server 4.12.1 on RHEL 8 and got the following result: | Printed on server | Printed on local printer | |-------------------+--------------------------| | 1 | 1 | | 15 | 15 | | 31 | 31 | | 32 | 0 | | 33 | 0 | | 34 | 0 | | 35 | 1 | | 36 | 2 | | 37 | 3 | As you can see something happens when printing more than 31 copies. I checked this by having a dummy printer on the client machine and then checked the logs. In tlclient.log: > Printing job with title "ThinLinc print job" and type "application/pdf" (3 copies) on queue "thinlocal". And in cups log on the client: > Jun 28 14:19:56 fedora cupsd[1269]: [Job 25] argv[2]="cendio" > Jun 28 14:19:56 fedora cupsd[1269]: [Job 25] argv[3]="ThinLinc print job" > Jun 28 14:19:56 fedora cupsd[1269]: [Job 25] argv[4]="3" Where 'argv[4]' is the number of copies. I'm pretty sure that it is not an error on the server side since I checked the cups log on the server and there thinlocal backend gets the correct number of copies. Tips for testing: * Easy printing with: > echo 'hello' | lpr -P thinlocal -# 37 * Create fake printer use Cups-PDF or: > lpadmin -p my_test_printer -E -v file:///dev/null
When I found this I tested with a 4.12.1 server on Fedora 34 and client 4.12.1 build 2093 on Fedora 32 (my workstation). Then I got another 'breaking' number: | Printed on server | Printed on local printer | |-------------------+--------------------------| | 66 | 66 | | 67 | 67 | | 68 | 0 | | 69 | 0 | | 70 | 0 | | 71 | 1 | | 72 | 2 |
