Mistyped the topic; now corrected. Full paste of body below.
Sorry for any inconveniences! X-/
Nice day to everyone!
Regarding: x2goserver 3.0.99.5-0~x2go3+wheezy~heuler~20110728~182~build1
If "x2gogetagent" is to keep its place below
Nice day to everyone!
Regarding: x2goserver 3.0.99.5-0~x2go3+wheezy~heuler~20110728~182~build1
If "x2gogetagent" is to keep its place below ".../lib/x2go/" then the
following change seems appropriate, because otherwise session-resuming
fails with error-message "x2gogetagent not found".
.../bin/
Hi,
I'm not sure if this has been discussed previously, but PowerPC-support was
removed in OS X Lion. Since x2go uses nxproxy, which is compiled on PPC, it
fails to display the remote desktop (it connects and creates sessions just
fine), yielding the following error in Finder:
"You can't open
Hi Mike,
2011/7/29 Mike Gabriel :
> The connecting stuff is a bit tricky...
>
> - x2gostartagent will try to detect a free server-side port >3.
> This port is put into the session database table. (Make sure you do
> not have other server-side stuff running that claims ports between
>
Hi Morty,
On Fr 29 Jul 2011 10:55:27 CEST Moritz Struebe wrote:
On 2011-07-29 10:39, Mike Gabriel wrote:
1.
Place file ,,profilename'' in the .x2go/ directory to
become able to relate between server and client.
Why is this needed?
I do think we must relate a session profile to a server, tho
On 2011-07-29 10:39, Mike Gabriel wrote:
>
> 1.
> Place file ,,profilename'' in the .x2go/ directory to
> become able to relate between server and client.
Why is this needed?
I do think we must relate a session profile to a server, though.
Especially when using a shared home, but a local sqlite da
Hi all,
for post-Baikal coding here the first proposal to get rid of (or
minimize) the lost .x2go/ directories:
1.
Place file ,,profilename'' in the .x2go/ directory to
become able to relate between server and client.
2.
When connecting to an X2go server do the following:
o do everythi
Hi Daniel,
On Fr 29 Jul 2011 07:24:40 CEST Daniel Lindgren wrote:
[...]
I've been trying to think of some way to make x2go automatically only
use free ports, but since there are possibly several clients and
servers involved in multiple incoming and outgoing sessions, the only
safe way I've com