From unknown Wed May 13 19:31:36 2026
X-Loop: owner@bugs.x2go.org
Subject: Bug#402: [X2Go-Dev] Bug#402: Bug#402: Numlock issues
Reply-To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, 402@bugs.x2go.org
Resent-From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: X2Go Developers <x2go-dev@lists.berlios.de>
X-Loop: owner@bugs.x2go.org
Resent-Date: Wed, 02 Apr 2014 13:05:01 +0000
Resent-Message-ID: <handler.402.B402.139644363124587@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 402
X-X2Go-PR-Package: x2gomatebindings
X-X2Go-PR-Keywords: 
Received: via spool by 402-submit@bugs.x2go.org id=B402.139644363124587
          (code B ref 402); Wed, 02 Apr 2014 13:05:01 +0000
Received: (at 402) by bugs.x2go.org; 2 Apr 2014 13:00:31 +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,
	RCVD_IN_DNSWL_BLOCKED,URIBL_BLOCKED autolearn=ham version=3.3.2
Received: from freya.das-netzwerkteam.de (freya.das-netzwerkteam.de [88.198.48.199])
	by ymir (Postfix) with ESMTPS id 6A0085DB16
	for <402@bugs.x2go.org>; Wed,  2 Apr 2014 15:00:30 +0200 (CEST)
Received: from grimnir.das-netzwerkteam.de (grimnir.das-netzwerkteam.de [78.46.204.98])
	by freya.das-netzwerkteam.de (Postfix) with ESMTPS id BFDA3224E;
	Wed,  2 Apr 2014 15:00:28 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by grimnir.das-netzwerkteam.de (Postfix) with ESMTP id E254A3BF4F;
	Wed,  2 Apr 2014 15:00:29 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at grimnir.das-netzwerkteam.de
