#461 - Can't connect to ssh anymore

X2Go Bug report logs - #461
Can't connect to ssh anymore

Reported by: Hadmut Danisch <hadmut@danisch.de>

Date: Mon, 24 Mar 2014 13:50:01 UTC

Severity: normal

Tags: pending

Merged with 408, 613

Found in version 4.0.1.2

Fixed in version 4.1.1.1

Done: X2Go Release Manager X2Go Release Manager <git-admin@x2go.org>

Bug is archived. No further changes may be made.

Received: (at submit) by bugs.x2go.org; 24 Mar 2014 13:47:47 +0000
From hadmut@danisch.de  Mon Mar 24 14:47:46 2014
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=ham
	version=3.3.2
X-Greylist: delayed 454 seconds by postgrey-1.34 at ymir; Mon, 24 Mar 2014 14:47:46 CET
Received: from mail.rackland.de (mail.rackland.de [212.86.200.188])
	by ymir (Postfix) with ESMTPS id B53715DB11
	for <submit@bugs.x2go.org>; Mon, 24 Mar 2014 14:47:46 +0100 (CET)
Received: from user.rackland.de (user.rackland.de [212.86.200.187])
	by mail.rackland.de (Postfix) with SMTP id AC49721360
	for <submit@bugs.x2go.org>; Mon, 24 Mar 2014 14:40:11 +0100 (CET)
Received: (nullmailer pid 17286 invoked by uid 1000);
	Mon, 24 Mar 2014 13:40:10 -0000
Date: Mon, 24 Mar 2014 14:40:10 +0100
From: Hadmut Danisch <hadmut@danisch.de>
To: submit@bugs.x2go.org
Subject: Can't connect to ssh anymore
Message-ID: <20140324134010.GA17202@danisch.de>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="wac7ysb48OaltWcw"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)

[Message part 1 (text/plain, inline)]

Package: x2goclient Version: 4.0.1.3-0~522~ubuntu14.04.1 Hi, I am currently testing x2go under Ubuntu 14.04. When I used x2go last week in my testing environment, everything was fine. Since 14.04 is still beta, there are heaps of daily updates, which I applied. Today I wanted to use x2go again, and it could not connect ssh anymore. x2go just shows an empty error messages (attached), and strace reveals, that x2go connects to port 22 of the server, reads (and even writes if needed) the ~/.ssh/known_hosts, and then silently aborts the connection without telling any reason. strace did not show a reason either. The sshd just complains because the client aborted the connections. The regular ssh command line client works. If x2go aborts the connection, it should at least notice and tell a good reason. regards Hadmut

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 18:41:11 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/.

X2Go Bug report logs - #461 Can't connect to ssh anymore

X2Go Bug report logs - #461
Can't connect to ssh anymore