X2Go Bug report logs - #1349
x2goclient not connecting after upgrade

version graph

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: Javier Almasoft <javier.almasoft@gmail.com>

Date: Mon, 26 Nov 2018 07:55:02 UTC

Severity: normal

Found in version 4.1.2.1-3

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#1349: Fwd: [X2Go-Dev] Bug#1349: x2goclient not connecting after upgrade
Reply-To: Felix Schueller <fs-linux_bug@fschueller.eu>, 1349@bugs.x2go.org
Resent-From: Felix Schueller <fs-linux_bug@fschueller.eu>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Tue, 24 Sep 2019 19:50:01 +0000
Resent-Message-ID: <handler.1349.B1349.156935447614261@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 1349
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
References: <CA+Xr7UiReYoLJckkbECbYETvHPsS7Q6BR_MBD70yA26n=+M1Vg@mail.gmail.com> <CANVnVYJV0VkZU106dtjnu_iJeo7MpDNfDUQK2-BZdra2UEy4Uw@mail.gmail.com> <CA+Xr7UjtG1ZbNhjtdPw8AzDP0zU_OothZ=2N0jziiXToT4WbMg@mail.gmail.com> <CA+Xr7Uj95Bb8vCE=i8Wb_aOCdS+Kx+b=YXrEyhCfa5hyv9EUKw@mail.gmail.com> <CA+Xr7UiReYoLJckkbECbYETvHPsS7Q6BR_MBD70yA26n=+M1Vg@mail.gmail.com>
Received: via spool by 1349-submit@bugs.x2go.org id=B1349.156935447614261
          (code B ref 1349); Tue, 24 Sep 2019 19:50:01 +0000
Received: (at 1349) by bugs.x2go.org; 24 Sep 2019 19:47:56 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=3.0 tests=BAYES_40,KHOP_HELO_FCRDNS,
	SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2
Received: from mail.fschueller.eu (newsfeed.fschueller.eu [IPv6:2a00:1828:2000:882::13])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 4352A5DAE5
	for <1349@bugs.x2go.org>; Tue, 24 Sep 2019 21:47:52 +0200 (CEST)
Received: from [fdfe:6fcc:3f02:2::52] (helo=hydra.v4.fschueller.eu)
	by mail.fschueller.eu with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.89)
	(envelope-from <fs-linux_bug@fschueller.eu>)
	id 1iCqmt-0002Qq-1V
	for 1349@bugs.x2go.org; Tue, 24 Sep 2019 21:47:51 +0200
Received: from felix by hydra.v4.fschueller.eu with local (Exim 4.92)
	(envelope-from <fs-linux_bug@fschueller.eu>)
	id 1iCqms-00031c-Rs
	for 1349@bugs.x2go.org; Tue, 24 Sep 2019 21:47:50 +0200
Date: Tue, 24 Sep 2019 21:47:50 +0200
From: Felix Schueller <fs-linux_bug@fschueller.eu>
To: 1349@bugs.x2go.org
Message-ID: <20190924194749.ar5fd4wxbrqzxrxn@fschueller.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+Xr7Uj95Bb8vCE=i8Wb_aOCdS+Kx+b=YXrEyhCfa5hyv9EUKw@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20180716

> I did a bit of testing today, and managed to set it running. I happen to
> have a non-standard port declared as default for ssh connections in my
> .ssh/config file, in the form:
> 
> Host *
> Port NNNNN

[...]

> This line doesn't give problems in my ssh connections, though. Perhaps
> there is a problem somewhere in the parsing of the ssh config file? Where
> should I report that?

I also triggered this bug. It looks like some problem with the parsing,
because ist is also triggered if the non-standard port is defined for
some totally unrelated host.

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Wed Apr 24 10:29:34 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.