It has been done at the server side (this is not the default behaviour anyway and this is optionnal) because this was the easiest way to do it and as far as I'm concerned, this is what I want since I have a dedicated TCE server farm and there is no reason for my TCEs to have this MagicPixel sh*t and the workaround (which has the merit to exist) is as ugly as the "bug" itself.
To me, disabling MagicPixel (which is something barely useful) at the server side is perfect. Feel free to give me a use case where this should be kept, I don't see any on my side.
Regards, Walid Moghrabi
TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3
----- Mail original -----
De: "Stefan Baur" <X2Go-ML-1@baur-itcs.de> À: "Walid MOGHRABI" <w.moghrabi@servicemagic.eu> Cc: x2go-dev@lists.x2go.org, "ionic >> Mihai Moldovan" <ionic@ionic.de> Envoyé: Mercredi 16 Mai 2018 15:55:55 Objet: Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE
Am 16.05.2018 um 15:52 schrieb Walid MOGHRABI:
MagicPixel is not a problem anymore. I filed a feature request which has been done to add a parameter to disable this behaviour directly at the nx level. Just add the "-nomagicpixel" option in x2goagent.options
Wait, that's on the server side and a per-server setting? That's not where this should go. This SHOULD be a client-side option, triggered e.g. by X2GoClient being called with "--thinclient", and active otherwise.
Kind Regards, Stefan Baur
DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you