<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html><head><meta http-equiv="content-type" content="text/html; charset=UTF-8"></head><body style="font-family:Arial;font-size:14px"><p>
some follow-up:<br><br>
Since a Windows-based client PC does not allow a lot of troubleshooting, I tested printing from a native Ubuntu 14.04LTS client running ThinLinc client version 4.3.0, on which CUPS is installed and configured for a local printer with URI (from "/etc/cups/printers.conf"):<br><br>
DeviceURI socket://10.50.0.4<br><br>
1) test printing to local printer from this client-PC running Ubuntu -> ok<br><br>
2) connect to the same TL-agent (v4.5), open same web-page, print it -> displays succesfull launch of the print job, but no print job is emitted from the TL-client to my local printer<br><br>
3) I check on the client-PC what happened inside its CUPS, and see the following log messages:<br><br>
$ cat /var/log/cups/page_log<br>
MFCJ6510DW rob 1 [30/Oct/2015:15:44:39 +0100] 1 1 - localhost [Thinlinc-technical] Thinlinc printing issue workaround - -<br>
$ cat /var/log/cups/access_log<br>
localhost - - [30/Oct/2015:15:44:39 +0100] "POST /printers/MFCJ6510DW HTTP/1.1" 200 354 Create-Job successful-ok<br>
localhost - - [30/Oct/2015:15:44:39 +0100] "POST /printers/MFCJ6510DW HTTP/1.1" 200 48895 Send-Document successful-ok<br><br>
OK, so where did this job go ?<br><br>
$ lpstat -t<br>
scheduler is running<br>
system default destination: MFCJ6510DW<br>
device for MFCJ6510DW: socket://10.50.0.4<br>
MFCJ6510DW accepting requests since vr 30 okt 2015 15:44:39 CET<br>
printer MFCJ6510DW is idle. enabled since vr 30 okt 2015 15:44:39 CET<br>
Waiting for printer to finish.<br><br>
"Waiting for printer to finish" ?? Check the spool directory:<br><br>
# ls -ltr /var/spool/cups<br>
totaal 56<br>
drwxrwx--T 2 root lp 4096 okt 7 12:53 tmp<br>
-rw-r----- 1 root lp 48632 okt 30 15:44 d00001-001<br>
-rw------- 1 root lp 831 okt 30 15:44 c00001<br><br>
Hmm... looks indeed like two job-files that are still pending :<br>
# file *<br>
c00001: data<br>
d00001-001: PDF document, version 1.5<br>
tmp: sticky, directory<br><br>
The PDF files will very likely be the job contents, so what's in this "c00001" file ?<br><br>
# od -c c00001 |more<br>
...<br>
0000100 a g e \0 005 n l - b e 002 E \0 \v p r<br>
0000120 i n t e r - u r i \0 ' i p p : /<br>
0000140 / l o c a l h o s t : 6 3 1 / p<br>
0000160 r i n t e r s / M F C J 6 5 1 0<br>
0000200 D W B \0 031 j o b - o r i g i n a<br>
...<br><br>
This looks like an invalid printer-URI "ipp://localhost:631/printers/MFCJ6510DWB" , in any case different from the "socket://10.50.0.4" which I configured in the files "/etc/cups/printers.conf"<br><br>
-> is this the reason why printing is not happening (not correct printer-URI) ?<br><br>
-> is this something that CUPS is doing ? Or is this printer-URI made up by the TL-client ?<br><br>
Rob<br><br><br><br>
Citeren Rob De Langhe <<a href="mailto:rob.de.langhe@twistfare.be">rob.de.langhe@twistfare.be</a>>:</p>
<blockquote style="border-left:2px solid blue;margin-left:2px;padding-left:12px;" type="cite">
<p>
hi TL-enthousiasts,<br><br>
I have the master and agent running TL-v4.5 now (the beta version); a Windows-client is version 4.4<br><br>
1) I can print normally from this Windows PC to my local printer, any type of file<br>
2) I have the Windows printer-queue open, to see what the printer is doing (if anything)<br>
3) I launch the TL-client, make sure that the local printer is exported to TL, then open a new session on the agent<br>
4) I see that the 'thinlocal' print queue is enabled:<br>
$ lpstat -t<br>
scheduler is running<br>
no system default destination<br>
device for thinlocal: thinlocal:/<br>
thinlocal accepting requests since vr 30 okt 2015 14:36:35 CET<br>
printer thinlocal is idle. enabled since vr 30 okt 2015 14:36:35 CET<br>
Sending job to queue thinlocal@127.0.0.1:4913<br><br>
5) I open some web-page, print it to a local PDF file; so far so good (the file exists, and is about 43KB size)<br><br>
6) when I transfer the file manually from the TL-directory to my Windows-PC, open the PDF file with Acrobat Reader, then I can print it normally to my local printer; so far so good<br>
7) however, when I print from within the TL-session to the 'thinlocal' printer, and keep an eye at the same time on the Windows-screen which shows the print-queue, I see a very short print-job appearing on the Windows-print-queue, then disappears again. And nothing gets sent to my printer.<br><br>
-> how to diagnose what gets sent to my Windows-TL-client ? Possible some empty job ?<br><br>
The log on the Windows-PC, "%TEMP%\tlclient.log" contains these lines with the confirmation that the job sending happens well :<br>
2015-10-30T14:48:00: New thinlocal printer job, receiving to: C:\Users\rob\AppData\Local\Temp\lpd18<br>
2015-10-30T14:48:00: Finished receiving printer job<br>
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".<br>
2015-10-30T14:48:00: Job printed successfully<br><br>
8) when I change my Windows default printer to a PDF-file printer, an retry again printing from the TL-session, then I can save the generated PDF file on the Windows-PC, and see correctly the web-page that I was trying to see on paper...<br><br>
-> I am lost, where to start diagnosing ?<br><br>
thanks in advance for any hints !<br>
Rob</p>
</blockquote>
<br><br></body></html>