In case there's an error on the remote device (e.g. no sftp-server available) the deployment process exits internally with a call to SftpChannelPrivate::handleExitStatus. But this does not close the connection. As a result the deployment dialog still shows some progress (until timeout) although the connection already failed. Maybe one should add a call to handleChannelClose when an exit status has arrived. Or any other close signal (throw a SSH client exception or whatever), such that the parent connection handle gets informed about the exit status too and shows the user an appropriate error message