Ok, i fixit:
I need use:
--broker-url=ssh://../usr/bin/x2gobroker-ssh --broker-autologin
and add users to x2gobroker-users group ;)
Resume work too in ssh mode ;)
On 11/26/2016 11:54 AM, Miguel Quero wrote:
> I can confirm this bug, but the problem is not with all x2gobroker, the
I can confirm this bug, but the problem is not with all x2gobroker, the
resume problem become when you use ssh broker.
In my setup, when client connect with
--broker-url=https://..:8080/plain/inifile, all work fine
and resume is working. But when same clients connect with same
I can confirm that as well, also on Windows 10. Maybe of note is that
I'm using a limited account (but the same happens if I run the program
as administrator too).
I'm not entirely certain how to debug this better. Maybe I'll try the
python client and see if that happens there.
I just tried to set up two fresh test servers and a broker to try.
Sadly, your suggestion doesn't fix the issue for me. The problem remains:
Suspended sessions remain suspended forever, and an new session is
created for each new login.
-Stefan
Am 27.11.2016 um 20:04 schrieb Miguel Quero:
> Ok,
This is in fact the same bug as bug #1114. They should probably be merged.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
Package: x2goclient-4.0.5.2-2016.09.20-setup
Version: x2goclient-4.0.5.2-2016.09.20-setup
Steps to reproduce:
1. Install x2goclient-4.0.5.2-2016.09.20-setup.exe
2. Make sure C:\Users\XXX\.x2go\etc does not exist, or delete it if existed.
3. Create a new session to a x2go server.
4. Enable
