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

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: Javier Almasoft <javier.almasoft@gmail.com>, 1349@bugs.x2go.org
Resent-From: Javier Almasoft <javier.almasoft@gmail.com>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Fri, 18 Jan 2019 08:45:02 +0000
Resent-Message-ID: <handler.1349.B1349.154780090232242@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 1349
X-X2Go-PR-Package: x2goclient
Received: via spool by 1349-submit@bugs.x2go.org id=B1349.154780090232242
          (code B ref 1349); Fri, 18 Jan 2019 08:45:02 +0000
Received: (at 1349) by bugs.x2go.org; 18 Jan 2019 08:41:42 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
X-Spam-Status: No, score=0.7 required=3.0 tests=BAYES_50,DKIM_SIGNED,
	autolearn_force=no version=3.4.2
Received: from localhost (localhost [])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 222755DACD
	for <1349@bugs.x2go.org>; Fri, 18 Jan 2019 09:41:39 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de
Received: from ymir.das-netzwerkteam.de ([])
	by localhost (ymir.das-netzwerkteam.de []) (amavisd-new, port 10024)
	with ESMTP id MvRzg1AiIPdJ for <1349@bugs.x2go.org>;
	Fri, 18 Jan 2019 09:41:32 +0100 (CET)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id A644C5DACB
	for <1349@bugs.x2go.org>; Fri, 18 Jan 2019 09:41:31 +0100 (CET)
Received: by mail-io1-xd29.google.com with SMTP id x6so10066524ioa.9
        for <1349@bugs.x2go.org>; Fri, 18 Jan 2019 00:41:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
X-Gm-Message-State: AJcUukfIA3AiEI1bpQ3rJKZOEXd7J+rlhHRg2TlaHQ1X88KRiUpzBWSB
X-Google-Smtp-Source: ALg8bN5OFWHHLX80UA05w6tDoG0upi+rBlvdUzjD4rO4UzWsyBrZmaBecrNI0L8Zt0FzITlfejFe3bxJ8meGA5oxcPU=
X-Received: by 2002:a5d:834e:: with SMTP id q14mr8808845ior.258.1547800889841;
 Fri, 18 Jan 2019 00:41:29 -0800 (PST)
MIME-Version: 1.0
References: <CA+Xr7UiReYoLJckkbECbYETvHPsS7Q6BR_MBD70yA26n=+M1Vg@mail.gmail.com>
 <CANVnVYJV0VkZU106dtjnu_iJeo7MpDNfDUQK2-BZdra2UEy4Uw@mail.gmail.com> <CA+Xr7UjtG1ZbNhjtdPw8AzDP0zU_OothZ=2N0jziiXToT4WbMg@mail.gmail.com>
In-Reply-To: <CA+Xr7UjtG1ZbNhjtdPw8AzDP0zU_OothZ=2N0jziiXToT4WbMg@mail.gmail.com>
From: Javier Almasoft <javier.almasoft@gmail.com>
Date: Fri, 18 Jan 2019 09:41:14 +0100
Message-ID: <CA+Xr7Uj95Bb8vCE=i8Wb_aOCdS+Kx+b=YXrEyhCfa5hyv9EUKw@mail.gmail.com>
To: 1349@bugs.x2go.org
Content-Type: multipart/alternative; boundary="00000000000038d993057fb77a00"
[Message part 1 (text/plain, inline)]
From: Javier Almasoft <javier.almasoft@gmail.com>
Date: jue., 10 ene. 2019 a las 10:25
Subject: Re: [X2Go-Dev] Bug#1349: x2goclient not connecting after upgrade

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 *

at the end of the file, because I have the custom of setting my installed
servers apart from the default 22, to minimize attacks from port scanners.
And not all my remote machines are declared in the config file, so this
line takes care of the forgotten ones. If I comment out that line,
x2goclient works again, both connecting to the default port 22 or to a
non-standard port.

It didn't matter before if I was connecting to a standard setup in port 22,
or a custom one. It always choked at that line.

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?

Thanks for taking your time in answering (and motivating me in digging more
on this... ;-) ). It was really a nuisance, i use x2go in a lot if machines.

Un saludo,
Javier Martínez
[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Sun Jun 11 00:46:32 2023; 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.