Hi Bernhard,
On Mo 12 Jan 2015 18:34:29 CET, Mayr, Bernhard J. | elexis-austria wrote:
Thank you for help and your gentle offer. Yet I would like to get x2go
work out of the box. especially as our users own different platforms
(linux, windows, mac).
I understand that.
After research on cups in ubuntu 14.04 I found out that I had to install
the cups-bsd compatibility package. Now the error log changed:
Well... I just checked the content of the cups-bsd package and it
seems absolutely unrelated to X2Go's client-side printing mech.
The only thing that might be relevant is the list of dependencies:
libc6 (= 2.4), libcups2 (= 1.4.0), debconf (= 0.5) | debconf-2.0,
cups-client (= 1.5.3-5+deb7u4), update-inetd, cups-common
- on Debian jessie
Could you check /var/log/dpkg.log for other packages that got pulled
in with the installation of cups-bsd? If you are right that a package
has been missing, we need to add it as a dependency for cups-x2go
and/or x2goserver-printing.
excerpt from the syslog:
Jan 12 18:33:40 eaustria /usr/lib/cups/backend/cups-x2go[1874]: Call to
printfile function with: /tmp/20-bmayr-cupsjob1874.pdf
/tmp/20-bmayr-cupsjob1874.pdf.title eaustria.app.server
bmayr-55-1421082562_stRPUBLISHED_dp24
Jan 12 18:33:40 eaustria /usr/lib/cups/backend/cups-x2go[1874]:
x2goprint bmayr bmayr-55-1421082562_stRPUBLISHED_dp24
bmayr-55-1421082562_stRPUBLISHED_dp24_20-bmayr-cupsjob1874.pdf
bmayr-55-1421082562_stRPUBLISHED_dp24_20-bmayr-cupsjob1874.pdf.title
In the above log message I count command (x2goprint) plus four
arguments, right?
Jan 12 18:33:40 eaustria /usr/bin/x2goprint.orig[1903]: ERROR: x2goprint
was called with a wrong number of cmd line args, x2goprint exits now!
What should be the right number of arguments and how can I change them?
The code that triggers the error message is this:
elsif (scalar(@ARGV) != 4)
{
syslog('err', ERROR: x2goprint was called with a wrong number of
cmd line args, x2goprint exits now!);
print { \*STDERR } ERROR: Usage:\nx2goprint user session file
titleFile\nx2goprint user\n;
exit 1;
}
I see that not x2goprint is called, but x2goprint.orig. Did you change
anything in that script? Did you use a wrapper?
Please get everything back in place and use the default installation
of x2goserver-printing for testing or fix the test setup (the wrapper
script you use).
You can also enable debugging for x2goserver-printing in
/etc/x2go/x2goserver.conf. That should show you how x2goprint(.orig)
gets launched, including the used cmdline options.
Mike
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgpojWBCKoa9S.pgp
Description: Digitale PGP-Signatur
___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user
