On Sun, 24 Dec 2017, Mihai Moldovan wrote:
- On 12/24/2017 06:42 AM, Robert Dinse wrote:
Just installed the updates and that did fix the issue. Thank you!Great, at least we've got that.
The new architecture still is a bit weird in that it deletes all RandR modes but the one that was detected on the remote (i.e., client-side) screens, so changing the resolution within the session itself won't be possible.
This shouldn't be a huge problem in general since resizing is still possible in windowed mode and irrelevant in whole display or fullscreen modes.
Other than that, be aware that the new version still has other unresolved bugs, which include a huge memory footprint within nxproxy (server/client mode), slowdowns for no apparent reason (though only one user so far has reproduced this), random application crashes for software that uses a lot of X resources (e.g., Firefox/Pale Moon, Audacity, KDE Plasma, fvwm2, ...) and sudden connection drops (which may be related to the previous slowdowns and have so far only been experienced by one user).
Mihai
I see that you pushed another update today on Christmas. Things stillseem work but I am curious about arguments to nxagent:
root 13298 6.0 0.0 282796 81308 ? S 17:02 0:02 nxagent -nolisten tcp -nolisten tcp -dpi 96 -D -auth /root/.Xauthority -geometry 800x600 -name X2GO-root-50-1514250167_stDMATE_dp24 :50
In particular the -geometry 800x600 even though I'm set at a screenresolution of 1920x1080 (and it is displaying at the correct resolution in spite of that).
Memory usage of nxagent does not seem unreasonable to me, 282k of which81k is in core. FIrefox is around 4GB at times.