What I am trying to say is the behavior changed from a working to
non-working state without my having changed nx-libs on this end, I only
changed them after things broke.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
 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, 24 Dec 2017, Mihai Moldovan wrote:

Date: Sun, 24 Dec 2017 01:17:03 +0100
From: Mihai Moldovan <[email protected]>
To: Robert Dinse <[email protected]>
Cc: [email protected]
Subject: Re: [X2Go-User] New x2go broken on Ubuntu 17.10

* On 12/24/2017 12:56 AM, Robert Dinse wrote:
      But this went from working to not working after an upgrade of x2go, I
did not recompile the libs until after it broke in an attempt to fix it.

Yes...? Where's the "but" coming from? Did I ever claim otherwise?

It's obvious that the new nx-libs version behaves differently and in this case
not particularly well.


I'll have to figure out why that is and fix it.



Mihai


_______________________________________________
x2go-user mailing list
[email protected]
https://lists.x2go.org/listinfo/x2go-user

Reply via email to