I wasn't looking to start a "shadow" session to access existing session. I just needed to use some software that was installed on that machine so fresh session worked fine. I will try the "extensions" approach for testing and will stick with a separate user scenario for main needs in future. Thank you.
-- Simon On Thu, May 21, 2015 at 3:23 PM, Mihai Moldovan <[email protected]> wrote: > On 21.05.2015 08:22 PM, Simon Baev wrote: > > I saw this setting but for some reason it didn't affect anything when I > > changed it to 96. Could it be caused by the fact that ongoing (not logged > > out) session was active on the server (physical console) while I was > trying > > to remotely connect to it via X2Go? > > What exactly are you doing, anyway? It seems like you are starting a shadow > session, i.e., connect to the already running "local" X server on the > server > machine? > > The DPI setting in X2Go Client controls the private X server's - i.e., > nxagent's > - DPI value. There's a caveat though, in the sense that desktop > environments can > and most likely will overwrite that. > > > > The only way I found to connect to that server with reasonable DPI was to > > create a separate user that runs default settings, but that doesn't seem > to > > be a good fix. > > X2Go provides support for hooks via its "extensions" support. I guess it's > not > properly documented anywhere yet, but the basic idea is to put scripts into > /usr/lib/x2go/extensions/. The "targets" in there are sort-of > self-explanatory. > > N.B.: the amount of "targets" available may differ between release and > nightly > versions. > > > All this said, I think a separate user is the "cleanest" and best-working > idea. > > > > Mihai > > -- Simon
_______________________________________________ x2go-user mailing list [email protected] http://lists.x2go.org/listinfo/x2go-user
