The CUPS backend script doesn't specify any encryption options when it executes the
xpra print command, so documents will fail to print on a server using encryption.
@joshiggins: r10439 should fix that.
(I never hit this issue before because I use
tcp-encryption but no
encryption for my unix domain sockets...)
If this works for you, it should get tested as part of #913, so you can just close or re-assign to afarr.
It is fixed indeed, thanks.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/964