From chrischavez@gmx.us Sun Jul 10 08:32:07 2016 Received: (at 402) by bugs.x2go.org; 10 Jul 2016 06:32:09 +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=0.8 required=3.0 tests=BAYES_50,FREEMAIL_FROM, URIBL_BLOCKED autolearn=ham version=3.3.2 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 4276E5DDF5 for <402@bugs.x2go.org>; Sun, 10 Jul 2016 08:32:07 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de Received: from ymir.das-netzwerkteam.de ([127.0.0.1]) by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWyf9f3wkiqV for <402@bugs.x2go.org>; Sun, 10 Jul 2016 08:32:00 +0200 (CEST) X-Greylist: delayed 301 seconds by postgrey-1.34 at ymir.das-netzwerkteam.de; Sun, 10 Jul 2016 08:32:00 CEST Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 69B7B5DDD0 for <402@bugs.x2go.org>; Sun, 10 Jul 2016 08:32:00 +0200 (CEST) Received: from mail-yw0-f171.google.com ([209.85.161.171]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MWkZL-1btJCT2VXH-00XufO for <402@bugs.x2go.org>; Sun, 10 Jul 2016 08:26:58 +0200 Received: by mail-yw0-f171.google.com with SMTP id b72so69024213ywa.3 for <402@bugs.x2go.org>; Sat, 09 Jul 2016 23:26:58 -0700 (PDT) X-Gm-Message-State: ALyK8tIQS+yOZwuZ+Yd63cP6Bgz7l2AACtwAH1aHyZrCa1svdN9jzeomFZdGHeuZzsO0kQ2dFWkwWGkSW1pv+Q== X-Received: by 10.13.199.130 with SMTP id j124mr9905133ywd.142.1468132017098; Sat, 09 Jul 2016 23:26:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.115.85 with HTTP; Sat, 9 Jul 2016 23:26:37 -0700 (PDT) In-Reply-To: <20141111125456.Horde.kt23NnRADz-iSdWMI7QMrA8@mail.das-netzwerkteam.de> References: <20141111125456.Horde.kt23NnRADz-iSdWMI7QMrA8@mail.das-netzwerkteam.de> From: Christopher Chavez Date: Sun, 10 Jul 2016 00:26:37 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Related issue in Ubuntu MATE... To: 402@bugs.x2go.org Cc: jordi@amospalla.es, Mike Gabriel Content-Type: text/plain; charset=UTF-8 X-Provags-ID: V03:K0:LeYPyvdCuYr6BtkfM8YSCUdyEukNisCMBbFtSZHLTT0OuRAQeOS XtpxLek09PDeaHJb96fXomf28EiXHgADTWO4yVkUHDv0R5zbtpRm1SETKpJFm4ZpQFfePS6 lua5GIlGVQ64NEBJ4pxBMcntkTBPnQaNVMrRCh3ECWJP+nBX9gssXvLLVN4ECOvWZDMVazC 2lt0a37dsFMvIcATjKGeA== X-UI-Out-Filterresults: notjunk:1;V01:K0:sZ7WmmCUN3I=:sc25hNjAbteb0wvoMuSasB RBnyjtcVsPwgYK3NpIeg2K3WqDThAyI2upMt/Bk3buYaTF8SGYV8pnzBb/uuBO7W8nYgM1tWC MLjfl86iZ5CwLBaY6zdDWnM7G4NPDQ0llEl24VxRYZjBXBkJWjzpu4TBadrJ+ioP6WDFefVX9 IdWLw+9SH2hKnLsxqaKcGzyDkk1EiZ2YIfqmBZFA6pxZaY1txmv0R3ZK4OL2RvRRHhdJKQPJo jWEBjE9424PVnKtQMmjKmaojISBxXr8U+VHoQMj+ePIEUqzCfu/nTP/VrO5sq2glUYaMsfUsu dd/BmEJxxWeHYsABjz196RQjuQufdNR+b6wx8E2Hi0zy+6/P1FHQqNVD9sUw7Hqnqn/F9x6Jh MTrtiA1NOYwPUais9lXwUYwmaO/4qiPrSslyN+iI24DF461kq2DRh9FobN45LpHlN2oripzHa QaSsQ6As+IAAAEdMsLJvx57myJS5NwoGQ5Lx4dqedj5/86RboBhWPqNKUEMQ4ppNjT8qrlriH R58buuOYQynO9I2qucgT21xIuriD2XtYqoKctyX1R/BnGZS1e65MiRFTON/2KNuZ53Y24Sa7k /3IDZdqgo+AFNtNhAgoidmWfFm3KK6HDBcqhPl2vZJxOI27u4HWY9DUTzKXGb4O0Y5Lhx85LL nNd41iquUuUj+A25i8NCy7NcJTEVvt+Ru3l47VqQZ3nNfEfvpZPlEyLrW3oXUz7fM9TnR/5MT yRV+Eg2RocBaMsEsAnxDZiRd7JZJlI6QtC5/zMswtY1xuNzPj/BvdB078bSMaihDu+RIlr594 Yieg6za 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 On Tue, Nov 11, 2014 at 5:54 AM, Mike Gabriel 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 >