From matthew.rubenstein@blue-green-group.com Tue Feb 6 20:08:27 2018 Received: (at submit) by bugs.x2go.org; 6 Feb 2018 19:08:30 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.8 required=3.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID autolearn=ham autolearn_force=no version=3.4.1 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id CF1965DACF for ; Tue, 6 Feb 2018 20:08:27 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de Received: from ymir.das-netzwerkteam.de ([127.0.0.1]) by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uNhLiZw5I4H8 for ; Tue, 6 Feb 2018 20:08:17 +0100 (CET) Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 224F75DAC8 for ; Tue, 6 Feb 2018 20:08:16 +0100 (CET) Received: by mail-qk0-x229.google.com with SMTP id l29so3691877qkj.8 for ; Tue, 06 Feb 2018 11:08:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=blue-green-group-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:subject:to:date:organization:mime-version :content-transfer-encoding; bh=CQs77PYnucHISlzZlmJT/CE8QbNTJjSQ6cZ8k/hMdHg=; b=y7KqboSHt+vXMJCs1pawEaOmB2MF9+DoFlXeN7kbdj7psWkxjIcbr0OD+SuowN8UTk 2pFXAeyX3Shoy3Vgos4c4tG2WMIBgH9sVS2s+kwS/2Wblodp/uoRntQHhi+vi88LwB2p XPf+J39H9qFEdnF0VWhyrSfNN3ZJ3X7T48/fFTk70Uak6DAuSAJBnqiUWsT/zqQ1ZC9J ocRnIG2qQdoLgNPba5iP3Y9s/FCTf0EquGijtLJ0kUrv1ElXoITgc7PgmdzdPCQuj/X2 Xrc8YXEJ/8qJH0NH+idBrKGuTtOqI4mVkmUzwsHE9DfTEetR+A0qMrqTjzrq1FR63qXd 1IUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:subject:to:date:organization :mime-version:content-transfer-encoding; bh=CQs77PYnucHISlzZlmJT/CE8QbNTJjSQ6cZ8k/hMdHg=; b=KXntMdxIyPqP1WTNebDG0Fl3ers/inTGfw8bkfI3v/Dfz0sJ21Xn+AhgS3m88vh4Kb X+7NfsqVKPogAHcYUnjPBvnqRZo9kHplLGVru05B30kXRliJaXikPiDKyWPqNxsPsqCt wx6oeZVm4HSUkBs431HMjnEx4bRlVdJYbFufbJH/HH7PUcXvIK1Chp5QZX1M+RfG3eMq fjMBhEZULgy/i2Pz7+TdU23h7KpzDeXh0tDaD3gmECEeUlWKIo+e3GL1ysfDw0xd5aFV GxMTJ0eyBh/4u6giboqAVDf3f3tKsPqXkFQocLJ0+KqBk9QwMiTiuqdT6VH/ucnZsszV 1Y1Q== X-Gm-Message-State: APf1xPBamZBlHlohmXQ72uAXedatywMS1nv7VckGoBzZBax8g3oLOJle YhMCvnR4Vf+4z3zhrSwu07z2DNkCrZw= X-Google-Smtp-Source: AH8x226ONNo46MZNW7NqmN+S1xF5vZITWim9SbZ7GJ6as181qkRqfzmIbpGYSLeaMlHwFT8uArhl9g== X-Received: by 10.55.74.142 with SMTP id x136mr4599328qka.223.1517944095501; Tue, 06 Feb 2018 11:08:15 -0800 (PST) Received: from studion99 (ool-45756eaa.dyn.optonline.net. [69.117.110.170]) by smtp.gmail.com with ESMTPSA id z66sm7797090qkc.9.2018.02.06.11.08.14 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 06 Feb 2018 11:08:14 -0800 (PST) From: Matthew Rubenstein X-Google-Original-From: Matthew Rubenstein Message-ID: <1517944093.27892.944.camel@blue-green-group.com> Subject: X2Go Doesn't Set Remote Environment To: submit@bugs.x2go.org Date: Tue, 06 Feb 2018 14:08:13 -0500 Organization: Blue Green Group, LLC Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.1-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Package: x2goclient, x2gostartagent Version: 4.0.5.1 Severity: wishlist Hello. x2goclient and x2gostartagent (and the rest of X2Go) use libssh, but do not use either the local ssh ~/.ssh/environment or the remote sshd ~/.ssh/rc . Neither does X2Go use its own corresponding config files for the remote environment. X2Go will use the remote ~/.bashrc when X2Go starts the remote bash shell, but if that .bashrc quits upon detecting a non-interactive bash session (such as the ones X2Go creates) then those .bashrc configs aren't applied to the X2Go session. That non-interactive=quit logic is standard practice, and indeed Ubuntu's /etc/skel/.bashrc includes it (among many other distros). This lack of X2Go session configuration can cause remote client applications to fail. Especially where the X2Go 'Session type' = 'Single application', where the environment X2Go is using was set per- user at (interactive) login prior to using X2Go. The hackaround is to create a per-user wrapper that sets the environment (but can't just source ~/.bashrc for the non-interactive session). This is unmanageable especially for multiple users and multiple local/remote hosts, and makes setting the remote environment complex and time consuming (compared to the basic X2Go invocation configuration). It also requires the user have access to the remote filesystem, probably to a remote shell, and to use it to write freeform wrappers. The best support for setting the environment would use a local ~/.x2gorc that can set the remote environment with bash syntax, overridden by a GUI in x2goclient, overridden by a remote ~/.x2gorc , with perhaps system defaults local and remote in /etc/x2go/.x2gorc . The X2Go config files/GUI could include an option to use their ssh(d)equivalents, ie. [. ~/.ssh/environment].