From unknown Tue Apr 28 17:11:20 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#1382: Issue resolved Reply-To: Fred Chen , 1382@bugs.x2go.org Resent-From: Fred Chen Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Wed, 17 Apr 2019 08:45:01 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 1382 X-X2Go-PR-Package: x2goagent X-X2Go-PR-Keywords: Received: via spool by 1382-submit@bugs.x2go.org id=B1382.15554906864481 (code B ref 1382); Wed, 17 Apr 2019 08:45:01 +0000 Received: (at 1382) by bugs.x2go.org; 17 Apr 2019 08:44:46 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.8 required=3.0 tests=BAYES_50,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,MIME_QP_LONG_LINE autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id C953C5DAED for <1382@bugs.x2go.org>; Wed, 17 Apr 2019 10:44:43 +0200 (CEST) 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 KQUoj9n4M48p for <1382@bugs.x2go.org>; Wed, 17 Apr 2019 10:44:35 +0200 (CEST) Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 0B0195DA8B for <1382@bugs.x2go.org>; Wed, 17 Apr 2019 10:44:34 +0200 (CEST) Received: by mail-pf1-x430.google.com with SMTP id w25so11764520pfi.9 for <1382@bugs.x2go.org>; Wed, 17 Apr 2019 01:44:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lionsemi-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:date:subject:message-id :to; bh=CQ/lC9tiilPxtMhEQ1cUqyHoufnj9n7J9MgUhMkVD4M=; b=X1bvdfEMiJ4tnFiiymOpMKvd4i9PK5yye4ZzYbU7cp9ZxFChEgb7zw5F4Zxe9pn8ze zUwPSbZHBW87sB82EQd969C3d+c/PElU07lYNMpkv5xqG8hkqgerdyndMZTMj+hgk5nf AM1dKRi/+8H+dlY/jy4+U7kbYVrMzwFgoGJEjPnu0M7YNOvONLPk49T6ZT2qpiX9H9+I tSfGA+p61I1AyTQisWCZbSWC9TFFi1qnUXI5rK96EJEJsrfGrQvztz5nYMciUAntCYgs RqzOPAuifPjSYPHH8Wkm1pjRoZBZ7JR9oFe5ZUQAxJeeSRi9pZmeWFMefy6gkb4YTS9w N7Kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version:date :subject:message-id:to; bh=CQ/lC9tiilPxtMhEQ1cUqyHoufnj9n7J9MgUhMkVD4M=; b=eTu83SPt3sbSRAQSNkFHtOPK3O0dL0vP6uLMbNqTNaG/g4yAPU0R0sRyLh8PwUee7c 7F6md+EbSjh3vmxwyhixTTdeWO2d42UclzAV+/eKi8XsZCvhA4oqmbK+j++wlCZsWeGV 8TvT9NxujSOP7lfpiTU81+MsFmMfjHDUf34nzCNsPDa57UwvzBdgwssMM1TmZGgCzvrB 83p16PXKxd8+dA7B8Eur/Licq2ag+LJb2kpukiwZPuG3FbKzA5y4eyrtbTE8jZuhwb2X zm3SWprz6f+NB7fVrL8PIDGEGGhj903fwealmogVxrvkyGnMuZ2dd6gej10LxZc4tj9c VsBg== X-Gm-Message-State: APjAAAUO63lxM9vG4L77qSZrcwKr8GpVImJ5vEVjyN8r2iAz+u8/h6wK S7wWyKQwE7Rj5Q1ARb2MoQfLpFSm5Xi3qA== X-Google-Smtp-Source: APXvYqzjXbvnH0V8fZ97xVJdSO3Eiy2Ec9jTNjQUK8EMNFSTOv8V5hI/KaC8DtU9ujDhkLhZVJwECQ== X-Received: by 2002:a63:c61:: with SMTP id 33mr75141957pgm.293.1555490672511; Wed, 17 Apr 2019 01:44:32 -0700 (PDT) Received: from [192.168.0.111] (c-73-170-245-102.hsd1.ca.comcast.net. [73.170.245.102]) by smtp.gmail.com with ESMTPSA id v19sm73540508pfn.62.2019.04.17.01.44.31 for <1382@bugs.x2go.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Apr 2019 01:44:31 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Fred Chen Mime-Version: 1.0 (1.0) Date: Wed, 17 Apr 2019 01:44:29 -0700 Message-Id: <803F14D8-EE3B-4C20-A2B7-955D7E147C67@lionsemi.com> To: 1382@bugs.x2go.org X-Mailer: iPhone Mail (16D57) It turns out the source of the problem was a single line in the LDAP user=E2= =80=99s .bashrc that was not in the local user=E2=80=99s config. I originally did not even look at this because both the local user and the L= DAP user were configured with /bin/csh as their login shell but it seems tha= t the .bashrc is still read by the desktop manager or some other service as p= art of the Xsession. We were using environment modules and the offending line was calling =E2=80=9C= module load=E2=80=9D on a module that then loaded other modules. When a new bash shell is started from the user=E2=80=99s session, there does= n=E2=80=99t seem to be a problem so I=E2=80=99m not sure why this terminates= the session but it=E2=80=99s mostly a non-issue now for us.=