[X2go-Dev] 3.99 Testing - Multiple X2goclient instances fail

[John A. Sullivan III]

On Thu, 2011-07-28 at 07:29 -0400, John A. Sullivan III wrote:
> On Wed, 2011-07-27 at 12:37 -0400, John A. Sullivan III wrote: 
> > On Wed, 2011-07-27 at 12:18 -0400, John A. Sullivan III wrote:
> > > On Wed, 2011-07-27 at 09:33 -0400, John A. Sullivan III wrote:
> > > > On Wed, 2011-07-27 at 14:41 +0200, Oleksandr Shneyder wrote:
> > > > > Am 27.07.2011 14:33, schrieb Mike Gabriel:
> > > > > > Hi Alex,
> > > > > > 
> > > > > > On Mi 27 Jul 2011 13:52:46 CEST Oleksandr Shneyder wrote:
> > > > > > 
> > > > > >> Am 22.07.2011 06:38, schrieb John A. Sullivan III:
> > > > > >>> I believe I have tested this on both Linux and Windows - becoming a bit
> > > > > >>> of a blur after a long hot day!.  In previous versions of X2GoClient, I
> > > > > >>> could open multiple instances and connect to multiple different X2Go
> > > > > >>> Server simultaneously.  It was not official and it generated a few
> > > > > >>> errors but it worked.  This is actually a highly desirable feature for a
> > > > > >>> possible very large account of ours.
> > > > > >>>
> > > > > >>> For some reason, that has stopped working in 3.99.  It did not work in
> > > > > >>> 3.0.1.18 either.  It does work in Pyhoca so I do not think it is an
> > > > > >>> impossibility.  If at all possible, we would like to see this
> > > > > >>> functionality restored - preferably officially but even accidentally as
> > > > > >>> it was would do :)  Thanks - John
> > > > > >>>
> > > > > >>> _______________________________________________
> > > > > >>> X2go-Dev mailing list
> > > > > >>> X2go-Dev at lists.berlios.de
> > > > > >>> https://lists.berlios.de/mailman/listinfo/x2go-dev
> > > > > >>
> > > > > >> Hello John,
> > > > > >>
> > > > > >> Unfortunately, I can't reproduce this. I was able to start a several
> > > > > >> sessions simultaneously on debian and win7, see screen shots:
> > > > > >>
> > > > > >> http://www.x2go.org/screenshots/multisess-debian.png
> > > > > >> http://www.x2go.org/screenshots/multisess-win7.png
> > > > > > 
> > > > > > Thanks for all your testing!!!!
> > > > > > 
> > > > > > If I recall John correctly, her meant:
> > > > > > 
> > > > > >   start x2goclient, connect to session A as user A
> > > > > >   start another x2goclient, also connect to session A as user A
> > > > > >       (that is a second session as the same user to the same server)
> > > > > > 
> > > > > > John, could you please cross-check this?
> > > > > > 
> > > > > > Thanks,
> > > > > > Mike
> > > > > > 
> > > > > 
> > > > > As I understood, John meant, connecting with user A to server A, start
> > > > > second client and connecting as user B to server B. But it does not
> > > > > matter, I've tried all variants:
> > > > > 
> > > > > A->A
> > > > > B->B
> > > > > 
> > > > > A->A
> > > > > B->A
> > > > > 
> > > > > A->A
> > > > > A->B
> > > > > 
> > > > > A->A
> > > > > A->A
> > > > > 
> > > > > regards,
> > > > > alex
> > > > <snip>
> > > > Oleksandr is correct - two separate users connected to two separate X2Go
> > > > servers.  I can do the initial connection but, within a few seconds, the
> > > > first session times out.  I've seen this myself on Debian and Windows XP
> > > > and another tester confirmed it on Windows 7 64 bit.  I'll try to dig
> > > > out more details.  Thanks very much for investigating - John
> > > <snip>
> > > OK - now this is bizarre - after days of it not working on Squeeze, it
> > > decided to work today when I tested. All right, who changed things while
> > > I wasn't looking! I'll give Windows a test later but I do know I wasn't
> > > imagining this and we had another tester confirm the same phenomenon.
> > > I'll check again with them, too.  Thanks - John
> > <snip>
> > The bizarreness continues.  Now it works in Windows, too.  Still waiting
> > to hear back from the other tester.  Other things have suddenly started
> > to work, too, as I'll report separately, yet we've done nothing to
> > change anything in our environment :(
> <snip>
> I can confirm this is still a problem for some.  The below report is
> from a windows 7/64 user.  How do we begin troubleshooting? Thanks -
> John
> 
> Same problem - soon after starting the second window, the system comes
> up with an error message: "No response received from the remote server.
> Do you want to terminate the current session?".  If one selects No,  one
> is able to connect and use the current (second) session, but it
> immediately kills the previously started (first) session, with the
> message "The connection with the remote session was shut down.  Please
> check the state of your network connection."
> 
> If one then attempts to start another (third) session, it generates the
> second error message again, which prevents a new session from starting,
> but does leave the existing (second) sesson running.
> 
> Not sure if there is a clue here, but when trying to log into the third
> session (when the session-locking dialog box comes up), I note that the
> number of black bullets coming up is different from the number of keys
> that I have pressed - and that if one tries to erase them with the
> backspace key, each press generates another black bullet.
> 
> So no progress viewed from this end, I regret.
> 
<snip>
This user (who happens to be working on an unexpected potentially
multi-thousand seat deployment based upon multiple simultaneous sessions
per user) confirmed that after upgrading from 3.0.1.14 to 3.99.0.0, he
still has the same problem - John