x2go-dev February 2022

x2go-dev@lists.x2go.org

4 participants
76 discussions

loginctl 'enable-linger' causes systemd --user to respawn on boot
by Montjoy, Robert (montjoy) 28 Sep '23

28 Sep '23

Hi. At one time "loginctl enable-linger" was added to the x2gostartagent to make sure the systemd did not kill the x2go process on disconnect. This has had the probably undesired affect of having systemd --user username being executed on boot for every x2go user. At the last boot about 70 processes (one for systemd and one for pam) were spawned. This is probably not what we want. Is there a better way to handle the systemd termination issue? Should something like systemd-run --scope --user x2goagent ..... be used instead? Or can x2go cleanup this entry on termination? Maybe have x2gocleansessions do it? Note: I will probably cleanup /var/lib/systemd/linger on boot by executing rm -f /var/lib/systemd/linger/* but that it is more of a "hammer" approach than anything else. Thanks in advance. Rob

3 2

Bug#1445: pyhoca-cli fails to connect to suspended x2go session
by Randy Goldenberg 22 Aug '23

22 Aug '23

Package: pyhoca-cli Version: 0.6.1.2 Tag: patch pyhoca-cli fails to connect to suspended x2g0 sessions. $ pyhoca-cli --server my.x2go.server -t desktop -c openbox-session -g maximize -R NEWEST pyhoca-cli[13131] NOTICE: preparing requested X2Go session pyhoca-cli[13131] (PyHocaCLI) NOTICE: preparing requested X2Go session pyhoca-cli[13131] (x2gosessregistry-pylib) NOTICE: registering X2Go session Pyhoca-Client_Session... pyhoca-cli[13131] (x2goclient-pylib) NOTICE: initializing X2Go session... pyhoca-cli[13131] (x2gocontrolsession-pylib) NOTICE: connecting to [my.x2go.server]:22 /usr/lib/python3/dist-packages/Crypto/Cipher/blockalgo.py:141: FutureWarning: CTR mode needs counter parameter, not IV self._cipher = factory.new(key, *args, **kwargs) pyhoca-cli[13131] (PyHocaCLI) NOTICE: authentication has been successful pyhoca-cli[13131] (PyHocaCLI) NOTICE: give the X2Go session some time to come up... Traceback (most recent call last): File "/usr/bin/pyhoca-cli", line 455, in <module> thisPyHocaCLI.MainLoop() File "/usr/lib/python3/dist-packages/pyhoca/cli/frontend.py", line 702, in MainLoop self.resume_session(self.x2go_session_hash) File "/usr/lib/python3/dist-packages/pyhoca/cli/frontend.py", line 229, in resume_session if available_sessions is None: UnboundLocalError: local variable 'available_sessions' referenced before assignment client OS: Ubuntu 16.04.6 LTS server OS: Ubuntu 16.04.6 LTS server's version of the x2goserver package: x2goserver: 4.1.0.4 x2goserver-common: 4.1.0.4 x2goserver-desktopsharing: 4.1.0.3 x2goserver-extensions: 4.1.0.4 x2goserver-fmbindings: 4.1.0.4 x2goserver-printing: 4.1.0.4 x2goserver-xsession: 4.1.0.4 Patch attached. ----- End forwarded message -----

4 4

Bug#1469: X2Go Client connection issue (Socket error)
by Melroy van den Berg 29 Jun '23

29 Jun '23

Package: x2goclient Version: 4.1.2.2 I often get an error message when I try to connect to my Debian buster docker image, running x2goserver and XFCE, via the X2Go Client on my host machine. It will give the following error message (when using the --debug flag on the x2goclient): x2go-DEBUG-../src/sshmasterconnection.cpp:2071> "ssh_channel_open_session failed": "Socket error: No such file or directory" x2go-DEBUG-../src/sshprocess.cpp:478> I/O error: "ssh_channel_open_session failed."" - Socket error: No such file or directory" (0). I created a detailed video, I posted it on YouTube, please take a look at the video: https://youtu.be/LAlLtBNTIUo Logging details, reproducibility and more is explained in the video itself. You'll notice that I can sometimes connect to the XFCE session and sometimes I can't. Although connecting via the ssh cli command is always working without any issues. Meaning there is really some kind of bug in the X2Go Client. I'm afraid. Again, I really hope somebody could help me in finding the root-cause and fixing the issue. Since I really love X2Go. And I would like to use this tool in production. I'm also a software developer so maybe I can help debugging the problem. Similar (same) bug is reported in the past (from 2019): https://lists.x2go.org/pipermail/x2go-user/2019-March/005512.html All the details regarding this Docker image and setup can be found in this git repo: https://gitlab.melroy.org/melroy/xfcevdi See attachments for additional debug logs of the client itself. One when successful and one during the error. Thanks in advance! Kind regards, Melroy van den Berg Ps. You can contact me by mail of course. But I can understand that debugging this issue would be preferable be done via VoIP for example.

7 18

Bug#1434: Use login shell for session
by Orion Poplawski 30 May '23

30 May '23

Package: x2goserver Version: 4.1.0.3 Tags: patch X2Go's Xsession file always starts the user's session with /bin/bash (at least on RedHat systems where SHELL is set to /bin/bash via ~/.bashrc calling /etc/bashrc). This patch attempts to determine the user's login shell and use that for launching the session. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1794660 Another option might be the judicious use of the --norc option when launching x2goruncommand on followers but I'm not sure what other effects this will have or where to do that. Effects might not be to bad because I can simulate this by moving away the user's .bash_profile and .bashrc files and then the tcsh is used as expected in this case. However, while $SHELL does not get set in this case, the xfce4-session script still gets launched with bash which triggers some other errors, so this patch may be the best option. --- x2goserver-xsession/etc/Xsession | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/x2goserver-xsession/etc/Xsession b/x2goserver-xsession/etc/Xsession index 270a0b3..522f37e 100755 --- a/x2goserver-xsession/etc/Xsession +++ b/x2goserver-xsession/etc/Xsession @@ -117,6 +117,10 @@ if ! echo "*" >>"$WRITE_TEST"; then fi rm -f "$WRITE_TEST" +# Determine the users login shell and use that to launch the session +SHELL=$(getent passwd $LOGNAME | cut -d: -f7) +# Fallback +[ -z "$SHELL" ] && SHELL=/bin/bash if [ -f /etc/debian_version ] || [ -f /etc/devuan_version ]; then -- 1.8.3.1 -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 https://www.nwra.com/

4 4

Bug#1388: Update keystrokes.cfg
by Ulrich Sibiller 30 May '23

30 May '23

Package: x2goserver-x2goagent Version: 4.1.0.3-0x2go1+git2018112 The keystroke.cfg is a) buggy and b) incomplete. Here's a patch that updates it (clone from nxagent 3.5.99.20).

3 2

Bug#1395: x2golistsessions_root update man page
by Ja Bi 30 May '23

30 May '23

Package: <x2goserver> Version: <a.b.c.d> Severity: wishlist Hi guys, it would be great to add "--all-servers" to x2golistsessions_root man page would be: SYNOPSIS x2golistsessions_root [<server_hostname>|--all-servers] thanks J.

4 3

Bug#1357: pyhoca 0.6.0.1 incompatible with x2goserver 4.1.0.3
by Chris Greenshields 30 May '23

30 May '23

Package: Pyhoca Version: 0.6.0.1 I tested all combinations of the following recent releases of the following software from the ppa:x2go/stable and ubuntu repositories: + x2goserver + 4.1.0.0-3 (ubuntu) + 4.1.0.3-0~1708~ubuntu18.04.1 (ppa:x2go/stable) + x2goclient + 4.1.1.1-2 (ubuntu) + 4.1.2.1-0~1788~ubuntu18.04.1 (ppa:x2go/stable) + pyhoca-cli + 0.5.0.4-1 (ubuntu) + 0.6.0.1 (ppa:x2go/stable) There is one combination that did not work: x2goserver 4.1.0.3-0~1708~ubuntu18.04.1 (ppa:x2go/stable) with pyhoca-cli 0.6.0.1 (ppa:x2go/stable) It failed with the following message, which I assume is a bug: " a bytes-like object is required, not 'str' pyhoca-cli: error: the remote server does not have the X2Go Server software installed "

5 12

Bug#1537: Logfile corruption
by Ulrich Sibiller 30 May '23

30 May '23

Package: x2goserver Version: 4.1.0.3 See attached patch for a fix to the session.log being corrupted when nxagent is printing a lot of debug output.

4 4

Bug#1538: Keystrokes file out-of-date
by Ulrich Sibiller 30 May '23

30 May '23

Package: x2goserver-x2goagent Version: 4.1.0.3 The keystrokes file does not match up with the version of the latest nxagent. Attached patch fixes that.

4 4

Bug#1228: Ctrl-Alt-T doesn't terminate connection in "local desktop" sessions
by Alexey Nemov 30 May '23

30 May '23

Package: x2goserver Version: 4.0.1.20 Summary: As stated in the wiki https://wiki.x2go.org/doku.php/wiki:advanced:nx-keyboard-shortcuts The action "close_session" should terminate the session. But, pressing Ctrl-Alt-t in a "local desktop" session does not "terminate" the session. Steps to reproduce: 0. Create a new session profile in x2goclient with session type "Connect to local desktop"; 1. Connect to remote computer using this session profile; 2. Press Ctrl-Alt-t at the client. Expected behaviour: The remote desktop window on the client should close, the connection should be terminated. Actual behaviour: The remote desktop window on the client does not close, the connection is not terminated. The following log entries appears in the server's system journal: ``` Oct 26 13:50:39 localhost /usr/bin/x2gosuspend-session[31790]: session with ID alex-50-1508997021_stS1XSHADalexXSHADPP0_dp24 has been suspended successfully Oct 26 13:50:45 localhost su[31900]: Successful su for alex by root Oct 26 13:50:45 localhost su[31900]: + ??? root:alex Oct 26 13:50:45 localhost su[31900]: pam_unix(su:session): session opened for user alex by (uid=0) Oct 26 13:50:45 localhost systemd-logind[508]: New session c99 of user alex. Oct 26 13:50:45 localhost systemd[1]: Started Session c99 of user alex. Oct 26 13:50:46 localhost su[31900]: pam_unix(su:session): session closed for user alex Oct 26 13:50:46 localhost su[31923]: Successful su for alex by root Oct 26 13:50:46 localhost su[31923]: + ??? root:alex Oct 26 13:50:46 localhost su[31923]: pam_unix(su:session): session opened for user alex by (uid=0) Oct 26 13:50:46 localhost systemd-logind[508]: Removed session c99. Oct 26 13:50:46 localhost systemd-logind[508]: New session c100 of user alex. Oct 26 13:50:46 localhost systemd[1]: Started Session c100 of user alex. Oct 26 13:50:49 localhost /usr/bin/x2gosuspend-session[32026]: session with ID alex-50-1508997021_stS1XSHADalexXSHADPP0_dp24 has been suspended successfully Oct 26 13:50:50 localhost su[31923]: pam_unix(su:session): session closed for user alex Oct 26 13:50:50 localhost systemd-logind[508]: Removed session c100. Oct 26 13:50:53 localhost /usr/sbin/x2gocleansessions[12745]: alex-50-1508997021_stS1XSHADalexXSHADPP0_dp24: session status S desynchronized with current status (R) and session suspend already tried unsuccessfully ``` Other infomation: 0. Executing x2gosuspend-session <ID> on the server has the same effect as pressing C-A-t at the client. 1. Execuitng x2goterminate-session <ID> on the server does terminates the session and closes the client window. 3. Server-side /etc/x2go/keystrokes.cfg: http://paste.debian.net/plain/992795 -- System Information (server and client): Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)

6 10

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev February 2022