x2go-dev April 2018

x2go-dev@lists.x2go.org

15 participants
102 discussions

Bug#1012: Session reconnect doesn't work (x2gobroker)
by Stefan Baur 07 Sep '18

07 Sep '18

package: x2gobroker version: 0.0.3.0 Situation: two identical nodes, only difference is DNS name + IP Desired result: load-balanced X2Go systems, where a suspended session can be resumed Actual outcome: Each connect starts a new session, suspended sessions are left dangling forever Questions: 1) Is x2gobroker-daemon needed at all for ssh-only connections to the broker? 2) Did I miss any obvious steps? 3) What would be the suggested path to debug this? A full typescript recording of the installation process is available, but as no command returned any error messages, let me shorten it down to the commands that were executed: # commands executed on both first and second node apt-get install x2gobroker -y cp /etc/x2go/x2gobroker.conf /etc/x2go/x2gobroker.conf.orig vi /etc/x2go/x2gobroker.conf # see diff below apt-get install x2gobroker-agent -y cp /etc/x2go/broker/x2gobroker-sessionprofiles.conf /etc/x2go/broker/x2gobroker-sessionprofiles.conf.orig vi /etc/x2go/broker/x2gobroker-sessionprofiles.conf # see diff below x2gobroker-keygen cp /var/lib/x2gobroker/.ssh/id_rsa.pub /tmp/ cd /tmp/ vi id_rsa.pub # added a blank and the server name to end of file python -m SimpleHTTPServer 8081 # run temporary web server so second node can fetch the file # once both web servers were up, the following commands were executed # on BOTH nodes: x2gobroker-pubkeyauthorizer -t http://firstnode:8081/id_rsa.pub x2gobroker-pubkeyauthorizer -t http://secondnode:8081/id_rsa.pub # Sadly, no working session reconnect with these command line # parameters - it always starts a new session: x2goclient --broker-url=ssh://accountwithapublickey@firstnode:22/usr/bin/x2gobroker --broker-autologin # This is using x2goclient-4.0.5.0-2015.07.31 # taking a closer look at # http://wiki.x2go.org/doku.php/doc:installation:x2gobroker: # maybe x2gobroker-daemon is missing? So ... apt-get install x2gobroker-daemon -y # this also pulls in x2gobroker-authservice # Sadly, no change, still no working session reconnect :-( # --------------------------------------------------------- diff -u /etc/x2go/x2gobroker.conf.orig /etc/x2go/x2gobroker.conf --- /etc/x2go/x2gobroker.conf.orig 2016-03-19 18:39:02.034407506 +0100 +++ /etc/x2go/x2gobroker.conf 2016-03-19 19:56:05.781729565 +0100 @@ -241,6 +241,7 @@ # The agent query mode can be configured on a per-broker-backend basis, the # below value is the default. #default-agent-query-mode=NONE +default-agent-query-mode=SSH # Probe SSH port of X2Go Servers (availability check) # @@ -254,7 +255,7 @@ # Per default, we set this to "true" here. The portscan feature can be # deactivated on a per-session-profile basis (use: broker-portscan-x2goservers = # false in the session profile configuration). -#default-portscan-x2goservers = true +default-portscan-x2goservers = false # Use load checker for querying X2Go Servers' loads in regular intervals # @@ -294,13 +295,13 @@ # o the session profile does not block queries to the load checker daemon # on a per profile basis # -#default-use-load-checker = false +default-use-load-checker = true # If the x2gobroker-loadchecker daemon gets used, define here how # many seconds to sleep between cycles of querying system load from the # associated X2Go Servers. # -#load-checker-intervals = 300 +load-checker-intervals = 300 ### @@ -345,9 +346,8 @@ #desktop-shell = KDE [broker_inifile] -#enable = true -#session-profiles = /etc/x2go/broker/x2gobroker-sessionprofiles.conf -#use-load-checker = false +enable = true +session-profiles = /etc/x2go/broker/x2gobroker-sessionprofiles.conf #[broker_ldap] -> MUSIC OF THE FUTURE #enable = false # --------------------------------------------------------- # --------------------------------------------------------- diff -u /etc/x2go/broker/x2gobroker-sessionprofiles.conf.orig /etc/x2go/broker/x2gobroker-sessionprofiles.conf --- /etc/x2go/broker/x2gobroker-sessionprofiles.conf.orig 2016-03-19 19:19:33.995277777 +0100 +++ /etc/x2go/broker/x2gobroker-sessionprofiles.conf 2016-03-19 19:58:45.407309387 +0100 @@ -63,146 +63,12 @@ directrdp=false user=BROKER_USER -[localhost-kde] -name=KDE - localhost -host=localhost -command=KDE +[GloveBox] +host=firstnode (firstnodeip), secondnode (secondnodeip) +name=GloveBox +published=true usebrokerpass=true - -[localhost-mate] -name=MATE - localhost -host=localhost -command=MATE -usebrokerpass=true - -[localhost-shadow] -name=SHADOW - localhost -# don't even try load-balancing here... it makes not sense and won't work (first given host will be used!) -host=localhost -command=SHADOW -usebrokerpass=true - -### EXAMPLES: Below you find some config examples. Adapt them to your needs or -### simply write your own session profiles and remove the examples below. - -## -## EXAMPLE: pool-A (staff servers) -## -## The pool-A contains three X2Go Servers (server-A, server-B and server-C). - -## The staff of our example institute falls into two groups of users: -## gnome-users and kde-users. -## The gnome-users log into server-A or server-B, depending on their client -## subnet (IP configuration of the client). -## The kde-users login to server-C (server-C can be reached from the whole -## intranet). -## -## The client IP based split-up of the GNOME users allows some primitive load -## balancing. -## -## If staff people are members of both groups (kde-users, gnome-users) both -## session profiles will be shown in X2Go Client. -## - -#[pool-A-server-A] -#user= -#host=server-a.pool-a.domain.local -#name=GNOME - pool-A (srv-A) -#command=GNOME -#rootless=false -#acl-groups-allow=gnome-users,admins -#acl-groups-deny=ALL -#acl-clients-deny=ALL -#acl-clients-allow=10.1.0.0/16 -#acl-any-order=deny-allow -#broker-session-autologin=true - -#[pool-A-server-B] -#user= -#host=server-b.pool-a.domain.local -#name=GNOME - pool-A (srv-B) -#command=GNOME -#rootless=false -#acl-groups-allow=gnome-users,admins -#acl-groups-deny=ALL -#acl-clients-deny=ALL -#acl-clients-allow=10.2.0.0/16 -#acl-any-order=deny-allow -#broker-session-autologin=true - -#[pool-A-server-C] -#user= -#host=server-c.pool-a.domain.local -#name=KDE - pool-A (srv-C) -#command=KDE -#rootless=false -#acl-groups-allow=kde-users,admins -#acl-groups-deny=ALL -#acl-any-order=deny-allow -#broker-session-autologin=true - -## -## EXAMPLE: pool-B (e.g. webserver in the DMZ or on the internet) -## -## The pool-B is a single X2Go Server (server-D) that is -## hosted externally. The server-D has an official internet IP. -## -## The session profile for server-D shall be provided to the -## admins group only. -## -## Furthermore, the session profile for server-D shall only get -## offered to a member of the admins group if the admin is sitting -## in front of one of the admin client machines. -## - -#[pool-B-server-D-LXDE] -#user= -#host=server-d (server-d.domain.internet) -#name=LXDE - srv-D -#command=LXDE -#rootless=false -#acl-groups-allow=admins -#acl-groups-deny=ALL -## make sure hostnames in client ACLs are resolvable via libnss!!! -#acl-clients-deny=ALL -#acl-clients-allow=admin-machine1.domain.local, admin-machine2.domain.local, admin-machine3.domain.local -#acl-any-order=deny-allow - -## -## EXAMPLE: pool-C (REAL LOAD BALANCING!!!) -## -## The pool-C is a server pool for students. Our example institute -## knows 200-300 students and has to offer working places for -## every student. -## -## The resource limits on these servers are pretty strict, so staff members -## normally stay away from these machines, anyway. Only two test account -## get this session profile into their X2Go Clients. -## -## The pool-C contains 6 X2Go Servers that serve all students users together -## as a load balance server farm. The servers' hostnames are s-E1, s-E2, ... -## (as found in /etc/hostname). The hosts, however, are not configured in DNS -## so we give their IPs explicitly (also works for IPv6). -## -## Make sure to install x2gobroker-agent on all these 6 X2Go Servers. Also make -## sure to once run the script x2gobroker-keygen on the broker host and once -## the script x2gobroker-pubkeyauthorizer per X2Go Server. -## -## All 6 X2Go Servers have to be configured to use the PostgreSQL X2Go session -## DB backend. -## - -#[pool-C-XFCE] -#user= -#host=s-E1 (10.0.2.11),s-E2 (10.0.2.12),s-E3 (10.0.2.13),s-E4 (10.0.2.14),s-E5 (10.0.2.15) -#name=XFCE - pool-C -#command=XFCE -#rootless=false -#acl-users-allow=testuser-A,testuser-B -#acl-users-deny=ALL -#acl-groups-allow=students,admins -#acl-groups-deny=ALL -#acl-any-order=deny-allow # this server pool has a special broker setup for SSH authorized_keys -#broker-session-autologin=true -#broker-authorized-keys=/var/lib/x2gobroker/ssh/%u/authorized_keys +broker-session-autologin=true +broker-authorized-keys=/etc/ssh/authorized_keys.d/%u # --------------------------------------------------------- # --------------------------------------------------------- dpkg -l|grep x2go ii cups-x2go 3.0.1.3-0x2go1+git20160127.135+jessie.main.1 all Virtual X2Go printer for CUPS ii libnx-x11-6:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 client-side library ii libnx-xcomposite1:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 Composite extension library ii libnx-xdamage1:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 damaged region extension library ii libnx-xdmcp6:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 Display Manager Control Protocol library ii libnx-xext6:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 miscellaneous extension library ii libnx-xfixes3:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 miscellaneous 'fixes' extension library ii libnx-xinerama1:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 Xinerama extension library ii libnx-xpm4:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 pixmap library ii libnx-xrandr2:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 RandR extension library ii libnx-xrender1:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 Rendering Extension client library ii libnx-xtst6:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 Testing -- Record extension library ii libxcomp3:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 compression library ii libxcompext3:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 protocol compression extensions library ii libxcompshad3:i386 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 nx-X11 shadowing library ii nx-x11-common 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 all nx-X11 (common files) ii nxagent 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 i386 NX agent ii python-x2gobroker 0.0.3.0-0x2go1+git20160126.999+jessie.main.1 all X2Go Session Broker (Python modules) ii x2go-keyring 2012.07.23~jessie~main~17~build1 all GnuPG keys of all X2Go developers and the X2Go archive ii x2goagent 2:3.5.0.32-0x2go1+git20160126.734+jessie.main.1 all X2Go agent ii x2gobroker 0.0.3.0-0x2go1+git20160126.999+jessie.main.1 all X2Go Session Broker (executable) ii x2gobroker-agent 0.0.3.0-0x2go1+git20160126.999+jessie.main.1 i386 X2Go Session Broker (remote agent) ii x2gobroker-authservice 0.0.3.0-0x2go1+git20160126.999+jessie.main.1 all X2Go Session Broker (PAM authentication service) ii x2gobroker-daemon 0.0.3.0-0x2go1+git20160126.999+jessie.main.1 all X2Go Session Broker (standalone daemon) ii x2goserver 4.0.1.19-0x2go2+git20160126.1064+jessie.main.1 i386 X2Go server daemon scripts ii x2goserver-extensions 4.0.1.19-0x2go2+git20160126.1064+jessie.main.1 all X2Go server daemon scripts (extensions) ii x2goserver-printing 4.0.1.19-0x2go2+git20160126.1064+jessie.main.1 all X2Go server daemon scripts (printing) ii x2goserver-xsession 4.0.1.19-0x2go2+git20160126.1064+jessie.main.1 all X2Go server daemon scripts (Xsession runner) # --------------------------------------------------------- cat /etc/apt/sources.list # Security Updates deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free # Backports deb http://ftp.debian.org/debian/ jessie-backports main contrib non-free # ClamAV etc. deb http://ftp.debian.org/debian jessie-updates main contrib non-free deb-src http://ftp.debian.org/debian jessie-updates main contrib non-free # Stable deb http://ftp.de.debian.org/debian/ jessie main contrib non-free deb-src http://ftp.de.debian.org/debian/ jessie main contrib non-free # X2go Repository deb http://packages.x2go.org/debian jessie main # X2go Repository (sources) deb-src http://packages.x2go.org/debian jessie main # --------------------------------------------------------- # --------------------------------------------------------- cat /etc/debian_version 8.3 # --------------------------------------------------------- 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

