Subject: Bug#402 closed by Mike Gabriel <[email-masked]> (Re: [X2Go-Dev] Bug#402: Related issue in Ubuntu MATE...)

From: [email-masked] (X2Go Bug Tracking System)
Date: Tue, 12 Jul 2016 04:25:02 +0000

This is an automatic notification regarding your Bug report
which was filed against the x2gomatebindings package:

#402: Numlock issues

It has been closed by Mike Gabriel <[email-masked]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mike Gabriel <[email-masked]> by
replying to this email.

-- 
402: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=402
X2Go Bug Tracking System
Contact [email-masked] with problems

Subject: Re: [X2Go-Dev] Bug#402: Related issue in Ubuntu MATE...
From: Mike Gabriel <[email-masked]>
To: [email-masked]
Cc: [email-masked]
Date: Tue, 12 Jul 2016 04:19:53 +0000

Control: close -1

On Sun Jul 10 08:26:37 2016 GMT+0200, Christopher Chavez wrote:
> I was one of the reporters of the numlock issue in
> mate-settings-daemon; I agree that the symptoms describe here are due
> to that issue. In Debian it has been resolved since
> mate-settings-daemon 1.8.2-3 (released Mar 2015).
> 
> Christopher Chavez
>

Ok, closing this bug then.

Greets, Mike
 
> On Tue, Nov 11, 2014 at 5:54 AM, Mike Gabriel
> <[email-masked]> wrote:
> > This issue (#402) is probably more a MATE upstream problem then an X2Go
> > issue itself...
> >
> >
> > Ubuntu MATE:
> > https://bugs.launchpad.net/ubuntu-mate/+bug/1364111
> >
> > MATE Upstream:
> > https://github.com/mate-desktop/mate-settings-daemon/issues/57
> >
> _______________________________________________
> x2go-dev mailing list
> [email-masked]
> http://lists.x2go.org/listinfo/x2go-dev
>

-- 
Sent from my Jolla

Subject: Numlock issues
From: [email-masked]
To: [email-masked]
Date: Fri, 17 Jan 2014 12:01:11 +0100

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/