From unknown Thu Mar 28 22:52:18 2024 X-Loop: owner@bugs.x2go.org Subject: Bug#402: [X2Go-Dev] Bug#402: Bug#402: Numlock issues Reply-To: jordi@amospalla.es, 402@bugs.x2go.org Resent-From: jordi@amospalla.es Resent-To: x2go-dev@lists.berlios.de Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Fri, 11 Apr 2014 09:40:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 402 X-X2Go-PR-Package: x2gomatebindings X-X2Go-PR-Keywords: moreinfo Received: via spool by 402-submit@bugs.x2go.org id=B402.139720918523249 (code B ref 402); Fri, 11 Apr 2014 09:40:02 +0000 Received: (at 402) by bugs.x2go.org; 11 Apr 2014 09:39:45 +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 autolearn=ham version=3.3.2 Received: from ispconfig.net1.amospalla.es (amospalla.es [188.40.66.228]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 1B4105DB09 for <402@bugs.x2go.org>; Fri, 11 Apr 2014 11:39:45 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ispconfig.net1.amospalla.es (Postfix) with ESMTP id C42031AC063C; Fri, 11 Apr 2014 11:39:44 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at ispconfig.amospalla.es Received: from ispconfig.net1.amospalla.es ([127.0.0.1]) by localhost (ispconfig.amospalla.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XjOrGD1MUv28; Fri, 11 Apr 2014 11:39:44 +0200 (CEST) Received: from amospalla.es (localhost [IPv6:::1]) by ispconfig.net1.amospalla.es (Postfix) with ESMTP id 4510C1AC0625; Fri, 11 Apr 2014 11:39:44 +0200 (CEST) Received: from 62.82.108.2 (SquirrelMail authenticated user jordi@amospalla.es) by amospalla.es with HTTP; Fri, 11 Apr 2014 11:39:44 +0200 Message-ID: <503a881576ef97220217828216264aba.squirrel@amospalla.es> In-Reply-To: <20140411065641.Horde.yF9GE4E_PlwSEp-wohkVdQ3@mail.das-netzwerkteam.de> References: <8be4d14fda106d24b56c8cf94ec9a918.squirrel@www.amospalla.es> <20140402130029.Horde.pCv_6moTdCQfNpA2fQNFFQ1@mail.das-netzwerkteam.de> <53404130.6080903@amospalla.es> <20140405193722.Horde.TssS-w1ielZ5Dbza76YEJA1@mail.das-netzwerkteam.de> <3f8a733e7f2c8b1774c67424a4d52209.squirrel@amospalla.es> <20140410112954.Horde.uCkuh3QAX7cM8yLbgqcxtQ1@mail.das-netzwerkteam.de> <20140410165745.Horde.xCxYOAHT8DxhPF2Uy13reA1@mail.das-netzwerkteam.de> <20140411065641.Horde.yF9GE4E_PlwSEp-wohkVdQ3@mail.das-netzwerkteam.de> Date: Fri, 11 Apr 2014 11:39:44 +0200 From: jordi@amospalla.es To: "Mike Gabriel" Cc: 402@bugs.x2go.org User-Agent: SquirrelMail/1.4.23 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Hi Mike, > Hi Jordi, > > On Fr 11 Apr 2014 08:51:32 CEST, jordi wrote: > >>> My question is: if you run the pre-runcommand script just before >>> session startup and then run the post-runcommand script right after >>> session startup (not when the session is ended), are the settings then >>> ok? >> >> Yes right, these scripts should be run at session start and at session >> end. > > Maybe we are misunderstanding each other. > > My intention is: change the config for a minute or so, launch the X2Go > session and then immediately switch back to the saved values. > > My question is: > > o launch X2Go session including the pre-runcommand script > o Wait for the session to come up > o MANUALLY launch the post-runcommand script > > Does that break the numlock state in the X2Go session immediately? Or > do the related applications remember the settings they had during > session startup. > > I don't want X2Go to "break" user profiles while X2Go sessions are > running. It is tolerable to tweak configuration files for 20secs > during session startup, but not for longer. > > The alternative approach would be making MATE (upstream) aware of X2Go > sessions (vs. local X11 sessions). Checked, these settings are global for the user, modifying them on a session do alter another concurrent sessions, and gets saved for future ones. Jordi.