3 10

Bug#1012: Session reconnect doesn't work (x2gobroker)
by Miguel Quero 07 Sep '18

07 Sep '18

I can confirm this bug, but the problem is not with all x2gobroker, the resume problem become when you use ssh broker. In my setup, when client connect with --broker-url=https://XXXX.XXXX.XXXX:8080/plain/inifile, all work fine and resume is working. But when same clients connect with same credentials to the same broker with x2goclient --broker-url=ssh://XXXX.XXXX.XXXX/usr/bin/x2gobroker --broker-autologin, all work fine but resume is not working, all connection open a new session :S. I cant debug with ssh broker :(. Any ideas? -- Miguel Quero | One eSecurity | www.one-esecurity.com M: +34 608 36 17 05 Europe (Spain): +34 911 011 000 PGP: 0x34AA 050B D15C 7593 5671 3748 40C6 8E95 6C5A 40D3

3 3

Bug#1280: Windows x2goclient 4.1.x crashes with Try Auto Login
by Ross Mohn 15 Aug '18

15 Aug '18

Package: x2goclient (Windows) Version: 4.1.x Reproduced with x2goclient-4.1.0.0-2017.03.11-setup.exe and x2goclient-4.1.1.1-2018.03.01-setup.exe Noticed this about a year ago, but didn't debug at that time and just fell back to 4.0.x version. Setup: pagent.exe running with correct id_rsa.ppk SSH key. Check the "Try auto login" box in the session preferences. Launch x2goclient.debug.exe (v4.1.1.1): x2go-INFO-1> "Starting X2Go Client..." x2go-WARNING-1> "English language requested, not loading translator." x2go-WARNING-1> "English language requested, not loading translator." x2go-INFO-3> "Started X2Go Client." Process Explorer shows the following processes started, roughly in this order: x2goclient.debug.exe x2gohelper.exe sshd.exe pulseaudio.exe conhost.exe Click to launch the Session: x2go-INFO-8> "Starting connection to server: example.com:922" QObject::killTimers: timers cannot be stopped from another thread Process Explorer shows the following processes killed, roughly all at once: x2goclient.debug.exe x2gohelper.exe sshd.exe pulseaudio.exe conhost.exe Work arounds: 1) roll back to v4.0.x 2) uncheck the "Try auto login" box" and live with typing in your password. Thanks -Ross -- Ross Palmer Mohn rpmohn(a)waxandwane.org

