Ok, I just tried it with lxde, and with lxde display 1 works properly.
With the new libs the nightly build worked properly until a few days ago when
there were updates to many of the x2go components. So there is an aspect
specific to Mate. But Mate worked properly with the previous version and works
properly locally. I'm running Mate on my local workstation as well, which is
also Ubuntu 17.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 Sat, 23 Dec 2017, Mihai Moldovan wrote:
Date: Sat, 23 Dec 2017 06:52:57 +0100
From: Mihai Moldovan <io...@ionic.de>
To: Robert Dinse <nan...@eskimo.com>
Cc: x2go-user@lists.x2go.org
Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10
* On 12/22/2017 08:08 PM, Mihai Moldovan wrote:
What does "but I can't use the bottom half or approximately right third of my
desktop now" mean exactly? Are these regions not drawn at all? Or are they drawn
but insensitive to clicks? Is the window big enough to cover the whole screen,
or is local desktop stuff visible within these regions (which would indicate
that the window is too small)?
I've played around with a 17.10 VM with Ubuntu MATE (not pure MATE) and noticed
that:
- with the legacy nx-libs version:
o the remote session had an 800x600 window within the proxy window (that was
correctly sized according to the fake fullscreen mode)
o I got an xrandr error message upon session startup (version too old)
- with the new nx-libs version:
o everything looked huge, like you said
o in MATE's appearance dialog, the "DPI" was set to 200 for some reason
o xpyinfo reported a (more correct) value of 95
o xrandr reported a *current* resolution of 800x600 and I haven't been able
to change it to a saner value
My current suspicion is that
- MATE needs a newer version of the XRANDR extension to resize itself properly
- nxagent for some reason passes through a wrong resolution value
- MATE tries to cope with the weird
should-be-high-resolution-but-is-low-instead by situation by raising the DPI
value
I guess I'll have to figure out where this discrepancy is coming from.
Mihai
_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
