On Wed, 2011-08-03 at 17:11 -0300, Mario OROZ wrote:
El 02/08/2011 11:47 p.m., John A. Sullivan III escribió:
El 02/08/2011 03:20 p.m., John A. Sullivan III escribió:
On Tue, 2011-08-02 at 15:12 -0300, Mario OROZ wrote:
El 02/08/2011 02:37 p.m., John A. Sullivan III escribi:
On Mon, 2011-08-01 at 16:49 -0300, Mario OROZ wrote: > Hello, I'm new to the list. > I use a server x2go on a Debian 6.0 with Windows XP clients. > I do not understand how to set the printing to print on printers on the client side. > I installed cups-x2go, and created a printer with cups cups-driver that provides > x2go. > I installed cups-x2go, and created a printer using the driver that provides > cups-x2go. > On the client windows, menu Option / Settings / Printing tab is checked the > "Show this dialog Before start printing" > > Can anyone tell me of some howto or explain how to configure the local client > printing from the server windows x2go > > Already, thanks <snip> Hi, Mario. Could you be a bit more detailed about where you are finding the problem. When you print from your X2Go desktop to the X2Go printer, what happens? Thanks - John
When I try to print from the client x2go desktop to the x2go printer nothings happens! The print job is queued in the spool of the x2go printer (cups server), nothings happens from the client side!
What I need is to understand how to configure the printing system, on both the client and the server side, to achieve redirect the print jobs on the server side to client's local printer. I saw no documentation on this configuration.
This is achievable with the current version of x2goserver/x2goprint/cups-x2go?
Since then, thanks for your answer <snip> Is the cups server running on the X2Go server? Yes! x2go server and tne cups server are in the same PC.
If not, I believe it needs the ability to SSH to it to transfer the file.
The printing is also dependent upon sshfs working properly. This should be relatively automagic assuming it is not being blocked by Windows.
On the X2Go server side, if you issue a mount command, do you see a print spool directory, e.g., sshuser@127.0.0.1:/cygdrive/C/DOCUME~1/MYID~1/X2GO~1/S-9270~1/spool on /tmp/spool_myid/myid-63-1312305869_stDKDE_dp32 type fuse.sshfs (rw,nosuid,nodev,max_read=65536,user=myid) I can see this type of mount! being logged in with my username, from the server in a console; can change dir to /tmp/spool_mario/mario-60-1312310981_stDGNOME_dp32 and I created 2 files in that directory: $ Echo "some text"> x.txt $ Echo "x.txt"> x.txt.ready
On the client PC, the window for print for x2go emerged.
Pressing the print button gave an error:
Window Title: Printing error Failed to execute command: C:\Archivos de programa\GhostGum\gsview\gsprint.exe -query -color C:/Documents and Settings/mario/.x2go/S-mario-60-1312310981_stDGNOME_dp32/spool/x.txt [OK button]
But that is not important; for now!
The important thing is that apparently the print jobs are not placed / created in the directory /tmp/spool_mario/mario-60-1312310981_stDGNOME_dp32
why? <snip> I really don't know. It has been quite a while since I setup X2Go
On Tue, 2011-08-02 at 17:10 -0300, Mario OROZ wrote: printing and our environment is very specialized. If I recall correctly, the X2Go print driver is a script or somewhere there is a script involved which places the files in the appropriate tmp directory. Is there any chance that script is not executable?
1 - I do not know perl!
The script / usr/lib/cups/backend/cups-x2go making the task of printing has permissions 0700 and owned by root and group is root
Reading the script I can see references to a user x2goprint, that is not created on my system. Instead it is added to the file / etc / sudoers
What we still do not recognize is how backen detects user's (not x2goprint user $spooldir) spool directory:
You may wish to find that script and edit it by adding some debug information. I usually add a logger command to send output or simply statements about where I am in the script to the syslog. This way, you can find out where the script is breaking. Hope that helps - John
How can i debug. What are those statement to make the script log to syslog?
<snip> Something like logger -t "X2GoPrint " "I at at such and such a point in the script"
As I mentioned, it is a long time since I've set up x2go printing and, although we highly customized it, it was pretty straightforward. You might want to doublecheck the instructions and see if you missed anything. Good luck - John