From mikedep333@gmail.com Thu Oct 9 13:57:10 2014 Received: (at 616) by bugs.x2go.org; 9 Oct 2014 11:57: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=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM, RCVD_IN_DNSWL_BLOCKED,T_DKIM_INVALID autolearn=ham version=3.3.2 Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 536D65DB16 for <616@bugs.x2go.org>; Thu, 9 Oct 2014 13:57:10 +0200 (CEST) Received: by mail-wi0-f177.google.com with SMTP id fb4so1486697wid.16 for <616@bugs.x2go.org>; Thu, 09 Oct 2014 04:57:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Yp9EBq0gfeMtpj9pfYKDYMsLpV9RZOUH601PvN68YgE=; b=FSwm6I9GO8IKGJTH3OklKkB2RJwkgeGuLiBNI8IhDN+z+NVwGoz/09yHP2e4yw8b5u ilmhlyOCcEC0bMcMiK/FybItUe7v30InE633ZILs7KmFO0VHqjQ64Pi6hPBO3zt3rLyb tsAeAqmA9kl+KziP2C0HIfboNO/pUEek8xQR7TTwzkuxBO5qtuISa29ICA93dlp5QSLm omjUTAf/EstA2jlFB+d785hT7SgQIAZgjFltI3E1iBp0+3oQ7+bnDXNMgMz4Ga8xvSib 2Hnzs+vTHIxObEpZm1ZpkkvIUz0Uoue2XUCwmX9Ns1HCWNlsafKM2oaj9Qb/KjM6wClG hKsw== MIME-Version: 1.0 X-Received: by 10.194.234.66 with SMTP id uc2mr12933891wjc.26.1412855829978; Thu, 09 Oct 2014 04:57:09 -0700 (PDT) Received: by 10.180.81.99 with HTTP; Thu, 9 Oct 2014 04:57:09 -0700 (PDT) In-Reply-To: <54367785.6070903@phoca-gmbh.de> References: <54367785.6070903@phoca-gmbh.de> Date: Thu, 9 Oct 2014 07:57:09 -0400 Message-ID: Subject: Re: bug 616 should be fixed before x2go client 4.0.3.0 is released From: Michael DePaulo To: Oleksandr Shneyder Cc: 616@bugs.x2go.org, Stefan Baur Content-Type: text/plain; charset=UTF-8 On Thu, Oct 9, 2014 at 7:54 AM, Oleksandr Shneyder wrote: > Hi Mike, > > I cannot reproduce this bug. Can you? > > regards, > Alex > > Am 09.10.2014 13:37, schrieb Michael DePaulo: >> Hi Alex, >> >> Stefan and I believe that this bug (#616) should be fixed before X2Go >> Client 4.0.3.0 is released. Please let us know if you have any ideas >> on how to fix it. >> >> Mihai, Mike#1 thought you may be able to help also. >> >> -Mike#2 Hi Alex, (Is there a reason why you did not CC others?) I cannot reproduce it either. Stefan can though.