From mikedep333@gmail.com  Wed Jul 23 04:14:45 2014
Received: (at 547) by bugs.x2go.org; 23 Jul 2014 02:14:46 +0000
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,FREEMAIL_FROM,
	T_DKIM_INVALID autolearn=ham version=3.3.2
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 313E05DB3E
	for <547@bugs.x2go.org>; Wed, 23 Jul 2014 04:14:44 +0200 (CEST)
Received: by mail-wi0-f180.google.com with SMTP id n3so1388510wiv.13
        for <547@bugs.x2go.org>; Tue, 22 Jul 2014 19:14:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:cc:content-type;
        bh=U6jdNER0d0HLX0kiXUzaqPZe+PkvCi56BWGCLF9LY2g=;
        b=t2Zu5ZqE2fYcjhoSusrLPWC5FR5TKPV8oQcQgxrlPBPr6KLzJp5gFgBt+sGhKJ53Rr
         dOile7cOJwPTxfJI/YRxJgUvOmAsiP6YxCNjeIfS42cFJcyVf5sVGDzWRTRTc3/FOUob
         +duaeIdDjNwkibJ8WpBGBivmWbQI2sXXMzC6AHLm2SzsPVsRikNHR62CA7tAoqqQXfJ7
         WSzbyJhQY5AGkM+u3hg4l1rNpBkb284ai7X7yNnwIvV0/fndzXkt555283VsuaQAAbMv
         vto2MVFRgLprdkE8TYS57kqyRNVFoboI4j0B3XT4VdUBWHqbtHIf7uQ6PqZikXjLmDTj
         DrRg==
MIME-Version: 1.0
X-Received: by 10.180.89.143 with SMTP id bo15mr19784251wib.78.1406081684319;
 Tue, 22 Jul 2014 19:14:44 -0700 (PDT)
Received: by 10.180.98.233 with HTTP; Tue, 22 Jul 2014 19:14:44 -0700 (PDT)
Date: Tue, 22 Jul 2014 22:14:44 -0400
Message-ID: <CAMKht8hMUGm2TcjYmikefUUuUKJ6rh5oM90iA9vqQFKSokDC8Q@mail.gmail.com>
Subject: Alex's fix in x2goserver
From: Michael DePaulo <mikedep333@gmail.com>
To: 547@bugs.x2go.org
Cc: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, 
	Oleksandr Shneyder <o.shneyder@phoca-gmbh.de>
Content-Type: text/plain; charset=UTF-8

I can confirm that Alex's commit to x2goserver (rather than
x2goclient) fixes this bug.

bf318affee905cf7cdeaa5a248dfd07bc46a8a96
Clean user SSHD process if connection between server and client lost.
This should fix error "Global request tcpip-forward failed".
http://code.x2go.org/gitweb?p=x2goserver.git;a=commit;h=bf318affee905cf7cdeaa5a248dfd07bc46a8a96

Mike#1
Should I retitle and reassign this bug (#547) to x2goserver? And
should we cherry-pick it for x2goserver release/4.0.0.x &
release/4.0.1.x? We should probably release updated versions of
4.0.0.x (baikal) and 4.0.1.x at least a month before we release
x2goclient 4.0.3.0. Otherwise, people will run into this bug if they
update their clients to 4.0.3.0 but do not update their servers.

-Mike#2