Received: from grimnir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (grimnir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HAreogpabQh1; Wed,  2 Apr 2014 15:00:29 +0200 (CEST)
Received: from grimnir.das-netzwerkteam.de (localhost [127.0.0.1])
	by grimnir.das-netzwerkteam.de (Postfix) with ESMTPS id 9FD843BAC7;
	Wed,  2 Apr 2014 15:00:29 +0200 (CEST)
Received: from m-118.informatik.uni-kiel.de (m-118.informatik.uni-kiel.de
 [134.245.254.118]) by mail.das-netzwerkteam.de (Horde Framework) with HTTP;
 Wed, 02 Apr 2014 13:00:29 +0000
Date: Wed, 02 Apr 2014 13:00:29 +0000
Message-ID: <20140402130029.Horde.pCv_6moTdCQfNpA2fQNFFQ1@mail.das-netzwerkteam.de>
From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
To: jordi@amospalla.es, 402@bugs.x2go.org
References: <8be4d14fda106d24b56c8cf94ec9a918.squirrel@www.amospalla.es>
 <bfeb081fdd3ec995c47b4ee7c9c96654.squirrel@amospalla.es>
In-Reply-To: <bfeb081fdd3ec995c47b4ee7c9c96654.squirrel@amospalla.es>
User-Agent: Internet Messaging Program (IMP) H5 (6.1.7)
Accept-Language: en,de
Organization: DAS-NETZWERKTEAM
X-Originating-IP: 134.245.254.118
X-Remote-Browser: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101
 Firefox/26.0 Iceweasel/26.0
Content-Type: multipart/signed; boundary="=_R2BmM3ISMZED6JJ2JWC1_w1";
 protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0

This message is in MIME format and has been PGP signed.

--=_R2BmM3ISMZED6JJ2JWC1_w1
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Control: tag -1 moreinfo

Hi Jordi,

On  Do 30 Jan 2014 09:46:04 CET, jordi wrote:

>> 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 sam=
e
>> 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
>> ...
>
> Found that the Mate setting which makes numlock state change at a very
> high rate can be disabled by:
>   gsettings set org.mate.peripherals-keyboard remember-numlock-state fals=
e
>
> Still, users notify me that numlock change randomly. I did monitor
> numlock status with "numlockx status" command, and I can see it do
> change but very intermitently.
>
> I first monitored numlock status and actively changed it to on with a
> script.
>
> Lately, I added to the keyboard options, the equivalent to "setxkbmap -o
> numpad:mac", which can be added to
> /org/mate/desktop/peripherals/keyboard/kbd/options with
> 'compat\tnumpad:mac'
>
> Here is a dirty script, which every user runs at session startup:
>
> ---------------%-----------------%------------------%------------------
> #!/bin/bash
> tab=3D"$(printf "\t")"
> cadena=3D( $(dconf read /org/mate/desktop/peripherals/keyboard/kbd/option=
s |
> sed -e 's/.*\[\|\]//g') )
> for (( i=3D0;i<${#cadena[@]};i++ )); do
> 	# esborrar '[', ']' i ','
> 	cadena[$i]=3D"$(printf "${cadena[$i]}" | sed -e 's/,//g')"
> done
> if ! echo ${cadena[@]} | grep -q 'compat\snumpad:mac'; then
> 	for (( i=3D0;i<${#cadena[@]};i++ )); do
> 		nova=3D"$nova ${cadena[$i]},"
> 	done
> 	nova=3D"$nova 'compat${tab}numpad:mac'"
> 	dconf write /org/mate/desktop/peripherals/keyboard/kbd/options "[ $nova =
]"
> fi
> gsettings set org.mate.peripherals-keyboard numlock-state          'on'
> ---------------%-----------------%------------------%------------------

I would like to get this fixed before the next release of x2gomatebindings.

Do you think you could write a patch?

Here is an example for a possible approach:
http://code.x2go.org/gitweb?p=3Dx2gomatebindings.git;a=3Dblob;f=3Dlib/x2go/=
extensions/pre-runcommand.d/005_MATE-monitors-xml-ignore;h=3D2f77bed691529e=
5cbbb45e569e196667b5b004d1;hb=3Da1a6a572d81a49c376eaab875de8343b2781d638

Simply use the extension concept of X2Go Server to hook into there and=20=
=20
execute=20code that is necessary.

The goal of such code should be that the Numlock settings are changed=20=20
for=20X2Go (on session startup e.g.), but that local logins (of the same=20=
=20
user)=20are not affected. If that is at all possible...

Mike

--=20

DAS-NETZWERKTEAM
mike=20gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x=
fb

--=_R2BmM3ISMZED6JJ2JWC1_w1
Content-Type: application/pgp-signature
Content-Description: Digitale PGP-Signatur
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAABAgAGBQJTPAntAAoJEJr0azAldxsxsKgP+wXHdzcEjplMwTWYY/5f475c
K0btqB0p0JsPUDj/jvWOtw/aYzrfXcJLrxKAn/c3aEQWFbdnR9RYEVtWyh3D6mcf
Bq7d3Qp+VbF0ZrbumcgupTbH1yYYj45mE0SPdb3H6f3cpEHC4naGchh4pdAPeqxx
d5b3TLecRWvnHnhNBYE6WI+e9fksUoJeW3cRwtmTZxCe8S+ClXqC7tzzPBCI8zMj
deC6BufjC0YanHaGrE7GLocyCXWOHXcCEAfyt+UioggEC5rmWoG2GbRd4uxEKK/D
H9rwAC1ufT8DnpZRNfYSiPcy7VBe+ZZy/l6vuNp+PrORj8KYpgv2YNVpsnmzO9ic
GjhrQwvACVUAbw5pAopDXMKg9zqX/Jt2Exnz7GSs0CRPFwW23DdFljSeNmevZ3Y/
gz5zkuu5FmfFyN588CxfiiDiBkXQV/R1acRF17EPrqHo4srmDgieFmuZYbxpLAdV
QNsElNlsVyR+SBnwgEzYEW6u4m7bYED/WHDRJeQZbPRU3SxmjSf8lJKbY/H8qEyj
2ZdExEH8/XRxejLXAyRk+dz61/D+iZmrDc/CFsMz7tuPAD9cNrA6VRC8stVj7MEs
HwMAv0UhwqZXkDfTIkvcg+KoFe+6kS5N85pGcJncBu2LGoe1HSS3rrhqpoh9YB3V
X07Bk1nWGxHX02KNEyE/
=rnoS
-----END PGP SIGNATURE-----

--=_R2BmM3ISMZED6JJ2JWC1_w1--
