On Tue, Jul 19, 2011 at 8:34 PM, John A. Sullivan III <jsullivan@opensourcedevel.com> wrote:
The disappearing mouse pointer is an Xming bug. Moving to vcxsrv will solve that. I think 3.0.1.14 was the first to support that but I'm not sure.
It may be, but on Window 7 64-bit, 3.01-14 and later are highly problematic.
We are also using an old X2Go Server - 3.0.1-5 I believe.
Which reminds me, what is the best way to determine the version of the installed x2goserver scripts (without looking at the package information)? I tried x2goagent does not seem to have --version as an option.
Hi John,
On Mi 20 Jul 2011 05:43:42 CEST John Williams wrote:
We are also using an old X2Go Server - 3.0.1-5 I believe.
Which reminds me, what is the best way to determine the version of the installed x2goserver scripts (without looking at the package information)? I tried x2goagent does not seem to have --version as an option.
In the x2goserver-extensions package I have added a script
,,x2goversion'' that gives you the versions of the server-side
component. Refer to the man page (man x2goversion) for details. This
x2goversion script, however, only work with latest X2go components
installed from Launchpad (Ubuntu) or from packages.x2go.org (Debian).
For x2goagent 3.5.0.2, unfortunately, I have just realized, that
x2goversion still shows the wrong version number (3.4.0.something).
This will be fixed within in the next half hour..
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Tue, 2011-07-19 at 20:43 -0700, John Williams wrote:
On Tue, Jul 19, 2011 at 8:34 PM, John A. Sullivan III <jsullivan@opensourcedevel.com> wrote:
The disappearing mouse pointer is an Xming bug. Moving to vcxsrv will solve that. I think 3.0.1.14 was the first to support that but I'm not sure.
It may be, but on Window 7 64-bit, 3.01-14 and later are highly problematic.
We are also using an old X2Go Server - 3.0.1-5 I believe.
Which reminds me, what is the best way to determine the version of the installed x2goserver scripts (without looking at the package information)? I tried x2goagent does not seem to have --version as an option. <snip> I'm on Debian so I do: dpkg-query -l x2goserver
-
John A. Sullivan III -
John Williams -
Mike Gabriel