I've been using Nightly Builds on Fedora, OpenSuse, Debian, and Ubuntuon account of the xrandr version issues on these machines for some time, so far so good.
I'm trying to get x2go to work on Zorin but so far I've not been able toget either stable or nightly builds to work, both exit but no error messages on either the server or client side are logged to give a clue.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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, 23 Feb 2018, Stefan Baur wrote:
Date: Fri, 23 Feb 2018 08:20:00 +0100 From: Stefan Baur <X2Go-ML-1@baur-itcs.de> Reply-To: x2go-project@lists.x2go.org To: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org>, "x2go-dev@lists.x2go.org" <x2go-dev@lists.x2go.org>, x2go-project@lists.x2go.org, x2go-announcements@lists.x2go.org Subject: [X2Go-User] Attention: All X2Go Server Admins! Upcoming major X2Go (Server) Release
Hi!
We would like to inform you that a new X2Go stable version is about to be released, most likely around March 1st, 2018.
In fact, the release is already ready - we are actively holding back the binary package builds at the moment so you have a chance to react.
If you have set all your servers to automatically update to new releases, we suggest that you disable this mechanism now until you have verified that the new version works for you.
If, on the other hand, you test and deploy updates manually, no change is required. Please test the new X2Go stable version as soon as it becomes available, so that we have a chance to fix any remaining issues that slipped through our testing early on.
Should you encounter major problems with the new version, we suggest switching to the ESR branch, codenamed "saimaa". This branch will continue to receive security updates, but is (and will remain) based on what you currently know as "stable". Some packages, like cups-x2go, pinentry-x2go, x2godesktopsharing, x2go*bindings, are not part of saimaa and thus must be pulled from the regular repository. This requires proper setting of repository priorities, so packages existing in the saimaa repository take priority over packages from the regular repository. If you need assistance with this, please make sure you have disabled automatic updates before doing anything else, then ask for help either in our IRC channel #x2go on freenode, or on the x2go-user Mailing List.
However, if you are a daredevil and already want to access binary packages that pretty much match what we are going to release soon, temporarily change your X2Go repository entry to the timestamped heuler repository bearing the timestamp of 2018-02-16, pull the update, then switch your repository back to stable. Note that this is a procedure not recommended for the average user. Try and use at your own risk.
Kind Regards, Stefan Baur
-- 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
-- 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