x2go-dev May 2018

x2go-dev@lists.x2go.org

16 participants
107 discussions

Bug#1295: x2goclient/broker mode : don't close on suspended session with --close-disconnect
by Walid MOGHRABI 15 May '18

15 May '18

package: x2goclient version: 4.1.2.0-0~1750~ubuntu16.04.1 priority: bug In broker/tce mode, when I connect a new session on TCE-CLIENT-1, if I live migrate the running session on TCE-CLIENT-2, the session is detached from client 1 to client 2 correctly (suspended on client 1 and correctly resumed on client 2) but x2goclient doesn't close itself on client 1 once session is detached. The client stays opened on the sessions profiles list with the currently logged in user instead of closing itself and getting back to the broker login prompt. This is a major security issue since anyone can then just click on a session profile to connect with the current user credentials. 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

2 1

Bug#1299: Improve user experience for "Display" selection in the Input/Output tab
by Stefan Baur 14 May '18

14 May '18

package: x2goclient priority: wishlist X2GoClient 4.1.1.1 introduced that the option "Whole Display" in the "Display" section of the Input/Output tab is hidden when only one screen is connected. IMO, this isn't ideal, because a user that only uses a second screen from time to time has no chance of finding out that they can limit an X2Go "fullscreen" session to a single screen (without showing window decorations on the X2Go window). This is why I suggest that instead of hiding, the option should be greyed out. Also, the average user has no clue that there is a difference between a screen and a display (in X-terminology). Therefore, I suggest renaming the options, or at least adding some explanatory text: "Fullscreen" should read "Fullscreen (span all screens)" while "Whole Display" should read "Whole Display (single-screen)" or similar. I'm open to suggestions, as long as they help making things clearer to an average/newbie user. Personally, I would prefer it if "Whole Display" was selectable even in single-screen mode (along with a display number that can be entered manually), but I can understand that this is more of an expert feature and would confuse most users. 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

1 0

Bug#1297: do not look for keys when one is supplied already
by Stefan Baur 11 May '18

11 May '18

Please note that the patch submitter's eMail address is invalid. We should verify the person behind the patch before accepting it, to make sure we know the copyright holder of the patch. -Stefan -- 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

1 0

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#1156: another workaround
by Jonathan Landis 05 May '18

05 May '18

You can fix the file permissions without Cygwin, but not with File Explorer. You need to use the industrial-strength subinacl.exe tool available for free from Microsoft. It's often the only option for permissions issues, so it is useful to have around. As noted earlier in the thread, the ssh_host_rsa_key file's primary group is the same as the user. So the group permissions are the user permissions, and there is no possible way to satisfy the permissions requirements, even if you delete all permissions entries except the one for the user. So what you have to do is set the primary group to something else, and make sure that it doesn't have access to the file. Like this: "c:\Program Files (x86)\Windows Resource Kits\Tools\subinacl.exe" /file ssh_host_rsa_key /setprimarygroup=Administrators That will set the primary group to the builtin Administrators group. Make sure that group doesn't have an access grant (which can be done in File Explorer if desired).

1 0

Bug#1294: Can't reconnect to existing x2go session
by Koozer, Craig 02 May '18

02 May '18

