From mikedep333@gmail.com Tue Sep 16 14:43:06 2014 Received: (at 566) by bugs.x2go.org; 16 Sep 2014 12:43:07 +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,FREEMAIL_FROM, 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 4561F5DB54 for <566@bugs.x2go.org>; Tue, 16 Sep 2014 14:43:06 +0200 (CEST) Received: by mail-wi0-f177.google.com with SMTP id em10so6205867wid.4 for <566@bugs.x2go.org>; Tue, 16 Sep 2014 05:43:06 -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:content-transfer-encoding; bh=btME2FCR7dkbmrLKAhMnetjIjUpjDA1+OlUIHvP8YLU=; b=bgfOpLWkK5XsON//Hz0D1X0p420VHDUxfxZ7yyTQqyfzGLgTC+fArbo5w0skAo6zbr eZpqwfpktkbZ/i+Pm2F0AnBkgsT1U7qQdi6Gm68w+PDifGbtzsLgg92YzNtQg7iQkC9I mbNpFBLGejKn+7yDz9MsYSIE9TzPueiF2JXSzYJMNeRF5xDmzGJ3QwejCfWJZD1GX7Qp poQay74jKpXvSZkcssV7KNf+DNK/WinQVtGbPOHtTTvlx9NmCR+lTxZ9CCjybiPR9We4 nbL+9xP+lvXhKbDz0C5jkcTWaqpNP3XdvdjX6dL3mz+jMvLRV4p5pvaLpacorEkzO0fT VssQ== MIME-Version: 1.0 X-Received: by 10.194.122.169 with SMTP id lt9mr43359664wjb.29.1410871385300; Tue, 16 Sep 2014 05:43:05 -0700 (PDT) Received: by 10.180.106.39 with HTTP; Tue, 16 Sep 2014 05:43:05 -0700 (PDT) In-Reply-To: <000001cfd172$255b96b0$7012c410$@edu.gr> References: <000001cfb552$3193a8a0$94baf9e0$@gr> <000001cfc60a$32831de0$978959a0$@gr> <20140901195103.Horde.HOAd34FDzvE7MwwNBCtaAg1@mail.das-netzwerkteam.de> <000001cfca83$2b11d830$81358890$@edu.gr> <20140908085833.Horde.1KVN9LjgQ3GOkz4EX-JZjA1@mail.das-netzwerkteam.de> <000001cfd0a5$a1fe42d0$e5fac870$@edu.gr> <000001cfd172$255b96b0$7012c410$@edu.gr> Date: Tue, 16 Sep 2014 08:43:05 -0400 Message-ID: Subject: Re: [X2Go-Dev] Bug#566: X2Go Client for Windows 4.0.2.1 cannot create C:\Users\\ssh\known_hosts file when the local Windows account username has non-Ascii characters From: Michael DePaulo To: 566@bugs.x2go.org Cc: uribepnr@gmail.com, =?UTF-8?B?zpPOtc+Oz4HOs865zr/PgiDOpM+BzrHOus6xz4TOrc67zrfPgg==?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi George, See inline responses. On Tue, Sep 16, 2014 at 1:50 AM, =CE=93=CE=B5=CF=8E=CF=81=CE=B3=CE=B9=CE=BF= =CF=82 =CE=A4=CF=81=CE=B1=CE=BA=CE=B1=CF=84=CE=AD=CE=BB=CE=B7=CF=82 wrote: > Dear Mike, > > Two things. > > 1. Please make a preview build of X2Go Client for Windows with the patch = applied and inform me when you do so. > I'd rather test a complete preview package of X2Go Client 4.0.3.0 for Win= dows. Done: 4.0.3.0-pre01. The debug build is available too, and I manually updated the shortcuts in the debug build.[1] http://code.x2go.org/releases/binary-win32/x2goclient/previews/4.0.3.0/ I will now announce this on the mailing list. > 2. Before writing this reply I had a recollection of initially having bum= ped onto a similar bug that was dismissed > due to the fact that the submitter's system was not POSIX compliant. I se= arched for the bug but I couldn't find it. > > Then I decided to give bug #566 a try on Linux, but Ubuntu 14.04 does not= allow non-Ascii characters in user names. > After that, I did a more thorough search and finally found the aforementi= oned bug. It is bug #397! > I'm wondering why that bug was filed as an x2goserver bug instead of x2go= client. Bug #397 refers to when the user's home folder on the server has non-Ascii characters. That is why the bug is filed against x2goserver. Normally I would say that we should clone this bug (566) for X2Go Client for Linux. However, the bug report is already extremely long, I think we should just file a new one and link to this one. Could you please file one? > The good news: I managed to change my (linux test) home folder to /home/n= =C3=A9stor using usermod > (changing to /home/=CE=93=CE=B9=CF=8E=CF=81=CE=B3=CE=BF=CF=82 is impossib= le (=CE=93=CE=B9=CF=8E=CF=81=CE=B3=CE=BF=CF=82=3DGeorge in Greek)). > Findings: x2goclient managed to create known_hosts but the nxproxy module= failed > "*** longjmp causes uninitialized stack frame ***: /user/lib/nx/bin/nxpro= xy terminated" > > In bug #397, N=C3=A9stor gives another reason for failure > "Error: The remote NX proxy closed the connection." > which implies x2goserver rejected the connection, so I stopped there. > Could you possibly test it? (If you cannot type an =C3=A9, just copy-past= e n=C3=A9stor) > > -George 1st of all, you were talking about a home dir with non-Ascii characters on the client machine, correct? If so, that test is not applicable to #397 for the aforementioned reason. In order to properly test the fix for #397 on Ubuntu, we would have to build a nightly build of x2goserver 4.0.1.16 or 4.1.0.0 from source. It is not fixed in 4.0.1.15. (AFAIK, there are no automated nightly x2goserver builds for Ubuntu. Only for Debian, Fedora and EPEL.[2]) Besides, our "fix" for #397 is not to make homedirs with non-Ascii characters "work". Our "fix" is to present a better error message and cleanly abort the session. -Mike#2 [1] http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2gocl= ient#build_x2go_client_from_source_debug_build [2] http://jenkins.x2go.org:8080/view/Server/