[X2Go-Dev] Problem integrating x2go into Linux-system

Stefan Baur X2Go-ML-1 at baur-itcs.de
Thu Aug 6 11:42:55 CEST 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Am 05.08.2015 um 14:27 schrieb Heinz-Ado Arnolds:
> Dear Mr. Bauer,
> 
> thanks for your immediate response!
> 
> On 05.08.2015 12:30, Stefan Baur wrote: ...
>> Since you're using a custom-built Linux distribution, it would
>> most likely be helpful to know what it is based on - Debian,
>> Ubuntu, Fedora Core, Red Hat, ... and the corresponding version
>> number.
> 
> Our system is build from scratch, no package manager. I used 
> x2goclient-4.0.5.0 x2goserver-4.0.1.19 nx-libs-3.5.0.32.tar.gz
> 
> System environment: gcc-5.2.0 glibc-2.21 linux-4.1.3
> 
>> Another thing to check: Are you using banners, like, for example
>> in /etc/hosts.allow?
> 
> No banners, no .profile, no /etc/profile
> 
> Would be really great if you have a look at client-sessions1:
> 
> Proxy: Identified message of 14 bytes for FD#6 channel ID#1. 
> handleWrite: Called for FD#6. handleWrite: Decoding messages for
> FD#6 with 14 bytes in the buffer.
> 
> a working connection shows
> 
> Proxy: Identified message of 50 bytes for FD#6 channel ID#1. 
> handleWrite: Called for FD#6. handleWrite: Decoding messages for
> FD#6 with 50 bytes in the buffer.
> 
> I assume that the fake cookie can't be set. Di you have any hint
> where to look for this?

In the meantime, Mihai Moldovan (ionic at ionic.de) took a look at your
logfiles.  He suggested you run a compile of nx-libs using the
"typescript" logging tool, and to post the logfile(s) here.

Two more bits of information:
- - The message "Loop: Assuming NX client location
'/home/arnolds/opt/x2go/bin/x2goclient'." looked weird to Mihai.  I'm
not sure what exactly he was referring to, the path of X2GoClient
residing in a subdirectory of your home directory, maybe?  Is that
intentional?

- - It would be interesting to see what happens when you connect to an
MPA-Linux-based X2GoServer from an Ubuntu Client.  You tested it from
an Ubuntu client to an MPA server, and from an MPA client to an MPA
server.  Testing it in the other direction would help to rule out or
confirm that it is an issue that requires an MPA Linux on both ends to
occur.

Kind Regards,
Stefan Baur


- -- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVwywfAAoJEG7d9BjNvlEZW/wH/1PN2RE4ZoSsnsx93qA9lN4O
2sUUO3kkre82Wat1ZS8Tp0b5oiBsazrGcjm4gzDHD3+Yof0r6LmbFrJ42FNK+7Gg
1lJYUSN7ghu1mzpgfyK25VHgpoVEoiMpTFb9kmL4+53/91hoEx9v7nrHWO0kVb9U
AqLVNn44JZHOv5xtQbfbDDcSPfYvQNXv+kKMWta3mrRAwUCVHiVVY1BXqbgcRgx3
zT364eH1fLommHoH+H3djhoQEmqSJeT4m2WSPtRZUjfQWeX2v1EV5TcpfsFelvf6
QT4qwqCAKOT4rNLp5keegLN6nnlFzxkEk9wyXM7XA1olROWkqIcX8yBhB+DDw54=
=WfOU
-----END PGP SIGNATURE-----


More information about the x2go-dev mailing list