When Xvnc gets terminated it kills of the VNC connection with complete disregard for the protocol. With some bad timing this causes the client to detect a problem with the protocol stream and displays an error message to the user. We should try and fix Xvnc so it shuts down more gracefully and terminates the VNC connection without causing protocol errors.
In revision 16364, we have disabled the error dialogs.
Got a dialog with broken pipe from the Linux client today. This is in the log: 2014-10-29T13:38:51: vncviewer[E]: Wed Oct 29 13:38:51 2014 2014-10-29T13:38:51: vncviewer[E]: Viewport: write: Broken pipe (32) 2014-10-29T13:38:51: vncviewer[E]: CConn: write: Broken pipe (32)
I was strace:ing Xvnc and noticed that it does not do shutdown() or close() on the VNC sockets. So that might be a good start and see if it solves the issue.
I don't think this is a server issue really. The client might be doing writes at any time, regardless of what it receives. So I think this might be a client issue. We need more investigation here. The key issue is that we are getting nasty errors that we show to the user.
This error dialog should now be suppressed as of the fixes for bug 289. Marking as resolved.
Tested as part of bug 289.
