Re: [X2Go-Dev] Windows nightly crashes
Hi Uli, Try to debug the code using the debugger? Adding print lines is not the way to do it. I hope somebody can say how to re-compile the code with debug symbols and if gdb is good enough? Kind regards, Melroy van den Berg ‐‐‐ Original Message ‐‐‐ Op woensdag, mei 20, 2020 2:16 PM, Ulrich Sibiller schreef: > Running with --libssh-packetlog shows a bit more: > [2020/05/20 14:08:36.287745, 2] ssh_socket_connect: Nonblocking > connection socket: 2228 > [2020/05/20 14:08:36.287745, 2] ssh_connect: Socket connecting, now > waiting for the callbacks to work > [2020/05/20 14:08:36.288743, 3] ssh_connect: Actual timeout : 6 > [2020/05/20 14:08:36.293743, 3] ssh_socket_pollcallback: Received > POLLOUT in connecting state > [2020/05/20 14:08:36.293743, 1] socket_callback_connected: Socket > connection callback: 1 (0) > [2020/05/20 14:08:36.295746, 3] ssh_socket_unbuffered_write: Enabling > POLLOUT for socket > [2020/05/20 14:08:36.309751, 3] callback_receive_banner: Received > banner: SSH-2.0-OpenSSH_5.8 > [2020/05/20 14:08:36.312765, 2] ssh_client_connection_callback: SSH > server banner: SSH-2.0-OpenSSH_5.8 > [2020/05/20 14:08:36.313757, 2] ssh_analyze_banner: Analyzing banner: > SSH-2.0-OpenSSH_5.8 > [2020/05/20 14:08:36.314750, 2] ssh_analyze_banner: We are talking to > an OpenSSH client version: 5.8 (50800) > [2020/05/20 14:08:37.352741, 3] ssh_client_select_hostkeys: Order of > wanted host keys: > "ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss" > [2020/05/20 14:08:37.353749, 1] ssh_known_hosts_read_entries: Failed > to open the known_hosts file '/etc/ssh/ssh_known_hosts': No such file > or directory > [2020/05/20 14:08:37.354752, 3] ssh_client_select_hostkeys: > Algorithms found in known_hosts files: "ecdsa-sha2-nistp256" > [2020/05/20 14:08:37.355743, 3] ssh_client_select_hostkeys: Changing > host key method to > "ecdsa-sha2-nistp256,ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss" > [2020/05/20 14:08:37.355743, 3] ssh_socket_unbuffered_write: Enabling > POLLOUT for socket > [2020/05/20 14:08:37.356742, 3] packet_send2: packet: wrote [type=20, > len=940, padding_size=4, comp=935, payload=935] > [2020/05/20 14:08:37.356742, 3] ssh_send_kex: SSH_MSG_KEXINIT sent > [2020/05/20 14:08:37.357742, 3] ssh_packet_socket_callback: packet: > read type 20 [len=852,padding=5,comp=846,payload=846] > [2020/05/20 14:08:37.357742, 3] ssh_packet_process: Dispatching > handler for packet type 20 > [2020/05/20 14:08:37.357742, 2] ssh_kex_select_methods: Negotiated > ecdh-sha2-nistp256,ecdsa-sha2-nistp256,aes256-ctr,aes256-ctr,hmac-sha1,hmac-sha1,none,none,, > [2020/05/20 14:08:37.359741, 3] packet_send2: packet: wrote [type=30, > len=76, padding_size=5, comp=70, payload=70] > [2020/05/20 14:08:37.360741, 3] ssh_socket_unbuffered_write: Enabling > POLLOUT for socket > [2020/05/20 14:08:37.371817, 3] ssh_packet_socket_callback: packet: > read type 31 [len=292,padding=8,comp=283,payload=283] > [2020/05/20 14:08:37.371817, 3] ssh_packet_process: Dispatching > handler for packet type 31 > [2020/05/20 14:08:37.374742, 3] ssh_socket_unbuffered_write: Enabling > POLLOUT for socket > [2020/05/20 14:08:37.374742, 3] packet_send2: packet: wrote [type=21, > len=12, padding_size=10, comp=1, payload=1] > [2020/05/20 14:08:37.376744, 3] crypt_set_algorithms2: Set output > algorithm to aes256-ctr > [2020/05/20 14:08:37.376744, 3] crypt_set_algorithms2: Set HMAC > output algorithm to hmac-sha1 > [2020/05/20 14:08:37.377744, 3] crypt_set_algorithms2: Set input > algorithm to aes256-ctr > [2020/05/20 14:08:37.377744, 3] crypt_set_algorithms2: Set HMAC input > algorithm to hmac-sha1 > [2020/05/20 14:08:37.378742, 2] ssh_init_rekey_state: Set rekey after > 4294967296 blocks > [2020/05/20 14:08:37.378742, 2] ssh_init_rekey_state: Set rekey after > 4294967296 blocks > [2020/05/20 14:08:37.378742, 2] ssh_packet_client_ecdh_reply: > SSH_MSG_NEWKEYS sent > [2020/05/20 14:08:37.379742, 3] ssh_packet_socket_callback: > Processing 16 bytes left in socket buffer > [2020/05/20 14:08:37.379742, 3] ssh_packet_socket_callback: packet: > read type 21 [len=12,padding=10,comp=1,payload=1] > [2020/05/20 14:08:37.379742, 3] ssh_packet_process: Dispatching > handler for packet type 21 > [2020/05/20 14:08:37.380742, 2] ssh_packet_newkeys: Received SSH_MSG_NEWKEYS > [2020/05/20 14:08:37.382742, 2] ssh_packet_newkeys: Signature > verified and valid > [2020/05/20 14:08:37.382742, 3] ssh_connect: current state : 7 > x2go-DEBUG-../src/sshmasterconnection.cpp:869> Session port before > config file parse (part 2): 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:879> Session port after > config file parse (part 2): 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:903> cserverAuth > x2go-DEBUG-../src/sshmasterconnection.cpp:942> state: 1 > > x2go-DEBUG-../src/sshmasterconnection.cpp:674> Setting SSH directory > to C:/Users/XXX/ssh > > On Wed, May
Re: [X2Go-Dev] Windows nightly crashes
On Wed, May 20, 2020 at 5:08 PM Melroy van den Berg wrote: > Try to debug the code using the debugger? Adding print lines is not the way > to do it. "the debugger" is something I don't know. I am not developing software on Windows (I am not even using Windows if I can avoid it). Therefore I also have no development environment to do anything. On Linux I can install gdb and attach to any program but I simply do not know what's possible on Windows. I have read about minidumps and VS tools you need to debug. I have nothing like that. Is a minidump created automatically? Where can I find it? I have also tried to exchange the libssh by an older version but it is extremely difficult to find a compiled libssh.dll file for reasons I am not sure about. Seems like shared libs with a stable API is something that is not common in the Windows world... > I hope somebody can say how to re-compile the code with debug symbols and if > gdb is good enough? Not me, sorry... Uli ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Windows nightly crashes
Running with --libssh-packetlog shows a bit more: [2020/05/20 14:08:36.287745, 2] ssh_socket_connect: Nonblocking connection socket: 2228 [2020/05/20 14:08:36.287745, 2] ssh_connect: Socket connecting, now waiting for the callbacks to work [2020/05/20 14:08:36.288743, 3] ssh_connect: Actual timeout : 6 [2020/05/20 14:08:36.293743, 3] ssh_socket_pollcallback: Received POLLOUT in connecting state [2020/05/20 14:08:36.293743, 1] socket_callback_connected: Socket connection callback: 1 (0) [2020/05/20 14:08:36.295746, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2020/05/20 14:08:36.309751, 3] callback_receive_banner: Received banner: SSH-2.0-OpenSSH_5.8 [2020/05/20 14:08:36.312765, 2] ssh_client_connection_callback: SSH server banner: SSH-2.0-OpenSSH_5.8 [2020/05/20 14:08:36.313757, 2] ssh_analyze_banner: Analyzing banner: SSH-2.0-OpenSSH_5.8 [2020/05/20 14:08:36.314750, 2] ssh_analyze_banner: We are talking to an OpenSSH client version: 5.8 (50800) [2020/05/20 14:08:37.352741, 3] ssh_client_select_hostkeys: Order of wanted host keys: "ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss" [2020/05/20 14:08:37.353749, 1] ssh_known_hosts_read_entries: Failed to open the known_hosts file '/etc/ssh/ssh_known_hosts': No such file or directory [2020/05/20 14:08:37.354752, 3] ssh_client_select_hostkeys: Algorithms found in known_hosts files: "ecdsa-sha2-nistp256" [2020/05/20 14:08:37.355743, 3] ssh_client_select_hostkeys: Changing host key method to "ecdsa-sha2-nistp256,ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss" [2020/05/20 14:08:37.355743, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2020/05/20 14:08:37.356742, 3] packet_send2: packet: wrote [type=20, len=940, padding_size=4, comp=935, payload=935] [2020/05/20 14:08:37.356742, 3] ssh_send_kex: SSH_MSG_KEXINIT sent [2020/05/20 14:08:37.357742, 3] ssh_packet_socket_callback: packet: read type 20 [len=852,padding=5,comp=846,payload=846] [2020/05/20 14:08:37.357742, 3] ssh_packet_process: Dispatching handler for packet type 20 [2020/05/20 14:08:37.357742, 2] ssh_kex_select_methods: Negotiated ecdh-sha2-nistp256,ecdsa-sha2-nistp256,aes256-ctr,aes256-ctr,hmac-sha1,hmac-sha1,none,none,, [2020/05/20 14:08:37.359741, 3] packet_send2: packet: wrote [type=30, len=76, padding_size=5, comp=70, payload=70] [2020/05/20 14:08:37.360741, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2020/05/20 14:08:37.371817, 3] ssh_packet_socket_callback: packet: read type 31 [len=292,padding=8,comp=283,payload=283] [2020/05/20 14:08:37.371817, 3] ssh_packet_process: Dispatching handler for packet type 31 [2020/05/20 14:08:37.374742, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2020/05/20 14:08:37.374742, 3] packet_send2: packet: wrote [type=21, len=12, padding_size=10, comp=1, payload=1] [2020/05/20 14:08:37.376744, 3] crypt_set_algorithms2: Set output algorithm to aes256-ctr [2020/05/20 14:08:37.376744, 3] crypt_set_algorithms2: Set HMAC output algorithm to hmac-sha1 [2020/05/20 14:08:37.377744, 3] crypt_set_algorithms2: Set input algorithm to aes256-ctr [2020/05/20 14:08:37.377744, 3] crypt_set_algorithms2: Set HMAC input algorithm to hmac-sha1 [2020/05/20 14:08:37.378742, 2] ssh_init_rekey_state: Set rekey after 4294967296 blocks [2020/05/20 14:08:37.378742, 2] ssh_init_rekey_state: Set rekey after 4294967296 blocks [2020/05/20 14:08:37.378742, 2] ssh_packet_client_ecdh_reply: SSH_MSG_NEWKEYS sent [2020/05/20 14:08:37.379742, 3] ssh_packet_socket_callback: Processing 16 bytes left in socket buffer [2020/05/20 14:08:37.379742, 3] ssh_packet_socket_callback: packet: read type 21 [len=12,padding=10,comp=1,payload=1] [2020/05/20 14:08:37.379742, 3] ssh_packet_process: Dispatching handler for packet type 21 [2020/05/20 14:08:37.380742, 2] ssh_packet_newkeys: Received SSH_MSG_NEWKEYS [2020/05/20 14:08:37.382742, 2] ssh_packet_newkeys: Signature verified and valid [2020/05/20 14:08:37.382742, 3] ssh_connect: current state : 7 x2go-DEBUG-../src/sshmasterconnection.cpp:869> Session port before config file parse (part 2): 22 x2go-DEBUG-../src/sshmasterconnection.cpp:879> Session port after config file parse (part 2): 22 x2go-DEBUG-../src/sshmasterconnection.cpp:903> cserverAuth x2go-DEBUG-../src/sshmasterconnection.cpp:942> state: 1 x2go-DEBUG-../src/sshmasterconnection.cpp:674> Setting SSH directory to C:/Users/XXX/ssh On Wed, May 20, 2020 at 1:52 PM Ulrich Sibiller wrote: > > Running with --libssh-debug does not provide any further hint: > x2go-DEBUG-../src/sshmasterconnection.cpp:805> Session port after > config file parse: 22 > [2020/05/20 13:49:23.492000, 2] ssh_connect: libssh 0.9.3 (c) > 2003-2019 Aris Adamantiadis, Andreas Schneider and libssh > contributors. Distributed under the LGPL, please refer to COPYING file > for information about your rights, using threading threads_pthr
Re: [X2Go-Dev] Windows nightly crashes
Running with --libssh-debug does not provide any further hint: x2go-DEBUG-../src/sshmasterconnection.cpp:805> Session port after config file parse: 22 [2020/05/20 13:49:23.492000, 2] ssh_connect: libssh 0.9.3 (c) 2003-2019 Aris Adamantiadis, Andreas Schneider and libssh contributors. Distributed under the LGPL, please refer to COPYING file for information about your rights, using threading threads_pthread [2020/05/20 13:49:23.502982, 2] ssh_socket_connect: Nonblocking connection socket: 2192 [2020/05/20 13:49:23.503982, 2] ssh_connect: Socket connecting, now waiting for the callbacks to work [2020/05/20 13:49:23.508040, 1] socket_callback_connected: Socket connection callback: 1 (0) [2020/05/20 13:49:23.523984, 2] ssh_client_connection_callback: SSH server banner: SSH-2.0-OpenSSH_5.8 [2020/05/20 13:49:23.523984, 2] ssh_analyze_banner: Analyzing banner: SSH-2.0-OpenSSH_5.8 [2020/05/20 13:49:23.524982, 2] ssh_analyze_banner: We are talking to an OpenSSH client version: 5.8 (50800) [2020/05/20 13:49:24.665982, 1] ssh_known_hosts_read_entries: Failed to open the known_hosts file '/etc/ssh/ssh_known_hosts': No such file or directory [2020/05/20 13:49:24.666982, 2] ssh_kex_select_methods: Negotiated ecdh-sha2-nistp256,ecdsa-sha2-nistp256,aes256-ctr,aes256-ctr,hmac-sha1,hmac-sha1,none,none,, [2020/05/20 13:49:24.684982, 2] ssh_init_rekey_state: Set rekey after 4294967296 blocks [2020/05/20 13:49:24.686022, 2] ssh_init_rekey_state: Set rekey after 4294967296 blocks [2020/05/20 13:49:24.687983, 2] ssh_packet_client_ecdh_reply: SSH_MSG_NEWKEYS sent [2020/05/20 13:49:24.687983, 2] ssh_packet_newkeys: Received SSH_MSG_NEWKEYS -> then it crashes On Wed, May 20, 2020 at 12:36 PM Ulrich Sibiller wrote: > > Here's the output of the centos7 nightly build > x2goclient-4.1.2.3-0.0x2go1.0.git20200520.1947.heuler.el7.x86_64 which > is working with the same session setup: > > x2go-DEBUG-../src/sshmasterconnection.cpp:795> Session port before > config file parse: 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:805> Session port after > config file parse: 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:869> Session port before > config file parse (part 2): 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:879> Session port after > config file parse (part 2): 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:903> cserverAuth > x2go-DEBUG-../src/sshmasterconnection.cpp:942> state: 1 > ---> Windows version stopped here > x2go-DEBUG-../src/sshmasterconnection.cpp:1206> Challenge > authentication requested. > > x2go-DEBUG-../src/sshmasterconnection.cpp:1084> Have prompts: 1 > > x2go-DEBUG-../src/sshmasterconnection.cpp:1088> Prompt[0]: |Password: | > > x2go-DEBUG-../src/sshmasterconnection.cpp:1092> Password request > > x2go-DEBUG-../src/sshmasterconnection.cpp:1084> Have prompts: 0 > > x2go-DEBUG-../src/sshmasterconnection.cpp:1170> Challenge authentication OK. > > On Wed, May 20, 2020 at 12:12 PM Ulrich Sibiller > wrote: > > > > Hi, > > > > both x2goclient for windows 4.1.2.2-20200213 and > > https://code.x2go.org/releases/binary-win32/x2goclient/heuler/mingw32-4.8/qt-4.8/x2goclient-4.1.2.3-2020.05.20-a1a2f62-setup.exe > > are crashing during connection establishment when using a proxy > > (output from the debug build): > > > > x2go-DEBUG-../src/onmainwindow.cpp:2931> Starting new ssh connection > > to server:"!myremotehost":"22" krbLogin: false > > x2go-DEBUG-../src/sshmasterconnection.cpp:168> SshMasterConnection, > > host "!myremotehost"; port 22; user "yyy"; useproxy true; proxyserver > > "!10.11.12.13"; proxyport 22 > > x2go-DEBUG-../src/sshmasterconnection.cpp:495> proxyserver: > > "!10.11.12.13"; proxyport: 22; proxylogin: "remoteuser" > > x2go-DEBUG-../src/sshmasterconnection.cpp:168> SshMasterConnection, > > host "!10.11.12.13"; port 22; user "remoteuser"; useproxy false; > > proxyserver ""; proxyport 0 > > x2go-DEBUG-../src/sshmasterconnection.cpp:248> Starting SSH connection > > without Kerberos authentication. > > x2go-DEBUG-../src/sshmasterconnection.cpp:250> SshMasterConnection, > > instance SshMasterConnection(0x3917608) created. > > x2go-DEBUG-../src/sshmasterconnection.cpp:492> SshMasterConnection, > > instance SshMasterConnection(0x3917608) entering thread. > > x2go-DEBUG-../src/sshmasterconnection.cpp:573> Setting SSH directory > > to C:/Users/LOCALUSER/ssh > > x2go-DEBUG-../src/sshmasterconnection.cpp:795> Session port before > > config file parse: 22 > > x2go-DEBUG-../src/sshmasterconnection.cpp:805> Session port after > > config file parse: 22 > > x2go-DEBUG-../src/sshmasterconnection.cpp:869> Session port before > > config file parse (part 2): 22 > > x2go-DEBUG-../src/sshmasterconnection.cpp:879> Session port after > > config file parse (part 2): 22 > > x2go-DEBUG-../src/sshmasterconnection.cpp:903> cserverAuth > > x2go-DEBUG-../src/sshmasterconnection.cpp:942> state: 1 > > x2go-DEBUG-../src/sshmasterconnection.cpp:674> Setting SSH directory > > to C:/Users/LOCALUSER/ssh > > > > and then x2go completely
Re: [X2Go-Dev] Windows nightly crashes
Here's the output of the centos7 nightly build x2goclient-4.1.2.3-0.0x2go1.0.git20200520.1947.heuler.el7.x86_64 which is working with the same session setup: x2go-DEBUG-../src/sshmasterconnection.cpp:795> Session port before config file parse: 22 x2go-DEBUG-../src/sshmasterconnection.cpp:805> Session port after config file parse: 22 x2go-DEBUG-../src/sshmasterconnection.cpp:869> Session port before config file parse (part 2): 22 x2go-DEBUG-../src/sshmasterconnection.cpp:879> Session port after config file parse (part 2): 22 x2go-DEBUG-../src/sshmasterconnection.cpp:903> cserverAuth x2go-DEBUG-../src/sshmasterconnection.cpp:942> state: 1 ---> Windows version stopped here x2go-DEBUG-../src/sshmasterconnection.cpp:1206> Challenge authentication requested. x2go-DEBUG-../src/sshmasterconnection.cpp:1084> Have prompts: 1 x2go-DEBUG-../src/sshmasterconnection.cpp:1088> Prompt[0]: |Password: | x2go-DEBUG-../src/sshmasterconnection.cpp:1092> Password request x2go-DEBUG-../src/sshmasterconnection.cpp:1084> Have prompts: 0 x2go-DEBUG-../src/sshmasterconnection.cpp:1170> Challenge authentication OK. On Wed, May 20, 2020 at 12:12 PM Ulrich Sibiller wrote: > > Hi, > > both x2goclient for windows 4.1.2.2-20200213 and > https://code.x2go.org/releases/binary-win32/x2goclient/heuler/mingw32-4.8/qt-4.8/x2goclient-4.1.2.3-2020.05.20-a1a2f62-setup.exe > are crashing during connection establishment when using a proxy > (output from the debug build): > > x2go-DEBUG-../src/onmainwindow.cpp:2931> Starting new ssh connection > to server:"!myremotehost":"22" krbLogin: false > x2go-DEBUG-../src/sshmasterconnection.cpp:168> SshMasterConnection, > host "!myremotehost"; port 22; user "yyy"; useproxy true; proxyserver > "!10.11.12.13"; proxyport 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:495> proxyserver: > "!10.11.12.13"; proxyport: 22; proxylogin: "remoteuser" > x2go-DEBUG-../src/sshmasterconnection.cpp:168> SshMasterConnection, > host "!10.11.12.13"; port 22; user "remoteuser"; useproxy false; > proxyserver ""; proxyport 0 > x2go-DEBUG-../src/sshmasterconnection.cpp:248> Starting SSH connection > without Kerberos authentication. > x2go-DEBUG-../src/sshmasterconnection.cpp:250> SshMasterConnection, > instance SshMasterConnection(0x3917608) created. > x2go-DEBUG-../src/sshmasterconnection.cpp:492> SshMasterConnection, > instance SshMasterConnection(0x3917608) entering thread. > x2go-DEBUG-../src/sshmasterconnection.cpp:573> Setting SSH directory > to C:/Users/LOCALUSER/ssh > x2go-DEBUG-../src/sshmasterconnection.cpp:795> Session port before > config file parse: 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:805> Session port after > config file parse: 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:869> Session port before > config file parse (part 2): 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:879> Session port after > config file parse (part 2): 22 > x2go-DEBUG-../src/sshmasterconnection.cpp:903> cserverAuth > x2go-DEBUG-../src/sshmasterconnection.cpp:942> state: 1 > x2go-DEBUG-../src/sshmasterconnection.cpp:674> Setting SSH directory > to C:/Users/LOCALUSER/ssh > > and then x2go completely vanishes. > > Any ideas how to debug this further? > > Uli ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Windows nightly crashes
Hi, both x2goclient for windows 4.1.2.2-20200213 and https://code.x2go.org/releases/binary-win32/x2goclient/heuler/mingw32-4.8/qt-4.8/x2goclient-4.1.2.3-2020.05.20-a1a2f62-setup.exe are crashing during connection establishment when using a proxy (output from the debug build): x2go-DEBUG-../src/onmainwindow.cpp:2931> Starting new ssh connection to server:"!myremotehost":"22" krbLogin: false x2go-DEBUG-../src/sshmasterconnection.cpp:168> SshMasterConnection, host "!myremotehost"; port 22; user "yyy"; useproxy true; proxyserver "!10.11.12.13"; proxyport 22 x2go-DEBUG-../src/sshmasterconnection.cpp:495> proxyserver: "!10.11.12.13"; proxyport: 22; proxylogin: "remoteuser" x2go-DEBUG-../src/sshmasterconnection.cpp:168> SshMasterConnection, host "!10.11.12.13"; port 22; user "remoteuser"; useproxy false; proxyserver ""; proxyport 0 x2go-DEBUG-../src/sshmasterconnection.cpp:248> Starting SSH connection without Kerberos authentication. x2go-DEBUG-../src/sshmasterconnection.cpp:250> SshMasterConnection, instance SshMasterConnection(0x3917608) created. x2go-DEBUG-../src/sshmasterconnection.cpp:492> SshMasterConnection, instance SshMasterConnection(0x3917608) entering thread. x2go-DEBUG-../src/sshmasterconnection.cpp:573> Setting SSH directory to C:/Users/LOCALUSER/ssh x2go-DEBUG-../src/sshmasterconnection.cpp:795> Session port before config file parse: 22 x2go-DEBUG-../src/sshmasterconnection.cpp:805> Session port after config file parse: 22 x2go-DEBUG-../src/sshmasterconnection.cpp:869> Session port before config file parse (part 2): 22 x2go-DEBUG-../src/sshmasterconnection.cpp:879> Session port after config file parse (part 2): 22 x2go-DEBUG-../src/sshmasterconnection.cpp:903> cserverAuth x2go-DEBUG-../src/sshmasterconnection.cpp:942> state: 1 x2go-DEBUG-../src/sshmasterconnection.cpp:674> Setting SSH directory to C:/Users/LOCALUSER/ssh and then x2go completely vanishes. Any ideas how to debug this further? Uli ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
