x2go-user March 2018

x2go-user@lists.x2go.org

34 participants
46 discussions

x2go Windows Client: Strange Issue with Screen Update
by Michael Klemm 10 Mar '18

10 Mar '18

Dear x2go-user list, I'm having trouble with the x2go Windows client on one of my machines. It seems that it misses some screen updates (see the attached screen shot). The screen was made after a I typed "ls" a few times. After I reconnect the session, the screen is updated properly once and then subsequent updates are missing again. This is on Windows 10 Pro (version 1709) and x2go client 4.1.1.1 (nightly build 2017-11-14). The error also happens with the 4.1.0 client. The server is a CentOS 7.4 box with x2goserver-4.0.1.20-1.el7.x86_64, the desktop is KDE. The same client version works perfectly on another Windows machine, so I doubt that the server or KDE is the culprit. If someone could provide me with a hint how to debug this issue to create a bug report, I'd appreciate it. Thanks! Kind regards, -michael

1 1

x2go problems
by Steven Spencer 08 Mar '18

08 Mar '18

Greetings, We use x2go extensively for some access to some Ubuntu based LTSP servers. Suddenly over the last two days, we get the following in the client: "The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server." And on the server we are trying to connect to, we see this in the logs: /usr/bin/x2goresume-session: client [ip.address.of.client] has successfully resumed session with ID kscadmin-51-1520534328_stDMATE_dp24 /usr/bin/x2gosetkeyboard: /home/ksca0dmin/.x2go/C-kscadmin-51-1520534328_stDMATE_dp24/keyboard did not appear within 30s after agent startup We are never able to connect. This happens even on all servers that we connect to and includes older server versions: x2goagent: 3.5.0.33 x2goserver: 4.0.1.22 x2goserver-extensions: 4.0.1.22 x2goserver-xsession: 4.0.1.22 As well as newer ones: 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.14 x2goserver-xsession: 4.1.0.0 Unfortunately, the clients are now updated as well trying to fix this issue, but they were failing on the older client version as well: X2Go Client v. 4.1.1.1 (Qt - 4.8.7) Any help would be appreciated. Thanks, -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 1131 Mobile 402-765-8010

1 0

x2go server closes the inactive connection and not possible to connect again
by Pongrácz István 07 Mar '18

07 Mar '18

