[X2Go-User] Client Printing not working!

[Chris Hemsing]

Solved!
It's a problem on the server side.
cups uses a private /tmp area. Spool directory uses /tmp, which is not the same 
as cups is.
Workaround under debian jessie:
Change in
/etc/systemd/system/printer.target.wants/cups.service

from
PrivateTmp=true
to
PrivateTmp=false

Chris

On 05/07/16 08:03, Chris Hemsing wrote:
> Hi to All,
>
> this is the setup
>
> x2goserver: debian jessie 4.0.1.19-0x2go2+git20160621.106
> mate session
> cups-x2go x2goserver-printing are both installed!
>
> The client can be debian or windows 7, both the same problem!
>
> While printing within the session to the cups-x2go printer the debugging info 
> of the x2goserver says:
>
> Jul  4 18:01:37 DC3 /usr/bin/x2goprint[6544]: x2goprint has been called with 
> options: hemsing hemsing-50-1467648002_stDMATE_dp32 
> hemsing-50-1467648002_stDMATE_dp32_7-hemsing-cupsjob6499Cu8FC4qpYbUTjMuT.pdf 
> hemsing-50-1467648002_stDMATE_dp32_7-hemsing-cupsjob6499Cu8FC4qpYbUTjMuT.pdf.title 
>
> Jul  4 18:01:37 DC3 /usr/bin/x2goprint[6544]: x2goprint is processing 
> /var/spool/x2goprint/hemsing-50-1467648002_stDMATE_dp32_7-hemsing-cupsjob6499Cu8FC4qpYbUTjMuT.pdf 
> with print job title ,,Test Page''
> Jul  4 18:01:37 DC3 /usr/bin/x2golistmounts[6566]: db_getmounts called, 
> session ID: hemsing-50-1467648002_stDMATE_dp32; return value: 
> 127.0.0.1|/tmp/.x2go-hemsing/spool/C-hemsing-50-1467648002_stDMATE_dp32|
> Jul  4 18:01:37 DC3 /usr/bin/x2goprint[6544]: client-side spool dir is 
> mounted, transferring printable file 
> hemsing-50-1467648002_stDMATE_dp32_7-hemsing-cupsjob6499Cu8FC4qpYbUTjMuT.pdf 
> to X2Go client system
> Jul  4 18:01:37 DC3 /usr/bin/x2goprint[6544]: x2goprint moved file 
> hemsing-50-1467648002_stDMATE_dp32_7-hemsing-cupsjob6499Cu8FC4qpYbUTjMuT.pdf 
> to X2Go client's spool dir
> Jul  4 18:01:37 DC3 /usr/bin/x2goprint[6544]: x2goprint moved file 
> hemsing-50-1467648002_stDMATE_dp32_7-hemsing-cupsjob6499Cu8FC4qpYbUTjMuT.pdf.ready 
> to X2Go client's spool dir, X2Go client should start the print dialog very soon
>
> So the print file has been sent to the client's spool directory. I rechecked 
> that by manually copying a pdf file on the server side to the mounted spool 
> directory and indeed it shows up on the clients spool directory.
> Thus, that mechanism works!
>
> However, no client side dialogue appears.
> Running the x2goclient with --debug does indeed give verbose logging, BUT 
> nothing during the time of submitting the print job!
>
> What is wrong? My setup? I can't find anything... Bug? What is the mechanism 
> to trigger the client's printing dialog??
> It does not seem to get triggered. Also, there is no file left over in the 
> client's spool directory.
>
> Cheers
> Chris
>
> _______________________________________________
> x2go-user mailing list
> x2go-user at lists.x2go.org
> http://lists.x2go.org/listinfo/x2go-user