Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#1261 Frequent lock-ups that can only be resolved with ctrl-alt-del

open
nobody
None
5
2013-07-17
2013-06-28
Marcel
No

As I am using TightVNC, frequently the input locks up: in other words, I can see the remote screen but it will not take any mouse clicks or keyboard input from me. I have tried many things but the only way that I can unlock it is to hit the send ctrl-alt-delete button, and when the ctrl-alt-del screen appears on the remote, I can hit ESC and presto, everything is back to normal.

This has been happening every few minutes to me, yet I have not been able to identify the exact sequence of events that triggers. I am under the impression that it is something related to switching windows on the remote end. I do not believe it has ever locked up if I have been working in a single window and not clicked away (I may be wrong, but that is what I believe).

It is very very frustrating and definitely did not happen as frequently in previous versions.

Please let me know what additional information I could gather (besides a reproducible way to cause the failure, which I have not been able to do so far).

I am running version 2.7.7 on both client and server. Both client and server are Vista 64 machines. However, I have been experiencing this bug through the last several versions. It seems to be worse with 2.7.7

My network connection is quite good. Both client and server are on Verizon FIOS. There are very few hops between them. Ping time is under 20ms and I can reliable push 20Mb in either direction. The connections seem stable because I can leave SSH sessions connected for days at a time without ever losing a connection.

Discussion

  • alex-tightvnc
    alex-tightvnc
    2013-06-28

    Does only one client connect to the server simultaneously or more than one?

     
    Last edit: alex-tightvnc 2013-06-28
  • Marcel
    Marcel
    2013-06-28

    Only one.

     
  • alex-tightvnc
    alex-tightvnc
    2013-06-28

    What is log verbosity level on the server side?

     
    Last edit: alex-tightvnc 2013-06-28
    • Marcel
      Marcel
      2013-06-28

      It's currently set to 0. What level should I set it to?

       
      • Marcel
        Marcel
        2013-06-28

        Ok - I upped the log on the server side to verbosity 9 and restarted the server. Then I went home and logged on and started working until I got a lock up a couple of minutes later. When the lock up happened I sent a ctrl-alt-del to unlock it, and then on the server side I made a copy of the log file which is attached. I made the copy a minute or two after the lockup so everything should be flushed.

         
        Attachments
  • Marcel
    Marcel
    2013-07-17

    I have found a 100% reproducible case of this. It causes the client to lock up whether I am running in windowed mode or full screen. I have tried it with Tight and ZRLE encoding and it causes a lock up in both.

    I am pretty sure there are other behaviors that cause lockups, but this is the first I have been able to duplicate 100%

    In the remote window, click on the very left edge of the screen, while still on the window. As soon as I do that, the remote system will not take any more input until I send it a ctrl-alt-delete. I realized this when I went to hit the start menu and missed to the left (yes, I am uncoordinated and was moving too fast).