2 1

Bug#1034: Fix a segfault in x2goclient with OpenBSD
by Denis Fondras 26 May '18

26 May '18

Event better patch from Jeremie on OpenBSD mailing-list : https://marc.info/?l=openbsd-ports&m=146327448112980&w=2

2 1

Bug#1226: x2goclient for Mac OS immediately throws error regarding "PulseAudio verison number" then crashes
by Sean Hooten 26 May '18

26 May '18

Package: X2GoClient_latest_macosx_10_9 Version: 4.1.0.0 Steps taken to produce the bug: Ran x2goclient.app, immediately get error upon initialization. Exact error message: > Error fetching PulseAudio version number! Unexpected format encountered. Expected: I expected x2goclient to initialize normally without an error message. What actually happened: x2goclient shows me the regular user interface with the pop-up error message. After selecting "Okay" it crashes. This was not an issue before, seemingly began happening spontaneously. I have attempted to reboot my machine, and reinstalled x2goclient and XQuartz to no avail. I have attached the full bug report. I'm not sure why it is attempting to fetch a PulseAudio version number, this is not on my machine and I had not yet attempted to connect to my server before receiving the error. OS: Mac OS X 10.11.6 Thanks! Sean

4 14

Bug#1253: ssh broker : bad error feedback in interaction mode
by Walid MOGHRABI 15 May '18