Package: x2goagent Version: 3.5.0.33 I'm having problems reconnecting to any existing sessions on a specific x2goserver instance from any client I've tried. If I kill the existing session using x2goterminate-session and create a new one the new one connects with no problems, but if then I disconnect from it and attempt to re-connect (even from the same client), then again I get the same problem -- client does not connect, and message is displayed in client "The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server.". I believe this started happening after upgrading to latest client and server versions on the server, but downgrading the server version or clients connecting to server or both did not make the problem go away. I also tried removing ~/.x2go and ~/.x2goclient directories on client and server and allow them to be recreated, but this did not change behavior. I enabled debug from client and server, and have saved the complete log entries for /var/log/messages on server, and client out on reconnect if you think that would be helpful, but what I've included below is the only thing that looks like an error. all other config settings are as installed, no other manual changes were made. from x2goclient --debug std. out: x2go-DEBUG-../src/sshprocess.cpp:372> Starting tunnel via SshProcess object 2: "localhost":59190 -> "localhost":60190 x2go-DEBUG-../src/onmainwindow.cpp:5612> "Starting NX proxy, command: nxproxy -S nx/nx,options=/home/ckoozer/.x2go/S-ckoozer-56-1525261822_stDXFCE_dp24/options:56" x2go-DEBUG-../src/sshprocess.cpp:157> Direct tunnel: waiting for connections on "localhost":60190 x2go-DEBUG-../src/onmainwindow.cpp:6071> Proxy wrote on stderr: " NXPROXY - Version 3.5.0 Copyright (C) 2001, 2010 NoMachine. See http://www.nomachine.com/ for more information. Info: Proxy running in client mode with pid '3938'. Session: Starting session at 'Wed May 2 11:48:25 2018'. Info: Using abstract X11 socket in kernel namespace for accessing DISPLAY=:0. " x2go-DEBUG-../src/onmainwindow.cpp:6071> Proxy wrote on stderr: "Info: Connecting to remote host 'localhost:60190'. Info: Connection to remote proxy 'localhost:60190' established. " x2go-DEBUG-../src/sshprocess.cpp:109> New TCP connection. x2go-DEBUG-../src/sshprocess.cpp:114> New socket: 15 x2go-DEBUG-../src/sshmasterconnection.cpp:1517> Creating new channel. x2go-DEBUG-../src/sshmasterconnection.cpp:1521> New channel:0x7fb888015870 x2go-DEBUG-../src/sshmasterconnection.cpp:1527> Forwarding new channel, local port: 58952 x2go-DEBUG-../src/sshmasterconnection.cpp:1545> New channel forwarded. x2go-DEBUG-../src/sshmasterconnection.cpp:1704> "channel_write failed." - "Remote channel is closed" x2go-DEBUG-../src/sshprocess.cpp:463> I/O error: "channel_write failed."" - Remote channel is closed" (2). x2go-DEBUG-../src/sshmasterconnection.cpp:1747> EOF sent. x2go-DEBUG-../src/sshmasterconnection.cpp:1751> Channel closed. x2go-DEBUG-../src/onmainwindow.cpp:6071> Proxy wrote on stderr: "Error: The remote NX proxy closed the connection. " x2go-DEBUG-../src/onmainwindow.cpp:6071> Proxy wrote on stderr: "Error: Failure negotiating the session in stage '7'. Error: Wrong version or invalid session authentication cookie. Session: Terminating session at 'Wed May 2 11:48:25 2018'. Session: Session terminated at 'Wed May 2 11:48:25 2018'. " x2go-DEBUG-../src/onmainwindow.cpp:5928> Deleting Proxy. Server details: [ckoozer@ckoozer-linux ~]$ uname -a Linux ckoozer-linux 3.10.0-862.el7.x86_64 #1 SMP Wed Apr 11 11:40:58 PDT 2018 x86_64 x86_64 x86_64 GNU/Linux [ckoozer@ckoozer-linux ~]$ rpm -qa | grep nx nxagent-3.5.0.33-4.el7.x86_64 nxproxy-3.5.0.33-4.el7.x86_64 lynx-2.8.8-0.3.dev15.el7.x86_64 inx-icon-theme-0.6-2.3.noarch nx-libs-3.5.0.33-4.el7.x86_64 inxi-2.3.56-1.el7.noarch [ckoozer@ckoozer-linux ~]$ rpm -qa | grep x2go x2goserver-xsession-4.0.1.22-2.el7.x86_64 x2goagent-3.5.0.33-4.el7.x86_64 x2goclient-4.1.1.1-1.el7.x86_64 x2goserver-4.0.1.22-2.el7.x86_64 Client details (but same behavior from multiple clients and x2goclient versions, including windows client): [ckoozer@ckoozer ~]$ uname -a Linux ckoozer 4.15.16-200.fc26.x86_64 #1 SMP Mon Apr 9 17:49:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [ckoozer@ckoozer ~]$ rpm -qa | grep nx nxagent-3.5.0.33-4.fc26.x86_64 nxproxy-3.5.0.33-4.fc26.x86_64 nx-libs-3.5.0.33-4.fc26.x86_64 [ckoozer@ckoozer ~]$ rpm -qa | grep x2go x2goclient-4.1.0.0-1.fc26.x86_64 (same behavior with latest version of client as well) x2goagent-3.5.0.33-4.fc26.x86_64 x2goserver-xsession-4.0.1.22-2.fc26.x86_64 x2goserver-4.0.1.22-2.fc26.x86_64 [ckoozer@ckoozer-linux ~]$ which nxagent /usr/bin/nxagent [ckoozer@ckoozer-linux ~]$ which x2goagent /usr/bin/x2goagent [ckoozer@ckoozer-linux ~]$ locate nxagent /etc/nxagent /etc/nxagent/keystrokes.cfg /etc/nxagent/nxagent.keyboard /etc/nxagent/rgb /usr/bin/nxagent /usr/lib64/nx/bin/nxagent /usr/share/man/man1/nxagent.1.gz /usr/share/pixmaps/nxagent.xpm [ckoozer@ckoozer-linux ~]$ locate x2goagent /etc/x2go/x2goagent.keyboard /etc/x2go/x2goagent.options /usr/bin/x2goagent /usr/lib64/x2go/bin/x2goagent /usr/share/man/man1/x2goagent.1.gz /usr/share/x2go/versions/VERSION.x2goagent [ckoozer@ckoozer-linux ~]$ which nxproxy /usr/bin/nxproxy [ckoozer@ckoozer-linux ~]$ locate nxproxy /usr/bin/nxproxy /usr/lib64/nx/bin/nxproxy /usr/share/man/man1/nxproxy.1.gz [ckoozer@ckoozer-linux ~]$ nxproxy -v NXPROXY - Version 3.5.0.33 thanks! craig(a)netsuite.com<mailto:craig@netsuite.com>

