To be clear, is this the same issue you reported here? https://github.com/TurboVNC/turbovnc/issues/112
If so, then I am still unable to reproduce it. I've tried leaving multiple viewer instances on multiple O/S's sitting at the authentication prompt, and I can't reproduce the Xvnc deadlock you observed. Given my inability to reproduce the problem, I have no idea how to proceed. On 5/16/18 3:40 AM, g1patnaik wrote: > Hi, > > I noticed that if try to connect to the server with VNC viewer and when > it asks username and password and if we just leave it without entering > any, the connection will never be closed by server until it is closed > from the client end. This also is preventing any new VNC viewer > connections as the Xvnc process is going to deadlock state and waiting. > > I found this with 2.1.2 version too. Is there any option to set a > timeout so that if we forgot/couldn't respond to username and password > prompt, it will be automatically closed after timeout? > Or am I missing anything. > > > Thanks. > Jeevan. -- You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/983eff34-608f-a94b-0b43-0f1746d7f8e8%40virtualgl.org. For more options, visit https://groups.google.com/d/optout.