15 May '18

package: x2gobroker-ssh version: 0.0.4.0-0~972~ubuntu16.04.1 priority: bug Using the ssh broker is great because it adds the ability for the x2goclient to interact with the auth mechanism such as PAM so that you get notified that you need to renew a password for example. This is great but it doesn't always work well. For example, the user don't get the reason why the access is denied. Here are different tests I made based on the following setup : x2gobroker in ssh mode with local PAM auth based on Samba Winbind/Kerberos. I tried both situations to compare : * with the x2goclient in broker-ssh mode * with a term rying to connect through SSH 1) Account set for password change with temporary password in Active Directory, user type wrong password (neither old or new one) * with x2goclient: get message "Access denied. Authentication that can continue: publickey,password,keyboard-interactive" * with term : "Your account has been locked. Please contact your System administrator. Password: " 2) Account set for password change with temporary password in Active Directory, user type good password * with x2goclient: get a new password form in order to type (and confirm) the new password. Reseting password works and you get logged in to the broker with the sessions list displayed. However, if you click on the "cancel" button, x2goclient freeze and must be killed, you're not sent back to the login form. On the other hand, if you change your password and then be logged in, clicking on the session slot fails because this is the old password that is relayed to the session slot and not the new one. When it fails, you get a new login form to enter your password again, if you type the new password there, it works. * with term: "Password: ******" "Password expired. You must change it now." "Enter new password: ******" "Enter it again: ******" If you cancel (ctrl+c), nothing happen and you get back to the prompt. If you enter the good old password, you're prompted to change it then you're logged in. If you enter the wrong password, your prompted to retry 2 times then you get this message "Your account has been locked. Please contact your System administrator" (this is our security policy, this is normal behaviour, 2 fauils then blocked for 10mn. 3) Account disabled in Active Directory * with x2goclient: get message "Access denied. Authentication that can continue: publickey,password,keyboard-interactive" * with term : "Your account has been locked. Please contact your System administrator. Password: " Would be great to fix the issues in 2) and would be great to retrieve the error message directly from PAM so that we get the reason. Regards, Walid Moghrabi TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3 --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

