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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Am 21.05.2015 um 20:22 schrieb Simon Baev:
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?
That might be - never tried that, I'm usually logged in either locally or remote, but not both. We'll have to wait for one of the Devs to chime in here.
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJVXi6uAAoJEG7d9BjNvlEZugQH/jcLLSNB7TxXSYeDzMy9D8PQ ztUPslSG5CSDXGxZJtjG5vwI4LS5GjrKJH4207MsMbZyGxIqJ9rFNFhazAKKFFqv HnDK/rTMAKP6RUnK9n7oFOtLNeB+Zln1vbg3Bf+3uxIaBxWwvsKiDQXcJcozr+fv Gu8Zu3FYoA7kdf3LphtWks3CY7rHOqATNZ1sLuIYAleQbnKVk08LLyyQ6MgI4A93 x/NEcqCqZVLzg6Fyy7fz/wXYkV75ovgLH2zIU2CVzEmDydvFG5RFOVWKaQpijO4I yZFicNDkaNVtI0ppRya7tZLYb1m2MDXwB6YFlQ/uWHsb/EV3eOwDcgpMdkvHPGY= =e1xy -----END PGP SIGNATURE-----
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
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
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 <ionic@ionic.de> 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
On 21.05.2015 08:22 PM, Simon Baev wrote: 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
Simon Baev píše v Čt 21. 05. 2015 v 14:22 -0400:
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.
I switched recently from KDE 4 to MATE (Arch Linux) and can see the same behaviour with MATE: x2goserver/nxagent ignores the dpi settings set in x2goclient.
I had not had time to investigate this further and for now worked around that by placing two launchers on my desktop and running them manually in the current session:
For local sessions: gsettings set org.mate.font-rendering dpi 107
For x2go sessions: gsettings set org.mate.font-rendering dpi 96
It works on the fly, only some apps (skype) need to be closed and restarted.
I believe one could use .config/autostart/ and some script with tests of the environment to set the proper DPI during log-in phase. This would resolve the issue with uncleanly terminated sessions. Perhaps it may not work for published apps.
I hope to look at the issue later (well, just a cheap promise...)
Milan
In Mate, if you go into System->Preferences->Look and Feel->Appearance,
then select the "Fonts" tab, in the lower right click on "Details", then in the upper left you can set the resolution to whatever DPI you want. This works with X2Go, NX protocol with Remmina, and pretty much everything else I've tried.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Fri, 26 Jun 2015, Milan Kníek wrote:
Date: Fri, 26 Jun 2015 13:34:54 +0200 From: "Milan [UTF-8] Kníek" <knizek.confy@gmail.com> To: Simon Baev <simonbaev@gmail.com>, x2go-user <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] x2goserver on Ubuntu Mate 15.04 with 4k monitor and high font-rendering DPI
Simon Baev píÿÿe v ÿÿt 21. 05. 2015 v 14:22 -0400:
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.
I switched recently from KDE 4 to MATE (Arch Linux) and can see the same behaviour with MATE: x2goserver/nxagent ignores the dpi settings set in x2goclient.
I had not had time to investigate this further and for now worked around that by placing two launchers on my desktop and running them manually in the current session:
For local sessions: gsettings set org.mate.font-rendering dpi 107
For x2go sessions: gsettings set org.mate.font-rendering dpi 96
It works on the fly, only some apps (skype) need to be closed and restarted.
I believe one could use .config/autostart/ and some script with tests of the environment to set the proper DPI during log-in phase. This would resolve the issue with uncleanly terminated sessions. Perhaps it may not work for published apps.
I hope to look at the issue later (well, just a cheap promise...)
Milan
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Robert Dinse píše v Pá 26. 06. 2015 v 05:32 -0700:
In Mate, if you go into System->Preferences->Look and Feel
->Appearance, then select the "Fonts" tab, in the lower right click on "Details", then in the upper left you can set the resolution to whatever DPI you want.
This works with X2Go, NX protocol with Remmina, and pretty much everything else I've tried.
It surely does, because it is the same as the command: gsettings set org.mate.font-rendering dpi XX
Using GUI is great for a once-set-do-not-touch-anymore action, but when you need to change the DPI often...
Anyway, the aim is to use DPI settings as per x2go client setup. It seems that in MATE, once the user sets hiw own value, the DPI from xorg.conf is ignored (which sounds logical but does not fit the bill for our use). xrandr --dpi XX in the running x2go session also does not have any effect.
Milan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Am 26.06.2015 um 15:27 schrieb Milan Knížek:
Robert Dinse píše v Pá 26. 06. 2015 v 05:32 -0700:
In Mate, if you go into System->Preferences->Look and Feel ->Appearance, then select the "Fonts" tab, in the lower right click on "Details", then in the upper left you can set the resolution to whatever DPI you want. This works with X2Go, NX protocol with Remmina, and pretty much everything else I've tried.
It surely does, because it is the same as the command: gsettings set org.mate.font-rendering dpi XX
Using GUI is great for a once-set-do-not-touch-anymore action, but when you need to change the DPI often...
Anyway, the aim is to use DPI settings as per x2go client setup. It seems that in MATE, once the user sets hiw own value, the DPI from xorg.conf is ignored (which sounds logical but does not fit the bill for our use). xrandr --dpi XX in the running x2go session also does not have any effect.
So basically, what you'd need for MATE is something that reads the desired DPI value from an ENV var or from some file, then issues the gsettings command you quoted above, and this would have to run on every session startup and reconnect, right?
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJVjWBmAAoJEG7d9BjNvlEZHmEH/jb0VgxmlO8MX+dbG4lv03rP hWc3I8PKFR9Id7EleMHEhUEfojLnKsenc3AldIYK+aUFTP8uEYwGZRQw7S/T5gd6 r6iz2QD4XTD2kfnAHg9mJ3c6lalxSQKr2tYeEw/VSs5CU62keafBa0kZ+lOoT3nE pCxhDOCkprrm/1Xtnob1tgXNi+SiZIVbmRpYuNHdKnWQxh1j5Z897LJVI/kB0/zS pIdxhntQxGW9fS7aCykcumL6pcc8dUBbUThgeol40EJbpzwALGKOTHt52PuhEvto DGT1fNltFgK16OzlNlxTN+b4Ik+6xM+l48TakkkOCOFcAKWYfRNBIjJ6J6WpOlk= =a/Jr -----END PGP SIGNATURE-----
Stefan Baur píše v Fri 26. 06. 2015 v 16:23 +0200:
Am 26.06.2015 um 15:27 schrieb Milan Knížek:
Anyway, the aim is to use DPI settings as per x2go client setup. It seems that in MATE, once the user sets hiw own value, the DPI from xorg.conf is ignored (which sounds logical but does not fit the bill for our use). xrandr --dpi XX in the running x2go session also does not have any effect.
So basically, what you'd need for MATE is something that reads the desired DPI value from an ENV var or from some file, then issues the gsettings command you quoted above, and this would have to run on every session startup and reconnect, right?
Yes, something along those lines.
Part of it could be done by x2go (startup, reconnect, terminate) and the other part by the user, eg. via $HOME/.config/autostart (for situations when x2go session terminates uncleanly and then the user starts a local session).
The latter could be done through autodetection, but that approach would make any user specific DPI for local session obsolete after re-login...
Once I have time I try to look at it, because running the gsettings command once the user is logged in is suboptimal (e.g. Skype has to be restarted to reflect the new DPI).
http://milan-knizek.net/ About linux and photography (Czech only) O linuxu a fotografování
Wondering if anyone has considered an x2go plugin for Remina?
Regarding 15.04, I'm using on a workstation, but loaded onto a server I
found it too unstable and reverted back to 14.10.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sun, 5 Jul 2015, Milan Kníek wrote:
Date: Sun, 05 Jul 2015 23:01:59 +0200 From: "Milan [UTF-8] Kníek" <knizek.confy@gmail.com> To: Stefan Baur <X2Go-ML-1@baur-itcs.de>, x2go-user@lists.x2go.org Subject: Re: [X2Go-User] x2goserver on Ubuntu Mate 15.04 with 4k monitor and high font-rendering DPI
Stefan Baur píÿÿe v Fri 26. 06. 2015 v 16:23 +0200:
Am 26.06.2015 um 15:27 schrieb Milan Kníÿÿek:
Anyway, the aim is to use DPI settings as per x2go client setup. It seems that in MATE, once the user sets hiw own value, the DPI from xorg.conf is ignored (which sounds logical but does not fit the bill for our use). xrandr --dpi XX in the running x2go session also does not have any effect.
So basically, what you'd need for MATE is something that reads the desired DPI value from an ENV var or from some file, then issues the gsettings command you quoted above, and this would have to run on every session startup and reconnect, right?
Yes, something along those lines.
Part of it could be done by x2go (startup, reconnect, terminate) and the other part by the user, eg. via $HOME/.config/autostart (for situations when x2go session terminates uncleanly and then the user starts a local session).
The latter could be done through autodetection, but that approach would make any user specific DPI for local session obsolete after re-login...
Once I have time I try to look at it, because running the gsettings command once the user is logged in is suboptimal (e.g. Skype has to be restarted to reflect the new DPI).
Milan
http://milan-knizek.net/ About linux and photography (Czech only) O linuxu a fotografování
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Am 05.07.2015 um 23:16 schrieb Robert Dinse:
Wondering if anyone has considered an x2go plugin for Remina?
That's a dev question, so you might get more responses over on x2go-dev.
Just saying. ;-)
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJVmZ82AAoJEG7d9BjNvlEZpJEH/1IKCs/CPs3UeTiJY/vjtxD9 cqjdw7h6CPaqrMJlUjzuT6isJVLXX6JZ+PRCH8nJTO1XqUVDaIVOsOKjY22cohGO wHGUXXj/dw9A4d7Kt0QTU/cS+OkutrVFK1niZiQjYZzSkQ0U4h7fmqa2QMdRT5YS OQxU9knuYl06/Xl0d03x8v0DtpCF8Gn1le0/nG0VqSnVUhOkG841l86ptZhm3a2i yOOx7siERovoC+86xftdQCOXSiUrzoricQnmj55zTufF9lPIB92h6+dQtI4PzpST S2jiQuA3PFk7AP9ccALK2fokb24iAVClALk5LHj34aSKBwbPozkLGEahGSE0aJE= =ewrj -----END PGP SIGNATURE-----
For what its' worth, xrandr is broken if you have xcinerama enabled, at
least with the Nvidia drivers.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Fri, 26 Jun 2015, Milan Kníek wrote:
Date: Fri, 26 Jun 2015 15:27:26 +0200 From: "Milan [UTF-8] Kníek" <knizek.confy@gmail.com> To: Robert Dinse <nanook@eskimo.com> Cc: Simon Baev <simonbaev@gmail.com>, x2go-user <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] x2goserver on Ubuntu Mate 15.04 with 4k monitor and high font-rendering DPI
Robert Dinse píÿÿe v Pá 26. 06. 2015 v 05:32 -0700:
In Mate, if you go into System->Preferences->Look and Feel
->Appearance, then select the "Fonts" tab, in the lower right click on "Details", then in the upper left you can set the resolution to whatever DPI you want. This works with X2Go, NX protocol with Remmina, and pretty much everything else I've tried.
It surely does, because it is the same as the command: gsettings set org.mate.font-rendering dpi XX
Using GUI is great for a once-set-do-not-touch-anymore action, but when you need to change the DPI often...
Anyway, the aim is to use DPI settings as per x2go client setup. It seems that in MATE, once the user sets hiw own value, the DPI from xorg.conf is ignored (which sounds logical but does not fit the bill for our use). xrandr --dpi XX in the running x2go session also does not have any effect.
Milan