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?

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.

Simon

Am 21.05.2015 um 20:05 schrieb Simon Baev:
> Hello,
>
> I'm looking for a way to run *x2goserver* on *Ubuntu Mate 15.04*
> which is living on computer with *4k monitor* attached. I changed
> *DPI* settings in Control Center -> Appearance -> Fonts -> Details
> to *168* to let all applications look good when I work on that
> machine locally.
>
> When I connect to this machine using *x2goclient* running on
> another Ubuntu Mate 15.04 (attached monitor has resolution of
> 1680x1050, fullscreen mode) I am seeing *huge* fonts (as expected)
> because it also uses dpi of 168 for that remote connection.
>
> *My question*: would it be possible to run *pre-connection* (and
> then post-connection) script(s) to temporally change DPI to
> "normal" value of 96 before and recover it back to 168 upon
> completion of the x2go session? I guess it can be done by running
> "*gsettings set org.mate.font-rendering dpi 96*" command but I'm
> not sure where to include this command. And also I'm not sure how
> to protect against abnormal session termination... what if session
> will terminate without recovering DPI back to 168?

There's a setting in the X2GoClient GUI to force a DPI value, doesn't
that work for you? If no, why?

- -Stefan