3 2

Bug#1252: ssh broker : load balancing not working
by Walid MOGHRABI 15 May '18

15 May '18

package: x2gobroker-ssh version: 0.0.4.0-0~972~ubuntu16.04.1 priority: bug Hi, Tried using x2gobroker-ssh (0.0.4.0-0~972~ubuntu16.04.1) instead of classical http broker and finaly got it working but in ssh mode, load balancing on my server farm is not working, every session is redirected to the same server (the first one) while it is balanced correctly with the http broker on the same broker server. I would love to send logs but it seems this broker don't produce log files or I couldn't find a way to get them. Regards, Walid Moghrabi TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3 --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

3 2

Bug#1291: FW: Flickering when maximised in Windows
by Poppe Koen 09 May '18

09 May '18

Package: x2goclient Version: 4.1.1.1 1. Start a session => The image is stable 2. Maximise the window => The image is flickering and the remote os seems to be switching back and forth between two slightly different sizes. The effect is independent of the window size: maximised on a smaller monitor exhibits the same behaviour. On the server, "session.log" is spammed (about 3x per second) with the following (monitor resolution: 1920x1200) Info: Screen [0] resized to geometry [1920x1181] fullscreen [0]. Info: Screen [0] resized to geometry [1920x1181] fullscreen [0]. Info: Screen [0] resized to geometry [1920x1181] fullscreen [0]. ... Client: - OS: Windows 7 SP1 64-bit (Windows classic theme) - x2goclient: 4.1.1.1 Server: - OS: Ubuntu 14.04 32-bit - x2goserver: 4.1.0.0 - x2goserver-common: 4.1.0.0 - x2goserver-extensions: 4.1.0.0 - x2goserver-fmbindings: 4.1.0.0 - x2goserver-printing: 4.1.0.0 - x2goserver-x2goagent: 3.5.99.16 - x2goserver-xsession: 4.1.0.0 - nxagent: 3.5.99.16 _____________ Mail Disclaimer<http://www.vandewiele.com/legal#/mail-disclaimer-en>

