From unknown Sat May 16 11:07:19 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#139: Reply-To: "Gross, Christopher W. (Chris)" , 139@bugs.x2go.org Resent-From: "Gross, Christopher W. (Chris)" Resent-To: x2go-dev@lists.berlios.de Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Mon, 16 Sep 2013 11:48:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 139 X-X2Go-PR-Package: x2goclient X-X2Go-PR-Keywords: Received: via spool by 139-submit@bugs.x2go.org id=B139.137933149121627 (code B ref 139); Mon, 16 Sep 2013 11:48:02 +0000 Received: (at 139) by bugs.x2go.org; 16 Sep 2013 11:38:11 +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=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE autolearn=ham version=3.3.2 Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ymir (Postfix) with ESMTPS id 7B3905DA79 for <139@bugs.x2go.org>; Mon, 16 Sep 2013 13:38:10 +0200 (CEST) Received: from mail166-tx2-R.bigfish.com (10.9.14.232) by TX2EHSOBE009.bigfish.com (10.9.40.29) with Microsoft SMTP Server id 14.1.225.22; Mon, 16 Sep 2013 11:38:08 +0000 Received: from mail166-tx2 (localhost [127.0.0.1]) by mail166-tx2-R.bigfish.com (Postfix) with ESMTP id 54FF72A006A for <139@bugs.x2go.org>; Mon, 16 Sep 2013 11:38:08 +0000 (UTC) X-Forefront-Antispam-Report: CIP:164.107.81.220;KIP:(null);UIP:(null);IPV:NLI;H:cio-tnc-pf06;RD:none;EFVD:NLI X-SpamScore: 17 X-BigFish: VPS17(zzc85fhzz1f42h1d77h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h18c673h1de097hz2fh2a8h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1fe8h1ff5h20f0ha02m20b8s1b1bi1155h) Received-SPF: pass (mail166-tx2: domain of osu.edu designates 164.107.81.220 as permitted sender) client-ip=164.107.81.220; envelope-from=gross.364@osu.edu; helo=cio-tnc-pf06 ;cio-tnc-pf06 ; Received: from mail166-tx2 (localhost.localdomain [127.0.0.1]) by mail166-tx2 (MessageSwitch) id 1379331485684602_2393; Mon, 16 Sep 2013 11:38:05 +0000 (UTC) Received: from TX2EHSMHS015.bigfish.com (unknown [10.9.14.252]) by mail166-tx2.bigfish.com (Postfix) with ESMTP id 98D9C4006E for <139@bugs.x2go.org>; Mon, 16 Sep 2013 11:38:05 +0000 (UTC) Received: from cio-tnc-pf06 (164.107.81.220) by TX2EHSMHS015.bigfish.com (10.9.99.115) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 16 Sep 2013 11:38:05 +0000 Received: from CIO-TNC-HT06.osuad.osu.edu (localhost [127.0.0.1]) by cio-tnc-pf06 (Postfix) with ESMTP id A1D9E3C0060 for <139@bugs.x2go.org>; Mon, 16 Sep 2013 07:36:35 -0400 (EDT) Received: from CIO-KRC-D1MBX04.osuad.osu.edu ([fe80::d025:f47e:cbe9:18b]) by CIO-TNC-HT06.osuad.osu.edu ([fe80::3d16:84bd:8d88:7cfd%12]) with mapi id 14.03.0123.003; Mon, 16 Sep 2013 07:38:05 -0400 From: "Gross, Christopher W. (Chris)" To: "139@bugs.x2go.org" <139@bugs.x2go.org> Thread-Index: AQHOstE0HorZ5qU3rkWrZtQBE+ggng== Date: Mon, 16 Sep 2013 11:38:04 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.146.220.206] Content-Type: multipart/alternative; boundary="_000_C873205AEA1C844AA36A68A66637C180819C248FCIOKRCD1MBX04os_" MIME-Version: 1.0 X-CFilter-Loop: Forward X-OriginatorOrg: osu.edu X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% --_000_C873205AEA1C844AA36A68A66637C180819C248FCIOKRCD1MBX04os_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable This is very disappointing. It's been 6 months since this report was filed = (and since the last release) and even though it was acknowledged in July, i= t still was not fixed in the current version. Will we be stuck with this bu= g for another six months? --_000_C873205AEA1C844AA36A68A66637C180819C248FCIOKRCD1MBX04os_ Content-Type: text/html; charset="us-ascii" Content-ID: <549D41B68C741841A9FDCA8F9BD6D6B0@osu.edu> Content-Transfer-Encoding: quoted-printable
This is very disappointing. It's been 6 months since this report was filed = (and since the last release) and even though it was acknowledged in July, i= t still was not fixed in the current version. Will we be stuck with this bu= g for another six months? --_000_C873205AEA1C844AA36A68A66637C180819C248FCIOKRCD1MBX04os_--