[Thinlinc-technical] TL v4.5 : failure printing from Ubuntu-agent (was: Windows-client)

Rob De Langhe rob.de.langhe at twistfare.be
Sat Nov 7 16:20:56 CET 2015

  hi Pierre,

thanks for your feedback, much appreciated !

Meanwhile the title of this mail-thread should be changed from 'failure
printing from Windows-client' into 'failure printing from Ubuntu agent'.

I searched a bit further on this issue, and got to the bug you filed in
Oct-2014 with CUPS : https://www.cups.org/str.php?L4494
That bug has now status Resolved, listing version 1.7.4 of CUPS in which
that should have happened. But its status also mentioned that it is "Fixed
In: Third-party".

The bug description refers to another bug filed at Redhat, bug

In this bug, it is not so clear to me whether there is finally some patch,
the only 'workaround' I see more or less described as succesfull, is
setting the printer driver on the client side (I assume that, in the
context of ThinLinc, that is the agent because there the print job is
initiated) to "raw" so that the client side is not doing any job-content

I did so, with (on the agent) "lpadmin -p thinlocal -m raw".
This changed the CUPS config file "/etc/cups/printers.conf" so that the
MakeModel Generic postscript printer
disappeared, and the line
Type 4180
changed into
Type 4

Stopped and restarted CUPS on the agent, then attempting again to print a
simple web page. The job is accepted by CUPS on the agent, but is not
handed over to CUPS on the master: the two corresponding files remain on
the agent in directory "/var/spool/cups", and the job content is still PDF
(this seemed to be the reason that the master is refusing that print

-> puzzled as to whom to contact to get this resolved ... As least I wanted
to share my findings (or lack of...) with anyone here who's investigating
the same issues on Ubuntu.


Quoting Pierre Ossman <ossman at cendio.se>:

> On Fri, 30 Oct 2015 15:04:58 +0100
> Rob De Langhe <rob.de.langhe at twistfare.be> wrote:
>> 2015-10-30T14:48:00: Printing job with title "[Thinlinc-technical]
>> Thinlinc printing issue workaround" and type
>> "application/octet-stream" (1 copies) on queue "thinlocal".
> The type "application/octet-stream" means that this got sent as a raw
> job. That means the data will be sent directly to the printer and
> should already be in a format that the printer understands. This is
> rarely the case unless you've done something special on your ThinLinc
> server.
> More likely is that you are running Ubuntu and you're getting issues
> from their broken CUPS. We have a note about that problem in our
> platform specific notes:
> https://www.cendio.com/thinlinc/docs/platforms/ubuntu
> We cannot do much about this so I suggest you also put pressure on
> Ubuntu to fix this.
> Rgds
> --
> Pierre Ossman           Software Development
> Cendio AB                https://cendio.com
> Teknikringen 8                https://twitter.com/ThinLinc
> 583 30 Linköping        https://facebook.com/ThinLinc
> Phone: +46-13-214600        https://plus.google.com/+CendioThinLinc
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> _______________________________________________
> Thinlinc-technical mailing list
> Thinlinc-technical at lists.cendio.se
> Manage your
> subscription:http://lists.cendio.se/mailman/listinfo/thinlinc-technical
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cendio.se/pipermail/thinlinc-technical/attachments/20151107/c290b304/attachment-0003.html>

More information about the Thinlinc-technical mailing list