2 1

Bug#1292: Windows client crashes in QObject::killTimers trying to connect with Pageant
by x2go user 30 Apr '18

30 Apr '18

Package: x2goclient Version: 4.1.1.1 When trying to connect with auto-login using Pageant on Windows, the client starts to connect and then crashes. The crash happens before anything shows in the event log UI; the debug log is below. It seems like the relevant log line is: QObject::killTimers: timers cannot be stopped from another thread It does not crash using normal password auth or public key auth with a private key file. It crashes with both the included 32-bit pageant and the 64-bit pageant from the PuTTY distribution. PuTTY connects fine using the same pageant and host. This client is Windows 10 version 1703 (build 15063.1029) 64-bit. The server is RedHat 7.3 64-bit, OpenSSH_6.6.1p1, OpenSSL 1.0.1e-fips 11 Feb 2013 Server versions: x2goagent: 3.5.0.32 x2goserver: 4.0.1.20 x2goserver-extensions: 4.0.1.20 x2goserver-xsession: 4.0.1.20 -------------------------------------- debug log -------------------------------------- x2go-INFO-1> "Starting X2Go Client 4.1.1.1..." x2go-WARNING-1> English language requested, not loading translator. x2go-WARNING-1> English language requested, not loading translator. x2go-DEBUG-../src/onmainwindow.cpp:1380> Removing apps from tray x2go-DEBUG-../src/onmainwindow.cpp:1348> Plugging apps in tray. x2go-DEBUG-../src/onmainwindow.cpp:10589> Getting X.Org Server settings. x2go-INFO-3> "Started X2Go Client." x2go-DEBUG-../src/onmainwindow.cpp:583> "$HOME=C:/Users/user" x2go-DEBUG-../src/onmainwindow.cpp:2420> Reading 2 sessions from config file. x2go-DEBUG-../src/sessionbutton.cpp:342> Creating QPixmap with session icon: ":/img/icons/128x128/x2gosession.png". x2go-DEBUG-../src/sessionbutton.cpp:342> Creating QPixmap with session icon: ":/img/icons/128x128/x2gosession.png". x2go-DEBUG-../src/onmainwindow.cpp:13086> libssh not initialized yet. Initializing. x2go-DEBUG-../src/onmainwindow.cpp:6934> Not starting PulseAudio x2go-DEBUG-../src/onmainwindow.cpp:10492> Starting helper servers for Windows ... x2go-DEBUG-../src/onmainwindow.cpp:10659> "/cygdrive/C/Users/user/.x2go/var" cygwin var path x2go-DEBUG-../src/onmainwindow.cpp:10742> "C:/Users/user/.x2go/etc/sshd_config created." x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/onmainwindow.cpp:10274> Port is free: 7022 x2go-DEBUG-../src/onmainwindow.cpp:11092> Logging cygwin sshd to: "C:/Users/user/.x2go/sshLogs/Hp1108.log" x2go-DEBUG-../src/onmainwindow.cpp:11106> Creating desktop: x2go_user x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/onmainwindow.cpp:10280> Port already in use: 7022 x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/onmainwindow.cpp:10280> Port already in use: 7022 x2go-DEBUG-../src/onmainwindow.cpp:11203> User mode OpenSSH server started successfully. x2go-DEBUG-../src/onmainwindow.cpp:2906> Creating QPixmap with session icon: '":/img/icons/128x128/x2gosession.png"'. x2go-DEBUG-../src/onmainwindow.cpp:2973> Starting session via Smart Card, SSH Agent or Kerberos token. x2go-DEBUG-../src/onmainwindow.cpp:1380> Removing apps from tray x2go-INFO-8> "Starting connection to server: 10.0.0.67:22" x2go-DEBUG-../src/onmainwindow.cpp:3007> Starting new ssh connection to server:"10.0.0.67":"22" krbLogin: false x2go-DEBUG-../src/sshmasterconnection.cpp:175> SshMasterConnection, host "10.0.0.67"; port 22; user "user"; useproxy false; proxyserver ""; proxyport 22 x2go-DEBUG-../src/sshmasterconnection.cpp:248> Starting SSH connection without Kerberos authentication. x2go-DEBUG-../src/sshmasterconnection.cpp:252> SshMasterConnection, instance SshMasterConnection(0x3c131f8) created. x2go-DEBUG-../src/sshmasterconnection.cpp:520> SshMasterConnection, instance SshMasterConnection(0x3c131f8) entering thread. x2go-DEBUG-../src/sshmasterconnection.cpp:592> Setting SSH directory to C:/Users/user/ssh x2go-DEBUG-../src/sshmasterconnection.cpp:840> Session port before config file parse: 22 x2go-DEBUG-../src/sshmasterconnection.cpp:850> Session port after config file parse: 22 x2go-DEBUG-../src/sshmasterconnection.cpp:915> Session port before config file parse (part 2): 22 x2go-DEBUG-../src/sshmasterconnection.cpp:925> Session port after config file parse (part 2): 22 x2go-DEBUG-../src/sshmasterconnection.cpp:950> cserverAuth x2go-DEBUG-../src/sshmasterconnection.cpp:991> state: 1 x2go-DEBUG-../src/sshmasterconnection.cpp:711> Setting SSH directory to C:/Users/user/ssh QObject::killTimers: timers cannot be stopped from another thread ------------------------------------------- sshd log ------------------------------------------- debug1: Bind to port 7022 on ::. Server listening on :: port 7022. debug1: Bind to port 7022 on 0.0.0.0. Server listening on 0.0.0.0 port 7022. debug1: fd 6 clearing O_NONBLOCK debug1: Forked child 4216. debug1: rexec start in 6 out 6 newsock 6 pipe 8 sock 9 debug1: fd 6 clearing O_NONBLOCK debug1: Forked child 1832. debug1: rexec start in 6 out 6 newsock 6 pipe 9 sock 10 debug1: inetd sockets after dupping: 5, 5 Connection from 127.0.0.1 port 62967 on 127.0.0.1 port 7022 Did not receive identification string from 127.0.0.1 debug1: inetd sockets after dupping: 5, 5 Connection from 127.0.0.1 port 62968 on 127.0.0.1 port 7022 Did not receive identification string from 127.0.0.1

1 0

Bug#1215: has the same issue - after last update of x2go components on the ubuntu server!
by Tarnin, Gai (Gai) 30 Apr '18

30 Apr '18

Gai Tarnin | R&D Endpoints | Avaya | HOLON, ISRAEL | +972(0)36457556 | gtarnin(a)avaya.com<mailto:gtarnin@avaya.com> | www.avaya.com<http://www.avaya.com/> [A Connection Built To Last]<https://www.avaya.com/en/connectwithavaya> [Facebook]<https://www.facebook.com/avaya> [Twitter]<https://twitter.com/avaya> [Linked In]<https://www.linkedin.com/company/avaya/> [YouTube]<https://www.instagram.com/avayainc/> [Google+]<https://plus.google.com/+avaya> [YouTube]<https://www.youtube.com/avaya> [http://avaya.netlabs.net/emt/email_sig2018/images/social7.jpg]<https://www.avaya.com/connect>

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev April 2018