1 0

Bug#1293: x2go crashes on start
by Elias Wright 02 May '18

02 May '18

Package: x2goclient-4.1.1.1-2018.03.01 Version: 4.1.1.1 On program start the program displays message, “PulseAudio failed to start”, then “Can’t start X.Org Server”. On clicking OK, program closes. Have tried uninstall and reinstall with and without admin privileges. 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:10589> Getting X.Org Server settings. x2go-INFO-3> "Started X2Go Client." x2go-DEBUG-../src/onmainwindow.cpp:583> "$HOME=C:/Users/elias" x2go-DEBUG-../src/onmainwindow.cpp:2420> Reading 3 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/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/pulsemanager.cpp:369> pulseaudio --version returned:"pulseaudio 7.1 " x2go-DEBUG-../src/onmainwindow.cpp:10492> Starting helper servers for Windows ... x2go-DEBUG-../src/onmainwindow.cpp:10659> "/cygdrive/C/Users/elias/.x2go/var" cygwin var path x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/onmainwindow.cpp:10742> "C:/Users/elias/.x2go/etc/sshd_config created." x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/onmainwindow.cpp:10274> Port is free: 6000 x2go-DEBUG-../src/onmainwindow.cpp:10274> Port is free: 7022 x2go-DEBUG-../src/onmainwindow.cpp:10340> Using internal X.Org Server: false xx2go-DEBUG-../src/onmainwindow.cpp:10408> Running "C:\program files\vcxsrv\vcxsrv.exe" "-multiwindow -notrayicon -clipboard :0" 2go-DEBUG-../src/onmainwindow.cpp:11092> Logging cygwin sshd to: "C:/Users/elias/.x2go/sshLogs/Hp1064.log" x2go-DEBUG-../src/onmainwindow.cpp:11106> Creating desktop: x2go_elias x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/pulsemanager.cpp:227> pulse started with arguments ("--exit-idle-time=-1", "-n", "-F", "C:\Users\elias\.x2go\pulse\config.pa", "-p", "C:\Users\elias\x2goclient2\pulse\lib\pulse-7.1\modules", "--log-level=debug", "--verbose", "--log-target=file:C:\Users\elias\.x2go\pulse\pulse.log") - waiting for it to finish... x2go-DEBUG-../src/onmainwindow.cpp:10274> Port is free: 7022 x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/pulsemanager.cpp:781> Warning! Pulseaudio's exit code is non-zero. x2go-DEBUG-../src/pulsemanager.cpp:785> Pulseaudio finished with code:1 x2go-DEBUG-../src/pulsemanager.cpp:788> x2go-DEBUG-../src/pulsemanager.cpp:791> x2go-DEBUG-../src/onmainwindow.cpp:10274> Port is free: 7022 x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/onmainwindow.cpp:10274> Port is free: 7022 x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/onmainwindow.cpp:10274> Port is free: 7022 x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/onmainwindow.cpp:10274> Port is free: 7022 x2go-DEBUG-../src/onmainwindow.cpp:10252> Resolved localhost. x2go-DEBUG-../src/onmainwindow.cpp:10274> Port is free: 7022 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread x2go-DEBUG-../src/onmainwindow.cpp:11199> Failed to start user mode OpenSSH server. I am using Windows 10 Pro x64

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev May 2018