Hi, I use x2go successfully for several years and I very like it, thank you! I have a problem with the latest x2go (http://ppa.launchpad.net/x2go/st able/ubuntu xenial main). I can login without problem to the server, working as expected, but when I do not work on the x2go session (inactive or idle), the server closes the connection and it is not possible to connect again. Before the upgrade I had open sessions for days. Any idea? Below the technical details. The client debug shows (short version): x2go-DEBUG-../src/sshmasterconnection.cpp:2089> Forwarding parameters: from remote ("localhost":49454) to local ("localhost":49788) x2go-DEBUG-../src/sshmasterconnection.cpp:2126> Temporary session port after config file parse: 49454 x2go-DEBUG-../src/sshmasterconnection.cpp:2130> Temporary session host after config file parse: localhost x2go-DEBUG-../src/sshmasterconnection.cpp:2160> New channel forwarded. x2go-DEBUG-../src/sshmasterconnection.cpp:2320> "ssh_channel_write failed": "Remote channel is closed" x2go-DEBUG-../src/sshprocess.cpp:472> I/O error: "ssh_channel_write failed."" - Remote channel is closed" (2). x2go-DEBUG-../src/sshmasterconnection.cpp:2363> EOF sent. x2go-DEBUG-../src/sshmasterconnection.cpp:2367> Channel closed. x2go-DEBUG-../src/onmainwindow.cpp:6459> Proxy wrote on stderr: "Loop: PANIC! The remote NX proxy closed the connection. Error: The remote NX proxy closed the connection. " x2go-DEBUG-../src/onmainwindow.cpp:6459> Proxy wrote on stderr: "Loop: PANIC! Failure negotiating the session in stage '7'. Error: Failure negotiating the session in stage '7'. Loop: PANIC! Wrong version or invalid session authentication cookie. Error: Wrong version or invalid session authentication cookie. So, on the server side the port 49454 did not exist and even on the server I can see the session running (with ps ax), it is not possible to connect (The remote NX proxy closed the connection....)) I did not find fresh or relevant information on the net, I spent about 2 days to figure out, but without success (purge, reinstall, xsession removing etc. - all done, without results) On the server, the sshd log contains this relevant information (it is the pair of the client debug log above): Mar 5 19:45:11 localhost sshd[19999]: Accepted publickey for xxxx from YYYYY.98 port 43002 ssh2: RSA SHA256:notrelevant Mar 5 19:45:11 localhost sshd[19999]: pam_unix(sshd:session): session opened for user username by (uid=0) Mar 5 19:45:11 localhost systemd-logind[787]: New session 9 of user username. Mar 5 19:45:22 localhost su[20438]: Successful su for username by root Mar 5 19:45:22 localhost su[20438]: + ??? root:username Mar 5 19:45:22 localhost su[20438]: pam_unix(su:session): session opened for user username by (uid=0) Mar 5 19:45:22 localhost systemd-logind[787]: New session c1 of user username. Mar 5 19:45:22 localhost su[20438]: pam_unix(su:session): session closed for user username Mar 5 19:45:22 localhost su[20492]: Successful su for username by root Mar 5 19:45:22 localhost systemd-logind[787]: Removed session c1. Mar 5 19:45:22 localhost su[20492]: + ??? root:username Mar 5 19:45:22 localhost su[20492]: pam_unix(su:session): session opened for user username by (uid=0) Mar 5 19:45:22 localhost systemd-logind[787]: New session c2 of user username. Mar 5 19:45:24 localhost su[20492]: pam_unix(su:session): session closed for user username Mar 5 19:45:24 localhost systemd-logind[787]: Removed session c2. Mar 5 19:45:25 localhost sshd[3615]: pam_unix(sshd:session): session closed for user username Mar 5 19:45:29 localhost sshd[20011]: error: connect_to localhost port 49454: failed. Mar 5 19:45:29 localhost sshd[20011]: channel_by_id: 0: bad id: channel free Mar 5 19:45:29 localhost sshd[20011]: Disconnecting: Received ieof for nonexistent channel 0. Mar 5 19:45:29 localhost sshd[19999]: pam_unix(sshd:session): session closed for user username Mar 5 19:45:29 localhost systemd-logind[787]: Removed session 9. The x2go server log from the syslog: Here is the session opened first time, successfully, you can see the agent port (49454): Mar 5 18:31:11 localhost /usr/bin/x2gostartagent: creating new session: username-50-1520271069_stDMATE_dp24 2a3a4f78ebac6c1318558ebfebbffff1 3799 YYYY.98 49454 49455 49456 -1 -1 In the syslog I did not find any related information about nxagent closing, but only the unsuccessful reconnect after 1 hour and 14 minutes. First reconnect, I was able to see the session selector window and I saw the session as running state, but I had only Suspend and Terminate buttons active. I pushed the suspend and resume, problem occurred. Here are the packages on the server: ii cups-x2go 3.0.1.3- 1 all Virtual X2Go printer for CUPS ii libx2go-log-perl 4.1.0.0- 0~1517~ubuntu16.04.1 all Perl X2Go::Log package ii libx2go-server-db-perl 4.1.0.0- 0~1517~ubuntu16.04.1 i386 Perl X2Go::Server:DB package ii libx2go-server-perl 4.1.0.0- 0~1517~ubuntu16.04.1 all Perl X2Go::Server package rc x2goagent 2:3.5.0.33- 0~710~ubuntu16.04.1 all X2Go agent rc x2godesktopsharing 3.1.1.4- 0~186~ubuntu16.04.1 i386 Share X11 desktops with other users via X2Go ii x2gomatebindings 0.0.1.5- 0~203~ubuntu16.04.1 i386 X2Go MATE bindings and MIME types ii x2goserver 4.1.0.0- 0~1517~ubuntu16.04.1 i386 X2Go server daemon scripts ii x2goserver-common 4.1.0.0- 0~1517~ubuntu16.04.1 i386 X2Go Server (common files) ii x2goserver-extensions 4.1.0.0- 0~1517~ubuntu16.04.1 all X2Go Server (extension support) ii x2goserver-printing 4.1.0.0- 0~1517~ubuntu16.04.1 all X2Go server (printing support) ii x2goserver-x2goagent 4.1.0.0- 0~1517~ubuntu16.04.1 all X2Go Server's X2Go Agent rc x2goserver-xsession 4.1.0.0- 0~1517~ubuntu16.04.1 all X2Go Server (Xsession runner) Here are the packages on the client: ii cups- x2go 3.0.1.3- 1 all Virtual X2Go printer for CUPS rc x2goagent 2:3.5.0 .33-0~710~ubuntu16.04.1 all X2Go agent ii x2goclient 4.1.1.1 -0~1719~ubuntu16.04.1 amd64 X2Go Client application (Qt4) rc x2gomatebindings 0.0.1.5 -0~203~ubuntu16.04.1 amd64 X2Go MATE bindings and MIME types rc x2goserver 4.0.1.2 2-0~1197~ubuntu16.04.1 amd64 X2Go server daemon scripts rc x2goserver- printing 4.0.1.22- 0~1197~ubuntu16.04.1 all X2Go server daemon scripts (printing) rc x2goserver- xsession 4.0.1.22- 0~1197~ubuntu16.04.1 all X2Go server daemon scripts (Xsession runner) ii x2gousbmount 1.1.0.2 -0~469~ubuntu16.04.1 all clientside usb mass-storage device mounting

3 5

SSH error with pyhoca-gui
by Michael Eager 06 Mar '18

06 Mar '18

I'm seeing a message saying "SSH Error" with pyhoca-gui when connecting to a CentOS 7 server. The message in /var/log/secure on the server is Connection closed by 192.168.20.12 port 36098 [preauth] I can log in to the server using SSH, and I am able to connect using pyhoca-cli and x2goclient. The profile specifies a shared id_rsa key. On the server: x2goserver-4.0.1.20-1.el7.x86_64 On the client: x2goclient-4.1.1.0-1.fc27.x86_64 python2-x2go-0.5.0.5-2.fc27.noarch pyhoca-gui-0.5.0.6-4.fc27.noarch pyhoca-cli-0.5.0.3-5.fc27.noarch How can I tell what pyhoca-gui is doing differently/incorrectly? -- Michael Eager eager(a)eagerm.com

1 0

X2Go Client: Startup of VcXsrv sometimes fails
by Schmid Andreas 06 Mar '18

06 Mar '18

Hi, I'm running X2Go Client 4.1.0.0 on Windows Server 2012 R2 for connecting to X2Go Server 4.0.1.22 on Ubuntu 14.04. This usually works flawlessly. Since about 4 months ago, however, X2Go Client *sometimes* fails to fully establish the session. (Sometimes means that it happens quite unregularly; which makes it hard to reproduce. But when it happens, it can last from 5 minutes up to around 30 minutes until connections are successful again.) In these cases X2Go Client actually connects to the server, but the startup of VcXsrv fails, so X2Go Client subsequently terminates the connection. I attached the log output of VcXsrv below. I suspect that in the cases when the connection fails to fully establish, VcXsrv for some reason doesn't manage to find a free display number. Maybe this is due to the fact that on the Windows server several users are logged in simultaneously and use X2Go Client. Another guess is that VcXsrv might not like the fact that the Windows server has two IPv4 addresses. Does anyone have a clue what could be the reason for it? Or where I could find further information on these error messages? Thank you for any hint. On the client side, the following is logged in C:\Users\<username>\AppData\Local\Temp\VCXSrv.0.log when the connection fails: -- Welcome to the VcXsrv X Server Vendor: The X2Go and Arctica Projects Release: 1.17.0.0 OS: Windows NT 6.2 build 9200 (WoW64) Contact: https://github.com/ArcticaProject/vcxsrv _XSERVTransSocketCreateListener: failed to bind listener _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: failed to create listener for inet DefineSelf - d16s003 has IPv6 addresses... ::1 LoadPreferences: C:\Users\<username>\AppData\Roaming/.XWinrc not found LoadPreferences: Loading P:\X2Go\V4_1_0_0\x2goclient\vcxsrv\system.XWinrc Warning: Locale not supported by X, falling back to 'C' locale. wglwrap: Can't resolve "wglGetExtensionsStringARB" (EE) AIGLX: Won't use generic native renderer as it is not accelerated (II) AIGLX: Loaded and initialized swrast (II) GLX: Initialized DRISWRAST GL provider for screen 0 winBlockHandler - pthread_mutex_unlock() winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5 winInitMultiWindowWM - Could not open display, try: 2, sleeping: 5 winInitMultiWindowWM - Could not open display, try: 3, sleeping: 5 winInitMultiWindowWM - Could not open display, try: 4, sleeping: 5 winInitMultiWindowWM - Could not open display, try: 5, sleeping: 5 winInitMultiWindowWM - Failed opening the display. Exiting. (EE) Server terminated with error (1). Closing log file. -- In the case of successful connection, the log output looks like: -- Welcome to the VcXsrv X Server Vendor: The X2Go and Arctica Projects Release: 1.17.0.0 OS: Windows NT 6.2 build 9200 (WoW64) Contact: https://github.com/ArcticaProject/vcxsrv DefineSelf - d16s003 has 2 usable IPv4 interfaces... addresses 10.36.2.103 10.36.18.106 DefineSelf - d16s003 has IPv6 addresses... ::1 LoadPreferences: C:\Users\<uername>\AppData\Roaming/.XWinrc not found LoadPreferences: Loading P:\X2Go\V4_1_0_0\x2goclient\vcxsrv\system.XWinrc Warning: Locale not supported by X, falling back to 'C' locale. wglwrap: Can't resolve "wglGetExtensionsStringARB" (EE) AIGLX: Won't use generic native renderer as it is not accelerated (II) AIGLX: Loaded and initialized swrast (II) GLX: Initialized DRISWRAST GL provider for screen 0 winBlockHandler - pthread_mutex_unlock() winClipboardThreadProc - DISPLAY=127.0.0.1:0.0 -- When I just start vcxsrv.exe, I'm getting the same messages. At times when connections fail: -- Welcome to the VcXsrv X Server Vendor: The X2Go and Arctica Projects Release: 1.17.0.0 OS: Windows NT 6.2 build 9200 (WoW64) Contact: https://github.com/ArcticaProject/vcxsrv _XSERVTransSocketCreateListener: failed to bind listener _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: failed to create listener for inet DefineSelf - d16s003 has IPv6 addresses... ::1 LoadPreferences: C:\Users\<username>\AppData\Roaming/.XWinrc not found LoadPreferences: Loading P:\X2Go\V4_1_0_0\x2goclient\VcXsrv\system.XWinrc Warning: Locale not supported by X, falling back to 'C' locale. (EE) AIGLX: No native OpenGL in modes with a root window (II) AIGLX: Loaded and initialized swrast (II) GLX: Initialized DRISWRAST GL provider for screen 0 winBlockHandler - pthread_mutex_unlock() -- At times when connections work: -- Welcome to the VcXsrv X Server Vendor: The X2Go and Arctica Projects Release: 1.17.0.0 OS: Windows NT 6.2 build 9200 (WoW64) Contact: https://github.com/ArcticaProject/vcxsrv DefineSelf - d16s003 has 2 usable IPv4 interfaces... addresses 10.36.2.103 10.36.18.106 DefineSelf - d16s003 has IPv6 addresses... ::1 LoadPreferences: C:\Users\<username>\AppData\Roaming/.XWinrc not found LoadPreferences: Loading P:\X2Go\V4_1_0_0\x2goclient\VcXsrv\system.XWinrc Warning: Locale not supported by X, falling back to 'C' locale. (EE) AIGLX: No native OpenGL in modes with a root window (II) AIGLX: Loaded and initialized swrast (II) GLX: Initialized DRISWRAST GL provider for screen 0 winBlockHandler - pthread_mutex_unlock() -- Best, Andy

1 0

Ldap auth fails
by martti pitkanen 05 Mar '18

05 Mar '18

Hi, After most recent update, PAM Ldap authentication fails, client claims "Wrong credentials" However, auth_log shows that X2Go login was successful (lower), as well as cmd line remote login (upper) instance. Mar 5 13:51:17 localhost su[30229]: Successful su for ratoansa by root Mar 5 13:51:17 localhost su[30229]: + ??? root:ratoansa Mar 5 13:51:17 localhost su[30229]: pam_unix(su:session): session opened for user ratoansa by (uid=0) Mar 5 13:51:17 localhost systemd-logind[826]: New session c49 of user ratoansa. Mar 5 13:51:17 localhost su[30229]: pam_unix(su:session): session closed for user ratoansa Mar 5 13:51:17 localhost systemd-logind[826]: Removed session c49. Mar 5 13:51:17 localhost su[30248]: Successful su for ratoansa by root Mar 5 13:51:17 localhost su[30248]: + ??? root:ratoansa Mar 5 13:51:17 localhost su[30248]: pam_unix(su:session): session opened for user ratoansa by (uid=0) Mar 5 13:51:17 localhost systemd-logind[826]: New session c50 of user ratoansa. Mar 5 13:51:18 localhost su[30248]: pam_unix(su:session): session closed for user ratoansa Mar 5 13:51:18 localhost systemd-logind[826]: Removed session c50. Ma -- --- Martti Pitkänen APLcomp Oy Mariankatu 17 00170 Helsinki Finland Tel +358 9 1357266 Mob +358 40 0602157 www.aplcomp.com Mail: P.O.BOX 126 00171 Helsinki Finland

1 0

LinuxMint 18.3 upgrade fails
by martti pitkanen 03 Mar '18

03 Mar '18

Hi, -After the most resent update: x2goagent : Depends: nxagent (< 2:3.5.0.33-0~710~ubuntu16.04.1.1) -however, nxagent is already the newest version (2:3.5.99.14-0~816~ubuntu16.04.1). -- --- Martti Pitkänen APLcomp Oy Mariankatu 17 00170 Helsinki Finland Tel +358 9 1357266 Mob +358 40 0602157 www.aplcomp.com Mail: P.O.BOX 126 00171 Helsinki Finland

7 44

More Details on Wedgeing
by Robert Dinse 03 Mar '18

03 Mar '18

I have discovered that, when the session disconnects abruptly and I go to reconnect, if I choose to terminate the session instead of trying to reconnect to it, then x2goserver does not wedge. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

1 0

SSH
by Robert Dinse 02 Mar '18

02 Mar '18

Looks like my ssh is hurt: [256092.528160] SshMasterConnec[4630]: segfault at dd ip 00007fc61a459eec sp 00007fc5ee2b8928 error 4 in libssh.so.4.4.2[7fc61a433000+6d000] [256163.639990] SshMasterConnec[5083]: segfault at dd ip 00007fa0a3453eec sp 00007fa0772ee928 error 4 in libssh.so.4.4.2[7fa0a342d000+6d000] This might be my issue rather than x2go, but it never happens when I do a straight ssh session. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

1 1

Mint now Ubuntu
by Robert Dinse 02 Mar '18

02 Mar '18

I updated a Ubuntu system with nightly builds and now it is doing the same as Mint but only if I login as root. If I login with a normal UID it does not. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user March 2018