#402 - Numlock issues - X2Go Bug report logs

X2Go Bug report logs - #402
Numlock issues

Reported by: jordi@amospalla.es

Date: Fri, 17 Jan 2014 11:05:02 UTC

Severity: normal

Tags: moreinfo

Found in version 0.0.1.1

Done: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Bug is archived. No further changes may be made.

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>
Resent-Date: Thu, 10 Apr 2014 17:00:02 +0000
Resent-Message-ID: <handler.402.B402.13971490676874@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
Date: Thu, 10 Apr 2014 16:57:45 +0000
Message-ID: <20140410165745.Horde.xCxYOAHT8DxhPF2Uy13reA1@mail.das-netzwerkteam.de>
From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
To: jordi@amospalla.es
Cc: 402@bugs.x2go.org
References: <8be4d14fda106d24b56c8cf94ec9a918.squirrel@www.amospalla.es>
 <bfeb081fdd3ec995c47b4ee7c9c96654.squirrel@amospalla.es>
 <20140402130029.Horde.pCv_6moTdCQfNpA2fQNFFQ1@mail.das-netzwerkteam.de>
 <53404130.6080903@amospalla.es>
 <20140405193722.Horde.TssS-w1ielZ5Dbza76YEJA1@mail.das-netzwerkteam.de>
 <3f8a733e7f2c8b1774c67424a4d52209.squirrel@amospalla.es>
 <20140410112954.Horde.uCkuh3QAX7cM8yLbgqcxtQ1@mail.das-netzwerkteam.de>
 <e0eb059bb49c22670224068d1ec228ca.squirrel@amospalla.es>
In-Reply-To: <e0eb059bb49c22670224068d1ec228ca.squirrel@amospalla.es>
User-Agent: Internet Messaging Program (IMP) H5 (6.1.7)
Accept-Language: en,de
Organization: DAS-NETZWERKTEAM
Content-Type: multipart/signed; boundary="=_Ml7mr61-7a2cKCV5eldlug2";
 protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0

[Message part 1 (text/plain, inline)]

Hi Jordi, On Do 10 Apr 2014 15:46:26 CEST, jordi wrote: >> Hi Jordi, >> (I am re-Cc:-ing #402 in our BTS, hope that's ok...) >> >> >> On Do 10 Apr 2014 12:03:02 CEST, jordi wrote: >> >>>> Hi Jordi, >>>> >>>> On Sa 05 Apr 2014 19:45:20 CEST, Jordi MarquÃ©s wrote: >>>> >>>>> Hello Mike, sorry for late answer. >>>>> >>>>> I have looked at it, so what you need is a simple bash script. I can >>>>> do that. Could I write it and send it to you? >>>>> >>>>> If so, I think I can do it on monday. >>>>> >>>>> Jordi. >>>> >>>> Sure, send it to me. >>>> >>>> Make sure that X2Go session startup does not break local session >>>> startup. So if you change something in pre-runcommand.d, make sure it >>>> gets restored in post-runcommand.d. >>> >>> Hello Mike, >>> >>> sorry again for being late, I've got more work than I can handle. >>> >>> Please take a look at this post-runcommand.d >>> http://paste.debian.net/92885/ >>> and this pre-runcommand.d: http://paste.debian.net/92886/ . >>> >>> I write to files to save the state of the two settings previous to being >>> modified so I can restore it. I set a folder variable where I save those >>> files. Would that be a correct way to work inside X2go? I set them to >>> /tmp >>> to test, please modify them accordingly to what would be the best value. >>> >>> Not directly related to this, I've played also with the >>> reduced_resources >>> variable, which set to true, disables completely windows animations, and >>> makes window moving be done with a classic transparent line drawn box, >>> instead of the real window image. I've applied to my users, if you find >>> it >>> interesting to try tell me to add it. >> >> The approach is good. I have copied both scripts from paste.debian.net >> to my local working copy of x2gomatebindings. Thanks! >> >> However, one thought: >> >> With your proposed approach, the dconf/gsettings setup remains >> X2Go'ish for the duration of the X2Go Session. >> It would be good, to make those settings and remove them immediately, >> after the session has successfully come up. I am not sure how MATE >> will behave if you launch the post-runcommand script 20 minutes after >> the session has come up. >> >> And another thought... >> >> Another approach actually is... Talking to MATE upstream and asking >> them to patch their code directly (i.e. ignore those settings / use >> pre-set value if MATE runs inside an X2Go session). I will talk to >> Stefano & co. about that (who is MATE upstream). > > I don't really know if these settings are session aware, but my impression > is that those are global settings for a user. If they are not and I can > modify the script please let me know! My question is: if you run the pre-runcommand script just before session startup and then run the post-runcommand script right after session startup (not when the session is ended), are the settings then ok? Mike -- DAS-NETZWERKTEAM mike gabriel, 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.xfb

[Message part 2 (application/pgp-signature, inline)]

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 18:10:32 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

X2Go Bug report logs - #402 Numlock issues

X2Go Bug report logs - #402
Numlock issues