x2go-dev August 2021

x2go-dev@lists.x2go.org

15 participants
94 discussions

Bug#1421: journalctl flooded with ssh_channel_accept: No channel request of this type from server
by Sorin T 10 Apr '23

10 Apr '23

Package: x2goclient Version: 4.1.2.1 This output is shown continuously. I have also disabled the Media and the Shared folders options. [2019/12/05 12:21:49.755356, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:49.844514, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:49.844968, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:50.345651, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:50.846330, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:51.347011, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:51.354536, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:51.355837, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:51.358011, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:51.858687, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:52.359381, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:52.860074, 1] ssh_channel_accept: No channel request of this type from server [2019/12/05 12:21:53.360787, 1] ssh_channel_accept: No channel request of this type from server It could be a ssh config problem ? I am using on client machine: OpenSSH_8.1p1, OpenSSL 1.1.1d 10 Sep 2019 Guest OS: Debian based Guest ssh version: OpenSSH_7.9p1 Debian-10, OpenSSL 1.1.1d 10 Sep 2019 Guest x2goserver: 4.1.0.3-4 Sent with [ProtonMail](https://protonmail.com) Secure Email.

3 6

Bug#1541: x2go graphics issue on MacOS Big Sur
by Kailin Zhuang 12 Aug '22

12 Aug '22

Package: x2goclient Version: 4.1.2.1 I'm using X2Go to run scientific software on our campus compute cluster (since 2019). I recently installed X2Go on a new MacBook Pro 2020 with the M1 chip running Big Sur. Immediately after launching X2Go, the following message repeats about 10 times per minute until I close X2Go: com.apple.xpc.launchd[1] (com.apple.mdworker.shared.XXX): Service exited due to SIGKILL | sent by mds[499]\ When I start Matlab (a scientific application I use for research), the x2go window turns black and becomes unusable. I'm enclosing a screenshot. The same Matlab software works as expected (no display problems) when I run it remotely via ssh (with X11 forwarding enabled) instead of X2Go.

2 1

Bug#1194: TERM variable not set
by Patryk P 12 Mar '22

12 Mar '22

Package: X2Go Client v. 4.1.0.0 (Qt - 4.8.6.) for windows 7 32bit Console output: [image: 2017-07-15 10_15_28-X2Go Client (Debug).png]

3 2

Bug#1556: GPG key error: public key E1F958385BFE2B6E is not available
by Chatterjee, Saion 15 Nov '21

15 Nov '21

Package: x2goserver Severity: critical Unable to install x2Go packages for Debian because the repository archive key is not available. When I try to bootstrap the repository GPG keys using the docs: https://wiki.x2go.org/doku.php/wiki:repositories:debian with this command: apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E Then I receive the following error message: GPG error: http://packages.x2go.org/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E1F958385BFE2B6E gpg: keyserver receive failed: No name It was working fine till last month. Please check if the public key has changed. I mark this ticket as critical because at the moment we are unable to even install x2Go for new users. Regards, Saion

2 3

Bug#1427: Update Tumbleweed packages for Perl 5.30
by Tristan Miller 28 Sep '21

28 Sep '21

Package: x2goserver Version: 4.1.0.4 Tags: rpm-packages Various openSUSE Tumbleweed packages for the X2Go server are built in such a way that they require Perl 5.28.1. However, Tumbleweed no longer distributes that version of Perl; it now distributes only Perl 5.30.1. This means that it is impossible to install these X2Go server packages on the most recent release of Tumbleweed, and for Tumbleweed systems where those X2Go server packages were already installed, it is impossible to upgrade Tumbleweed without removing the X2Go server: $ sudo zypper dup [sudo] password for root: Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... 9 Problems: Problem: x2goserver-common-4.1.0.4-0.0x2go1.0.git20191106.1811.heuler.x86_64 requires perl(:MODULE_COMPAT_5.28.1), but this requirement cannot be provided Problem: perl-5.28.1-3.4.x86_64 requires perl-base = 5.28.1, but this requirement cannot be provided Problem: perl-X2Go-Server-DB-4.1.0.4-0.0x2go1.0.git20191106.1811.heuler.x86_64 requires perl(:MODULE_COMPAT_5.28.1), but this requirement cannot be provided Problem: perl-X2Go-Server-4.1.0.4-0.0x2go1.0.git20191106.1811.heuler.x86_64 requires perl(:MODULE_COMPAT_5.28.1), but this requirement cannot be provided Problem: perl-X2Go-Log-4.1.0.4-0.0x2go1.0.git20191106.1811.heuler.x86_64 requires perl(:MODULE_COMPAT_5.28.1), but this requirement cannot be provided Problem: x2goserver-4.1.0.4-0.0x2go1.0.git20191106.1811.heuler.x86_64 requires perl(:MODULE_COMPAT_5.28.1), but this requirement cannot be provided Simply telling zypper to keep the obsolete packages doesn't work as this ends up in a rabbit-hole of seemingly irresolvable dependency issues.

1 4

Bug#1520: Proxy-Server - SSH - strong Cipher crash x2Go-Client
by Marian.Schwarcz＠dlr.de 20 Sep '21

20 Sep '21

Package: x2goClient Version: 4.1.2.2-2020.02.13 Host-System: Windows 10, und Windows Server 2012 R2 (German Language) Installations-Typ: Recommended (Default) *** Problem Description *** When using x2GoClient via jumpserver (as SSH-Proxy-Server), then is X2GoClient automatic closed (without any Information). Problem are the SSH-Strong-Ciphers, which are configured in SSHd on Jumpserver. Strong Ciphers => x2GoClient crashed. If default Ciphers => x2GoClient and connection works. *** X2GoClient - Configuration *** Sitzungsname: test Pfad: / Host: ziel-server Login: test_ye SSH-Port: 22 Proxy-Server für SSH-Verbindung verwenden SSH Host: jumpserver Port: 22 Gleiche Anmeldung wie für X2Go-Server Gleiches Kennwort wie für X2Go-Server XFCE *** Jumpserver Configuration) *** Jumpserver SSHd Config: /etc/ssh/sshd_config (CentOS 7) Ciphers aes128-ctr,aes192-ctr,aes256-ctr The ciphers are used for strong Encryption. Then access from x2GoClient via jumpserver cannot handle this. ------ When the Cipher-Restriction is not configured: Jumpserver SSHd Confg: (CentOS 7) #Ciphers aes128-ctr,aes192-ctr,aes256-ctr then the connection from x2GoClient via jumpserver to Destination X2Go-Server does work. I hope I provided all needed information for you. Let me know if this can be patched, or does our Company need to search for other solution. Thank you. Best regards, Marián Schwarcz

