© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Steps 1-3: Accurate.
Step 4: I believe it is always initially, but sometimes I reconnect repeatedly for different reasons and I can't recall for sure if it is always immediate.
Step 5: Yes, pressing crtl and alt have always fixed it.
Step 6: Accurate
Step 7: Computer is already logged in.
Step 8: Seems to be pretty common to find it has happened on the server after it has happened on the client.
Yes, I run vncviewer from the command line. I'm not sure what version it is at the moment, but I would assume whatever the version available from each of their respective repositories (I can check for sure if necessary). I run it either from school which is currently running the last LTS, which I believe is 6.10. Or my laptop which is running 7.10. Both seem to behave similarly (though for some reason I seem to have issues with the new -lowcolorlevel flag not working, but I suppose that's another issue). So no, neither is running Hardy, but I have installed vncviewer from the repository on my server (Hardy) as well (not that it's probably relevant).
Not sure if all the output is useful, but this is the result of dpkg -l vino:
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Description
+++-===
ii vino 2.21.90-0ubuntu1 VNC server for GNOME
and dpkg -l xvnc4viewer prints out the same as above, but with the last line as:
ii xvnc4viewer 4.1.1+xorg1.0.2-0 Virtual network computing client software for X
I will try to start paying more attention. It's been something I've kind of ignored for a while because since I've discovered how to make it stop, I have mostly been ignoring it. Please let me know if there is any other information I can provide to assist you. I will make an effort to see if I can reproduce on demand, but at present, no discernible pattern or reason has emerged that I can see.