X2Go Bug report logs - #402
Numlock issues

version graph

Package: x2gomatebindings; Maintainer for x2gomatebindings is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2gomatebindings is src:x2gomatebindings.

Reported by: jordi@amospalla.es

Date: Fri, 17 Jan 2014 11:05:02 UTC

Severity: normal

Tags: moreinfo

Found in version

Done: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Bug is archived. No further changes may be made.

Full log

Message #63 received at 402@bugs.x2go.org (full text, mbox):

Received: (at 402) by bugs.x2go.org; 11 Apr 2014 09:39:45 +0000
From jordi@amospalla.es  Fri Apr 11 11:39:45 2014
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=ham
Received: from ispconfig.net1.amospalla.es (amospalla.es [])
	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 [])
	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 ([])
	by localhost (ispconfig.amospalla.es []) (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
        (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>
References: <8be4d14fda106d24b56c8cf94ec9a918.squirrel@www.amospalla.es>
Date: Fri, 11 Apr 2014 11:39:44 +0200
Subject: Re: [X2Go-Dev] Bug#402: Bug#402: Numlock issues
From: jordi@amospalla.es
To: "Mike Gabriel" <mike.gabriel@das-netzwerkteam.de>
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


Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Jan 17 11:26:52 2019; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.