X2Go Bug report logs - #803
Numlock-state resets on first keypress after resume/start

Full log

Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

Received: (at submit) by bugs.x2go.org; 4 Mar 2015 18:28:35 +0000
From florian.wicke@hetzner.de  Wed Mar  4 19:28:34 2015
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,URIBL_BLOCKED
	autolearn=ham version=3.3.2
X-Greylist: delayed 967 seconds by postgrey-1.34 at ymir.das-netzwerkteam.de; Wed, 04 Mar 2015 19:28:33 CET
Received: from mail.hetzner.company (mail.hetzner.company [213.133.106.242])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id EF63C5DCAB
	for <submit@bugs.x2go.org>; Wed,  4 Mar 2015 19:28:33 +0100 (CET)
Received: from [78.46.134.130] (helo=[10.200.1.57])
	by mail.hetzner.company with esmtpsa (TLSv1.2:DHE-RSA-AES256-SHA:256)
	(Exim 4.80)
	(envelope-from <florian.wicke@hetzner.de>)
	id 1YTDmh-0007X8-IJ
	for submit@bugs.x2go.org; Wed, 04 Mar 2015 19:12:39 +0100
Message-ID: <54F74AFF.8080409@hetzner.de>
Date: Wed, 04 Mar 2015 19:12:15 +0100
From: Florian Wicke - Hetzner Online AG <florian.wicke@hetzner.de>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: submit@bugs.x2go.org
Subject: Numlock-state resets on first keypress after resume/start
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Authenticated-Sender: florian.wicke@hetzner.de

Package: x2goserver
Version: 4.0.1.18-0x2go1+git20141006.949+jessie.main.1


Unfortunately i am NOT able to "synchronize" the local numlock status to
the client session in any way or even CHANGE the numlock status of the
usersession.
Clients running as thinclients with "x2gothinclient-displaymanager" from
heuler and everything is up2date with the "heuler" branch.

Desktop is XFCE but the same issue appears with KDE or LXDE.
Numlock-state saving is disabled - but should not be executed on resume
as far as i understand - just on starting a new session.

Even replacing "x2gosetkeyboard" with an empty "exit 0"-script does not
change this behavier (my first guess was the setxkbd resetting the
numlock state on keypress).

Any ideas how i can debug this further?



Steps to reproduce:

1. turn numlock off and verify with 'numlockx status' in the user session
2. start terminal with 'numlockx status'-loop like:
   while :; do sleep 1; numockx status; done
3. have a post-resume.d-script present with 'numlockx on'-command (with
correct DISPLAY set)
4. suspend session
(5. turn local numlock on)
6. resume session
7. see 'numlockx status' transists from "off" to "on" as executed from
the post-resume.d-script

but now the unexpected problem:

8. press ANY key on the keyboard
9. see 'numlockx status' transists to "off" again no matter what your
local keyboard is set.

Time between #7 and #8 does not matter - first keypress after resume
resets numlock.




Best Regards,

 Florian Wicke

Hetzner Online AG
Industriestr. 25
91710 Gunzenhausen
Phone: +49 9831 505-0
Fax: +49 9831 505-3
florian.wicke@hetzner.de
http://www.hetzner.de

Registergericht Ansbach, HRB 3204
Vorstandsvorsitzender: Dipl. Ing. (FH) Martin Hetzner
Aufsichtsratsvorsitzende: Diana Rothhan

Send a report that this bug log contains spam.