Re: [X2go-Dev] Berlios is closing
Am 14.10.2011 21:43, Heinz-M. Graesing schrieb: Thanks to Gmane the history of the groups will survive. Why not download the history from Berlios and upload it to the new ML-server? If it isn't too much trouble, of course. But exports are mbox, and most systems can also import that. Cheers Morty ___ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-Dev] OT: exclude /usr/lib/x2go/libX11.so.6 from being linked by other apps
V Sat, 15 Oct 2011 20:32:38 +0300
Ivan Kabaivanov chep...@yahoo.com napsáno:
Hi Milan,
Hello Ivan,
check if /usr/lib/x2go is listed in /etc/ld.so.conf (or whatever
file/directory your distribution is using). If it is listed, remove
it and re-run /sbin/ldconfig. Then create a wrapper to start
x2goagent with the correct LD_LIBRARY_PATH.
The man page of ldconfig reads that /usr/lib is a trusted directory
and as such is not specified extra in /etc/ld.so.conf.d
nor /etc/ld.so.conf. /usr/lib/x2go is neither listed in the ld.so conf
files.
So far, the only problem seems to be with darktable, whose cmake script
looks in any subdir of /usr/lib - the configuration log file
shows it found x2go/libx11.so.6. I am not sure if it is an error of
darktable cmake configuration or if this is an expected behaviour.
Just for the curiosity, I have checked all binaries in /usr/bin and none
is dynamically linked to /usr/lib/x2go/...
Devs, perhaps it would be a good idea to change the x2goagent code
and rename the above libs to ${lib}-x2go.so.* or some such? Then
they can safely be installed in /usr/lib without fear of interfering
with other programs.
This could be a solution for me. As a workaround, I have simply
moved /usr/lib/x2go temporarily away and compiled darktable.
Thanks for the hints.
Regards,
Milan
--
http://www.milan-knizek.net/
About linux and photography (Czech only)
O linuxu a fotografování
___
X2go-Dev mailing list
X2go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev
[X2go-Dev] Problem with windows x2go client 3.99.0.1
Hello, x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian. 3.01.18 under ubuntu with no problem Where is the problem? ___ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-Dev] Problem with windows x2go client 3.99.0.1
On Sat, 2011-10-15 at 20:38 +0200, va...@spsmb.cz wrote: Hello, x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian. 3.01.18 under ubuntu with no problem Where is the problem? snip I've noticed the exact same thing. I assumed it was because I am using 3.0.1-5 on the server side and there was a backwards compatibility issue so I postponed investigation until I have a chance to upgrade the server side - John ___ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-Dev] Problem with windows x2go client 3.99.0.1
On Sat, 2011-10-15 at 22:40 +0200, va...@spsmb.cz wrote: Dne 15.10.2011 20:56, John A. Sullivan III napsal(a): On Sat, 2011-10-15 at 20:38 +0200, va...@spsmb.cz wrote: Hello, x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian. 3.01.18 under ubuntu with no problem Where is the problem? snip I've noticed the exact same thing. I assumed it was because I am using 3.0.1-5 on the server side and there was a backwards compatibility issue so I postponed investigation until I have a chance to upgrade the server side - John snip I use most recent x2go server (3.0.99.6). Only 3.01-4 client from http://www.x2go.org/index.php?id=7 works (3.01-2 should work but there are trojans inside of installation package). snip Hmm . . . smells like libssh. I wonder if it's related to another problem we are seeing in Linux with the newer clients; we are constantly dropping SSH sessions. Sound, file sharing, printing, all those functions which rely upon the reverse ssh forwarding all break after a while. Suspending and resuming the session restores them - John ___ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-Dev] Problem with windows x2go client 3.99.0.1
Dne 15.10.2011 23:01, John A. Sullivan III napsal(a): On Sat, 2011-10-15 at 22:40 +0200, va...@spsmb.cz wrote: Dne 15.10.2011 20:56, John A. Sullivan III napsal(a): On Sat, 2011-10-15 at 20:38 +0200, va...@spsmb.cz wrote: Hello, x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian. 3.01.18 under ubuntu with no problem Where is the problem? snip I've noticed the exact same thing. I assumed it was because I am using 3.0.1-5 on the server side and there was a backwards compatibility issue so I postponed investigation until I have a chance to upgrade the server side - John snip I use most recent x2go server (3.0.99.6). Only 3.01-4 client from http://www.x2go.org/index.php?id=7 works (3.01-2 should work but there are trojans inside of installation package). snip Hmm . . . smells like libssh. I wonder if it's related to another problem we are seeing in Linux with the newer clients; we are constantly dropping SSH sessions. Sound, file sharing, printing, all those functions which rely upon the reverse ssh forwarding all break after a while. Suspending and resuming the session restores them - John ___ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev x2go client 3.99.0.1 under ubuntu (with new libssl) works, but not under windows. ___ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-Dev] Problem with windows x2go client 3.99.0.1
On Sun, 2011-10-16 at 03:52 +0200, va...@spsmb.cz wrote: Dne 15.10.2011 23:01, John A. Sullivan III napsal(a): On Sat, 2011-10-15 at 22:40 +0200, va...@spsmb.cz wrote: Dne 15.10.2011 20:56, John A. Sullivan III napsal(a): On Sat, 2011-10-15 at 20:38 +0200, va...@spsmb.cz wrote: Hello, x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian. 3.01.18 under ubuntu with no problem Where is the problem? snip I've noticed the exact same thing. I assumed it was because I am using 3.0.1-5 on the server side and there was a backwards compatibility issue so I postponed investigation until I have a chance to upgrade the server side - John snip I use most recent x2go server (3.0.99.6). Only 3.01-4 client from http://www.x2go.org/index.php?id=7 works (3.01-2 should work but there are trojans inside of installation package). snip Hmm . . . smells like libssh. I wonder if it's related to another problem we are seeing in Linux with the newer clients; we are constantly dropping SSH sessions. Sound, file sharing, printing, all those functions which rely upon the reverse ssh forwarding all break after a while. Suspending and resuming the session restores them - John snip x2go client 3.99.0.1 under ubuntu (with new libssl) works, but not under windows. snip It works for us too under Squeeze in the sense the session is established and all works initially. However, after a while, the sound stops. Does this happen to you? - John ___ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-Dev] Problem with windows x2go client 3.99.0.1
x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. Two things I've had problems with that sound similar: 1) Symantec antivirus on 64-bit Windows 7 seems to interfere with x2go clients newer than 3.0-13, even if Symantec antivirus is completely disabled. Try 3.01-13 from http://code.x2go.org/releases/binary-win32/x2goclient/pre-git/ or uninstall antivirus. Microsoft Security Essentials (free for personal use) worked with 3.99.0.1 on W7 x64 last time I tried. 2) If the server that you're connecting to also is a client (ClientA - ServerA - ServerB), there could be a port conflict. Default incoming port 30001 is already in use by an outgoing tunnel on the same port. Try modifying /usr/bin/x2gostartagent on ServerA and change the port interval from 3 to 30200. Do the same on ServerB, but use 30400. Close all existing client sessions to/from the servers in the chain and try again. Cheers, Daniel ___ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