4 5

x2gokdrive: Move remote_init call into ddxProcessArgs function
by Mike Gabriel 01 Sep '21

01 Sep '21

Hi Alex, I looked into cmdline option parsing of x2gokdrive today. Reason was that I have a server where I set "-clipboard client" via a cmdline option. The x2gokdrive executable failed on that, because -clipboard is not a known option. What I found is that, other than in nxagent, in x2gokdrive the remote_init function is called via OsVendorInit, just when the session is about to start. In nxagent, the nxagentOption Rec (remoteVars in x2gokdrive is the equivalent) gets initialized earlier in ddxProcessArgs, this is a bit earlier. In X2Go, we have /etc/x2go/x2goagent.options. The file allows one to inject extra options into nxagent via server-side cmdline options. With Uli I recently discussed that the cmdline options should actually supercede the nx/nx options (so that X2Go-wise, site-admins can enforce certain agent features that cannot be overridden by X2Go Client client parameters). For nxagent, we are actually discussing a change in Args.c to make this possible. So, for x2gokdrive, I wonder if we could establish such a feature, as well: let cmdline options (set in /etc/x2go/x2goagent.options) override nx/nx options coming from X2Go Client and for this we would need to support setting remoteVars via cmdline options in ddxProcessArgs. For this, we would have to move the remoteVars init bit over into ddxProcessArgs (x2gokdriveinit.c, instead of x2gokdriveremote.c). I tried this locally, but failed, because whenever I referenced remoteVars from x2gokdriveinit.c the x2gokdrive ran into a segmentation fault. As you are much more familiar with the x2gokdrive code, is this something you could take a look at? For now, I have added a commit that adds more stub and compat cmdline options to x2gokdrive, also -clipboard. Thanks+Greets, Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de

