El 14/08/2011 02:13 p.m., Mike Gabriel escribió:
Hi Ted,
On Mo 08 Aug 2011 18:04:18 CEST Ted Barnes wrote:
We are experimenting with X2go (very cool), but having a devil of a time getting printing to work. This request for help is keying off of posts by John Sullivan and Mario Oroz (thanks so much for those, guys, e.g., see tread http://www.mail-archive.com/x2go-user@lists.berlios.de/msg00104.html and http://www.mail-archive.com/x2go-user@lists.berlios.de/msg00115.html). We are having pretty much the same problem as described there. We are assuming that X2go printing in general can be made "to work" and that this is a matter of something we are doing wrong (maybe starting with the install?), some necessary "tweaks", etc.
To make sure you use latest software, please use these sources for installation of the server-side of X2go:
Debian+Ubuntu: http://wiki.x2go.org/nightly-built_packages_debian_ubuntu
Furtheron for initial debugging, please use x2goclient on Debian or Ubuntu to eradicate some not-so-generic Windows problems.
Please install the x2goclient from our nightly builds as well.
Nightly builds are for debugging+testing, not for production setups, though!
Q: In testing (where we simulate what we imagine the printing process to be by doing each step manually) when we issue the .ready command, why does that only seems to work sometimes as judged by the x2go print client popping on the XP side? Does that tell us something?
Good question. If the latest code does not solve your issues, please send the .ready file's content.
Q: Should printing be putting jobs in "/" (is that normal)? Does
NO! You use old server-side packages. Upgrade to the nighly builds.
the x2goprint script know what to grab based on job#s? We assume this all should work with multiple users and the x2goscript identifies which jobs to grab and put them individual user spool queues.
Yes, this does work with latest code.
Q: To work, should x2goprinting pass the print file from the server through the ssh connection to the client? Is this in part an "ssh passing the file" problem? We can connect through putty from the client to the server, and assume we have the keys correct because we can connect from XP to the Ubuntu server via x2go in the first place. Back to the lack of an id_dsa file? Again, we're not sure that printing is invoking the right scripts to begin with.
The print job files are stored on the client via SSHFS. The SSHFS file sharing uses a temporary pub/priv key pair, so for this mechanism it is not relevant if you can SSH to and from the server. The SSHFS mount is issued by the server and connects to the client (via a SSH tunnel).
Q: Assuming we get this working, we also assume that on the Ghostview/Ghostscript side we shouldn't be having to put the name of the file in the command line, nor actually having to use the command line. I.e., there is an option there to print that refers to whatever default printer we have set on the XP machine, but currently nothing happens if we use that particular option instead of the command line.
Yes, this should be so. Please test this with a Linux x2goclient first. If this works then check with the Windows x2goclient and report experienced differences.
Hello Ted You see/read that: https://lists.berlios.de/pipermail/x2go-user/2011-August/000335.html
regards. Mario.