x2go-dev November 2022

x2go-dev@lists.x2go.org

2 participants
75 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#1593: X2Go Windows Client fails to connect to hostname resolving to both IPv4 and IPv6
by me＠jcn50.com 24 Nov '22

24 Nov '22

Package: X2Go Windows Client Version: 4.1.2.2 I have a hostname that has both 1x IPv4 address (A records) and 1x IPv6 address (AAAA records). The client fails to connect (connection timeout error) if I use the hostname. However if I enter the IPv4 or the IPv6 instead of the hostname: it works! Proposed solution: it should try to connect/resolve to the IPv6 first, then the IPv4. Regards, Chris. PS: I have re-sent this message because I was not a member of the mailing list, and I cancelled the previously sent one.

1 1

Bug#1594: X2Go Windows Client fails to connect to hostname resolving to both IPv4 and IPv6
by me＠jcn50.com 24 Nov '22

24 Nov '22

Package: X2Go Windows Client Version: 4.1.2.2 I have a hostname that has both 1x IPv4 address (A records) and 1x IPv6 address (AAAA records). The client fails to connect (connection timeout error exact message: "Timeout connecting to $HOSTNAME") if I use the hostname. However if I enter the IPv4 or the IPv6 instead of the hostname: it works! Proposed solution: it should try to connect/resolve to the IPv6 first, then the IPv4. Regards, Chris.

1 0

Bug#1592: X2Go Windows Client fails to connect to hostname resolving to both IPv4 and IPv6
by me＠jcn50.com 24 Nov '22

24 Nov '22

Package: X2Go Windows Client Version: 4.1.2.2 I have a hostname that has both 1x IPv4 address (A records) and 1x IPv6 address (AAAA records). The client fails to connect (connection timeout error) if I use the hostname. However if I enter the IPv4 or the IPv6 instead of the hostname: no problem! Proposed solution: it should try to connect/resolve to the IPv6 first, then the IPv4. Regards, Chris.

1 0

Two Upcoming X2Go Events: X2Go: The Spread 2021.5 and 2022
by Stefan Baur 22 Nov '22

22 Nov '22

Hi $ALL, It's been a while, but now it is time for not only one, but two X2Go Events. As you all know, the Covid-19 pandemic kept us from hosting our usual X2Go: The Gathering events in 2021 and 2022. So instead of gathering, we'll now spread out. Instead of meeting for a weekend in "meatspace", like we used to, we'll now meet online during the work week starting 18:00 CET/MEZ each day (or possibly even later, given volunteer feedback), and only for a few hours each day. X2Go: The Spread 2021.5 (2022-11-28 to 2022-12-02) is the replacement event for X2Go: The Gathering 2021, which had to be cancelled due to illness of several core members. This event starts in a little less than a week - but if you can't make it on such short notice, do not worry. X2Go: The Spread 2021.5 will be more of an informal virtual meetup, with people working on "behind the scenes" stuff, testing out our streaming/recording equipment, etc. The "real deal" will be X2Go: The Spread 2022, which is also scheduled for the evening hours, but will take place from 2022-12-12 to 2022-12-16 (with a possible extension to one of the weekends before or after - we'll see). This is where we'll also have the annual orca e.V. meeting. The date and time for the orca e.V. meeting is fixed: 2022-12-16, 20:00 CET/MEZ. This is the event where we'll see/hear a talk each evening, and work on getting our releases out. Of course, both events have their own wiki page to track progress and updates: X2Go: The Spread 2021.5: <https://wiki.x2go.org/doku.php/events:x2go-spread-2021.5> X2Go: The Spread 2022: <https://wiki.x2go.org/doku.php/events:x2go-spread-2022> Kind Regards, Stefan Baur, X2Go's Event Planner -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev November 2022