2 2

Bug#1557: Windows client crashes when connecting to RHEL8
by Hans Peter Verne 27 Aug '21

27 Aug '21

Package: x2goclient Version: 4.1.2.2 Hello, devs! I'm afraid this is not a very precise bug report. Any assistance in how to investigate this is appreciated. We're running x2goclient 4.1.2.2 on Windows-10 machines, this has served us well up to now. With our new RedHat Enterprise Server 8.4 in production, we see the client crashing very often. When the client crashes, it does so shortly after trying to log in to a new or existing session. The clients "show details" window pane is activated, but the client dies before anything can be seen there. On the server, just these entries in the system logs appears: Aug 05 14:42:56 mimi.uio.no sshd[2421324]: Connection from 2001:700:100:4028:9462:e3c7:21c5:ec1c port 49763 on 2001:700:100:118::101 port 22 Aug 05 14:42:59 mimi.uio.no sshd[2421324]: Connection reset by 2001:700:100:4028:9462:e3c7:21c5:ec1c port 49763 [preauth] If I disable IPv6: Aug 05 14:45:30 mimi.uio.no sshd[2421601]: Connection from 193.157.161.44 port 57619 on 129.240.118.101 port 22 Aug 05 14:45:33 mimi.uio.no sshd[2421601]: Connection reset by 193.157.161.44 port 57619 [preauth] Note the absence of the "Fail password for ..." log entry. It looks like it never gets to even try authenticating. There is no problem logging in with putty from the same client machine, both with IPv6 and IPv4. Neither have I had this problem (at least not so frequent) with the Linux client. The server is running sshd and x2goserver from the RHEL8/EPEL repos, packages openssh-server-8.0p1-6 and x2goserver-4.1.0.3-9, respectively. I eventually tried to run sshd -ddd on the server and catch the output. The typescripts are attached (slightly edited): one where the client crashed; and one where it didn't (but couldn't authenticate, bad password). I'm no expert on ssh, but it seems like the difference appears after the key exchange ("KEX done"), when the instance that crashed never reaches the bit with userauth-request. I also tried "setenforce 0" on the server, i.e. disable SELinux, but the client still crashed. As it is, I can't clearly provide a procedure to reproduce the problem, as it doesn't always happen. If more information is required, or there are suggested steps to take, please let me know. Thanks in advance, and best regards, -- Hans Peter Verne -- IT-drift Geofag. In 1934, Van der Lubbe was beheaded in a German prison yard. In 1967, a court in West Berlin overturned the 1933 verdict, and posthumously changed Van der Lubbe's sentence to eight years in prison. -- "Reichstag fire" on Wikipedia.

3 4

Bug#1561: bug of ssh daemon\s public host key
by guo jiawei 24 Aug '21

24 Aug '21

Package: X2GO Client Version: 4.1.2.2 My x2go client can’t work. It report an error that “SSH daemon failed to opean it’s public host key. You have enabled remote printing or file sharing. The features require a running and functioning SSH server on your computer.Pringting and file sharing will be disable for this session. Normally this should not happen as X2GOclient for windows ships its own internal SSH server and automatically generates the required keys.”. And it asks me to report a bug on //wiki.x2go.org/doku.php/wiki:bugs It says disabling remote Pringting or file sharing support in the session setting will get rid of this message. Thank you a lot Jiawei Guo 从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送

1 1

Bug#1560: 转发: Bug of SSH host key
by guo jiawei 24 Aug '21

24 Aug '21

Package: X2GO client Version: 4.1.2.2 Hello x2go team, Since yesterday ,there is a flashback of the x2go client on my computer(win10). The problem is , after I connect with the server, the x2go client will have flashback. And today I got this message ,so I report this bug with you. [cid:image001.png@01D798C0.246E2520] Best regards Jiawei Guo 从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev August 2021