From unknown Fri Mar 29 09:59:17 2024 X-Loop: owner@bugs.x2go.org Subject: 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, 17 Jan 2014 11:05:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: report 402 X-X2Go-PR-Package: x2goserver X-X2Go-PR-Keywords: Received: via spool by submit@bugs.x2go.org id=B.13899564738009 (code B); Fri, 17 Jan 2014 11:05:02 +0000 Received: (at submit) by bugs.x2go.org; 17 Jan 2014 11:01:13 +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 autolearn=ham version=3.3.2 Received: from ispconfig.net1.amospalla.es (amospalla.es [188.40.66.228]) by ymir (Postfix) with ESMTP id E40465DB2C for ; Fri, 17 Jan 2014 12:01:12 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by ispconfig.net1.amospalla.es (Postfix) with ESMTP id AF3951AC2006 for ; Fri, 17 Jan 2014 12:01:12 +0100 (CET) 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 MBJmkv9fdRrq for ; Fri, 17 Jan 2014 12:01:11 +0100 (CET) Received: from www.amospalla.es (localhost [IPv6:::1]) by ispconfig.net1.amospalla.es (Postfix) with ESMTP id D0B901AC0877 for ; Fri, 17 Jan 2014 12:01:11 +0100 (CET) Received: from 62.82.108.2 (SquirrelMail authenticated user jordi@amospalla.es) by www.amospalla.es with HTTP; Fri, 17 Jan 2014 12:01:11 +0100 Message-ID: <8be4d14fda106d24b56c8cf94ec9a918.squirrel@www.amospalla.es> Date: Fri, 17 Jan 2014 12:01:11 +0100 From: jordi@amospalla.es To: submit@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 Package: x2goserver Version: 4.0.1.12-0x2go2+git20140108.809+wheezy.main.1 Hello, numlock does not behave correctly. It behaves like if it was randomly and continuously toggling it state. Happens when numlock key is pressed, and after some time, it seems to stabilize in some state (on or off), but it can take some time. Happens on Mate 1.6 desktop environment over Debian 6. No problem on same host with a KDE session. If numlock state is modified with numlockx binary, it works as expected, only the key triggers this. user@host:~$ while numlockx status; do sleep 0.1; done Numlock is off Numlock is off Numlock is on Numlock is on Numlock is off Numlock is on Numlock is off Numlock is on Numlock is off Numlock is on Numlock is off Numlock is off Numlock is on Numlock is on Numlock is off Numlock is on Numlock is on ... Standard output of xev, after typing on it "test" and numlock key: http://paste.debian.net/76762/