Hi All:
No responses yet...hoping for some suggestions. Our guess is that because we are encrypting the home space with Encfs, the symlink used by the x2go spool to /tmp is broken (i.e., if we use all the same commands to set up an account without encrypting home space, we can print).
Suggestions? FYI not suggesting this is a bug per se, just looking for a way forward and figure others may come on to wanting something similar.
Are we on the right track, that it would seem likely that using Encfs (which moves the original data) would be the cause of the problem, including the broken link between the x2go spool and the area it points to in /tmp
Could we issue some sort of command inside of .bashrc that would establish the link correctly after log in? My recollection is there are a set of pre and post login commands opportunities....apologize, can't remember command structure or if this is still current....is there a link that describes? And I think the folder name holding the spool changes periodically...
Leave .x2go out of the encryption process in it's original location......not sure this would work
Other?
....Thanks!